Glossary
A
API Key |
Unique identifier that allows an application to access an API and is used for authentication and access control. |
Authorization Code |
An OAuth 2.0 authorization flow that requests an authorization code to exchange for an access token, providing additional security to protected resources and token interception. |
Authorization Code com PKCE |
An OAuth 2.0 authorization flow that prevents code interception with unique cryptographic challenges for each authorization request. |
C
Choice |
A General Tool that performs a flow deviation within an integration based on conditions you can configure. |
Client Credentials |
An OAuth 2.0 authorization flow that uses client credentials to directly obtain access tokens without requiring any end-user interaction. |
Code Challenge Method |
Security extension in Authorization Code with PKCE that protects applications and access tokens using code challenges. |
Connector |
A step that connects to third-party applications, translating information into specific protocols, such as the HTTP protocol, to interact with APIs. |
Cron Expression |
A string that defines periodic scheduling following a specific format: <minute> <hour> <day of month> <month> <day of week>. |
D
Data Mapping |
A process that matches one or more fields from a source dataset to their equivalents in the target. In addition to establishing relationships, it ensures interoperability between data in different formats. |
E
Environment Variable |
A string that contains information applicable to the steps of the integration flow. |
Exception Flow |
Alternative flow that is activated in case of error (except status code errors) in the execution of the integration flow. It begins in the step On Exception. |
F
For Each |
A General Tool repetition method that executes the same code for each element of a list (array). |
G
General Tools |
A set of tools that performs operations with data within the integration flow. They can deviate the flow based on configured conditions (Choice), iterate elements (For Each), transform simple and complex data (JSON Transformation) and execute alternative routes when there are errors that don’t return a status code (On Exception). |
I
Integration Flow |
A set of interconnected steps that automate a process of integration between systems. The execution of the integration flow starts at the mandatory Start step and ends at the End step. |
J
JSON Transformation |
A General Tool that transforms simple and complex JSON data using JSONata language. |
O
OAuth 2.0 |
Authorization protocol that allows users to grant access to protected resources via access tokens without sharing their credentials. |
On Exception |
A General Tool that executes alternative routes when there are errors that don’t return a status code. This way, the execution of the integration flow is not interrupted. |
Open API |
Open source format used to describe and document APIs. |
S
Step |
Component of the integration flow that can have different functions, such as a trigger or a connector. There is no limit to the quantity of steps that you can add to an integration flow. |
T
Trigger |
Step that starts the execution of the integration flow and automatically replaces the Start step on the canvas. |
Share your suggestions with us!
Click here and then [+ Submit idea]