❗️

Connections doesn't support Contact/Agent Sync.

JSON

The input and output of the action execution must be JSON, as this is the supported format.

Arrays

It's possible to configure an action schema from which one or more fields are the array type.
However, to use such an action in Studio it's also necessary to use the Run Function Studio component.

🚧

The output schema must only contain the properties that are going to be used within Talkdesk (in Studio for instance). This way, a possibly not supported field will not impact the action configuration nor its usage.

Multi-type Variables

Even though multi-type variables (such as type: [string,null]) can be configured in the input/output schema of an action, it is not currently possible to map them when configuring the Studio Execute Action component. This applies to any combination of variable types.

🚧

Connections - Property Types

Null Variables

Even though null type variables (type: null) can be configured in the input/output schema of an action, it is not currently possible to map them when configuring the Studio Execute Action component.

Authentication

Types of authentication (not variations of them) that can be configured with Connections:

• No authentication.
• Basic authentication.
• X-API-Key.
• OAuth2 Client Credentials.
• OAuth2 Client Credentials V2.
• OAuth2 Client Credentials with scopes.
• OAuth2 Resource Owner.
• OAuth2 Resource Owner V2.
• OAuth2 Authorization Code Flow.

Standard Implementations

HTTP basic authentication and OAuth follow the Request for Comments (RFC) standard. However, there is no RFC for the X-API-Key authentication.

📘

More Information

HTTP Basic Authentication

X-API-Key

OAuth2

The authentication types available cover the majority of use cases, as they are the most commonly used on public API systems.

Timeouts

Connections supports support third-party APIs that respond in less than 10 seconds.

Encoding

❗️

From April 13, 2022, 10.50 am (GMT +1), all created actions, including its query parameters, will have their correspondent URL encoded according to RFC 3986.

Special characters will be encoded according to this table: