The input and output of the action execution must be JSON, as this is the supported format.
The output schema must only contain the properties that are matched in the Studio Execute Action Component: if the action returns an array in the output response and you don't need that information on Studio, you must ignore that property in the output schema.
Even though multi-type variables 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.
We support multi-types variables such as
Types of authentication (not variations of them) that can be configured with Connections:
- No authentication.
- Basic authentication.
- OAuth2 Client Credentials.
- OAuth2 Client Credentials V2.
- OAuth2 Client Credentials with scopes.
- OAuth2 Resource Owner.
- OAuth2 Resource Owner V2.
- OAuth2 Authorization Code Flow.
HTTP basic authentication and OAuth follow the Request for Comments (RFC) standard. However, there is no RFC for the X-API-Key authentication.
The authentication types available cover the majority of use cases, as they are the most commonly used on public API systems.
Connections supports support third-party APIs that respond in less than 10 seconds.
Special characters will be encoded according to this table:
: / ? # [ ] @ ! $ & ' ( ) * + , ; =
Alphanumeric characters, such as 1 or a
Non-alphanumeric characters, such as á or <
Encoded (e.g.: á -> %C3%A1)
Updated 25 days ago