You must establish connections to the source and destination applications before a flow can run. A connector stores the system credentials and other access information for the source or target application. For instructions on configuring a specific connector, see Connect to anything.
Available connectors are categorized into several types:
-
Recently used: Some of your most recently used connectors.
-
Databases: Allow you to authenticate connections to database platforms.
-
Universal connectors: Allow you to authenticate with HTTP-based platforms, FTP servers, AS2 platforms, GraphQL platforms, or wrappers. Use a universal connector if no application connector exists for the platform you are connecting to, or if you need access to APIs or functionality not available in the prebuilt connector’s endpoints.
-
EDI trading partners: EDI trading partners.
-
Connectors: Prebuilt connectors are designed to optimize your connection to specific platforms. Whenever possible, you will find it easiest to select an application connector.
Before proceeding, gather the credentials to your application, with sufficient permissions for integration operations. You can create a connector for a source or destination application in either of the following ways:
This method creates a connector that is not bound to any specific flow. Once you've built the connector, you can add it to a flow step in Flow builder and register it.
-
From the left navigation menu, under the Resources menu, click Connections.
-
Click + Create connection at the top right.
-
In the resulting Create connection panel, select an item from the Application list.
-
Name your new connection and provide the authentication values as described in the Celigo Help Center Connection guide. Refer to your API’s control panel and documentation as needed.
-
When you save or test the connection, Celigo attempts to authenticate it and informs you of the success. (For a failed attempt, see Troubleshoot setup or test errors, below.)
You can now apply this connection to any flow or API step where it’s available.
While working in Flow builder,
-
Click Add source or Add destination/lookup, then select an item from the Application list.
-
Click into the Connection setting and select Create connection:
-
Name your new connection and provide the authentication values as described in the Celigo Help Center Connection guide. Refer to your API’s control panel and documentation as needed.
-
When you save or test the connection, Celigo attempts to authenticate it and informs you of the success. (For a failed attempt, see Troubleshoot setup or test errors, below.)
When you receive an error attempting to connect to a new or edited HTTP connection, the Celigo platform also lets you view details of the API calls, including requests, responses, and status codes made.
Important
When configuring a universal HTTP connector, you must enter its test connection settings to view the troubleshooting information.
The status for an attempted connection is displayed at the top of the Edit connection panel; scroll to the top, if necessary. Click View log to dive deeper into the messages between Celigo and your endpoint.
The result is similar to invoking an API using a third-party tool such as Postman. The log should give you greater context for debugging any connection issues and identifying a solution, especially for OAuth 2.0 HTTP connections.
Note
The connection logs are unavailable in certain scenarios:
-
All connections that you initiate from the homepage under Create > Connection.
-
All connections to OAuth endpoints that do not send a success or failure authorization callback message to the Celigo platform.
For troubleshooting issues with the data passed through a connection during a flow run, see Debug a connection.