A connection is the conduit that regulates the flow of data to and from the source and destination. When you query an application to export data from or import data into it, that HTTP request is added to the connection’s queue and processed in order, after earlier requests.
The Celigo platform offers you flexibility in selecting and changing the connection that you use for each flow step (such as an export, import, lookup, or download), including “global” changes for all of the steps in a flow that use a shared connection. You can also replace a connection across every step in an API built with API builder — see Replace a connection in API builder.
Deliberately applying connections and adjusting the concurrency levels among them gives you greater control over the volume of data that is requested. It’s the most effective way to optimize integration performance so that high-volume flows run more quickly and high-priority records reach their destination first.
Caution
When you replace a connection in a flow, all jobs in progress will be canceled, including any jobs that happen to be currently queued to run, even if the actual processing has not yet started. APIs behave differently: an API remains invokable while its connection is replaced.
Whenever you modify a flow step – via Flow builder, or > – you have the opportunity to perform any of the following connection operations:
- Select an existing connection to the same endpoint (from the list of available connections registered to the current integration)
- Add a new connection (Create connection) – applied to the current resource and available throughout your account
- Edit an existing connection to the same endpoint (the
option in the list of connections)
In other words, the Connection setting – in an import, for example – works exactly the same in either the Create import or the Edit import pane.
This Help Center provides instructions on creating connections to prebuilt applications, databases, and universal connectors.
Sample lookup (export) with editable connection
This operation applies only to the flow steps that use the connection you’re replacing; other flow steps to the same endpoint (but different, discrete connection), as well as other endpoints in the flow, are unaffected.
Tip
Be sure to configure the new connection before you continue with the steps below.
- Navigate to your integration and open a flow in Flow builder.
- In the Connections tab, find the row for a specific connection:
- Select its Actions overflow (...) menu.
-
Select Replace connection from the list.
-
In the Replace connection pane, the Connection list contains all available connections for this endpoint. Select a different connection from the list.
- Select Replace.
The new connection applies to each flow step that had used the replaced connection.
All jobs in progress will be canceled, including any jobs that happen to be currently queued to run, even if the actual processing has not yet started.
If your API uses the same connection across multiple steps, you can replace it everywhere in a single action instead of updating each step individually. You need edit access to the API's integration to replace a connection.
- Navigate to > > > .
-
Select Connections to view the connections your API uses.
[Screenshot: Connections panel in API builder showing the Actions overflow menu]
- Find the connection you want to replace and select Actions > Replace connection.
- Select a replacement connection. Only connections of the same type as the original are available, and the replacement must be registered to your API's integration.
-
Review the confirmation, which shows how many steps will be updated, and confirm the replacement.
[Screenshot: Replace connection confirmation showing the affected step count]
All affected steps are updated together — the replacement either completes for every step or doesn't apply at all. Step configurations such as mappings and scripts are preserved; only the connection reference changes. The replaced connection itself is untouched — it remains in your account and in any other resources that use it. Your API remains invokable while the replacement runs.
Note
If no step uses the selected connection, the replacement completes without updating any steps. The Connections panel can also list connections that this action doesn't modify, such as override and async-helper connections — replacing one of these reports zero steps updated.