A Connection authorizes a Recipe to interact with 3rd party applications, using triggers and actions. Connections are reusable and can be used across multiple Recipes. When building a Recipe, the first step is to establish a connection between Integration Hub and an application.
Prerequisites
Integration Hub accesses connections through the application's authorization or authentication API. It establishes the connection using one of the following methods:
Basic authentication (username and password)
API Token
OAuth 2.0 (and variations)
Personal Access Token
During this process, you authorize Integration Hub to access data from the application. The granted permissions generally align with those of the user authorizing the connection.
Create Connection
A Connection in Integration Hub is the secure link between your project and an external application or system. Creating a connection allows recipes to authenticate, send data, and perform actions in that system. Connections are reusable across all recipes within the project.
To create a connection, perform the following steps:
Log in to the Application.
Navigate to Integration Hub > User > Projects.
Create a Project, for more information, refer Projects.
Click Create and select Connection in the Project.
Figure: ConnectionSearch for the App to connect.
Figure: New ConnectionEnter the required details and click Connect.
Figure: ConnectionWhen the Connection is successful, you can verify by navigating to the list page and select the Connect that was created.
Figure: ConnectionClick on the connection to view the configured details.
Figure: Connected
Others ways to create Connection
There are two ways to connect apps in Integration Hub:
In the Recipe editor
In the Connection wizard
Using Connections in Recipes
Connections are reused in Recipes in the following ways:
Note
Before configuring Triggers and Actions in Recipes, establish valid connections to apps.
#
Multiple app instances, one Recipe
Managing multiple app instances efficiently is key. Setting up separate connections for production and testing ensures smooth operation. Tying recipes to the appropriate app connections avoids conflicts. Proper authentication is required for each instance.
Multiple connections should be created for multiple instances. Separate authentication is needed for each app instance. Typically, each connection links to a single instance. Proper configuration ensures smooth integration.
Most connectors allow only one connection per app, per recipe. Single connections are the norm for each app instance. To integrate multiple instances, multiple connections are required. Proceed with unique authentication for each connection.
Runtime user connections
Recipes perform actions based on the credentials that are used to authorize the connection. However, by using the Runtime user connection feature, you can swap out connections when a recipe runs.
For example, consider a recipe that creates opportunities in Salesforce. If the connection is authorized using the Sales Manager's credentials, any opportunity created by other sales reps will still appear as if the Sales Manager created it.
Note
The Runtime user connections are available only in callable Recipes.
Connection Errors
App connections may occasionally become invalid. The following are the most common causes:
Connection errors: On occasion, app connections can become invalid. These are the most common reasons:
Modified credentials: If credentials were changed in the app and not in the Integration Hub, the connection becomes invalid.
Insufficient permissions: The user authorizing the connection doesnot have the permissions to access required data or perform certain actions.
The following are the guidelines, if an invalid connection error occurs:
Verify the authorizing user’s permissions: Verify the user who is authorizing the connection has sufficient permissions.
Verify that the connections credentials are correct: Re check the password, API key, are entered properly.
Re-authorize the connection: If the user’s permissions and credentials are valid and verified, try re-connecting the connection.
References
Documentation
FAQs
What data can Integration Hub access in Connections?
Integration Hub can access only the data available to the user authorizing the connection.
Example: If a user has view-only access to accounts in Salesforce and creates a Salesforce connection in Integration Hub, the connection will have view-only access to accounts.
What does creating a Dedicated User for Integration Hub mean?
Creating a dedicated app user for Integration Hub ensures that recipes are not dependent on a human user’s account. If a user leaves the company, recipes continue to run. A dedicated Integration Hub user allows you to customize permissions, reducing security risks. Applications define user roles and permissions with varying levels of granularity.
Why should we use Sandbox Credentials for Development?
When developing and testing recipes, use sandbox (non-production) credentials for connections. Using test data during development prevents accidental modifications to live data.