Articles in this section

Add multiple connections to your integration app

Your integration app comes with one primary connection per endpoint by default. You can create additional connections to the same endpoint and assign them to specific flows. This is useful when you want to distribute the load across multiple credentials to improve throughput, or when you need separate connections for different stores or configurations.

For guidance on when and how to use multiple connections strategically, see Optimize your integration app flows for throughput.

Create a new connection

  1. Sign in to integrator.io and go to your integration app tile.
  2. Select Connections.
  3. Select + Create connection.
  4. On the Create connection: application page, select the endpoint to add a connection for. You can add connections only for your integration app's endpoints (for example, Shopify or NetSuite in the Shopify - NetSuite integration app).
  5. On the Create connection page, configure the connection with the required settings. For help, see Connector solutions.

Tip: Give each connection a unique, descriptive name so you can identify which connection serves which flow or store later.

Replace the connection for all steps in a flow

Use this option to switch every step in a flow to a different connection at once.

Prerequisite: Configure the new connection before following these steps.

  1. Go to your integration app tile and select Flows.
  2. In the Actions column of the flow you want to update, select Actions elipses-button.png and then select Edit flow to open Flow Builder.
  3. In Flow Builder, select Connections.
  4. In the Actions column of the connection you want to replace, select Actions elipses-button.png and then select Replace connection.
  5. In the Replace connection panel, select the new connection from the list.
  6. Select Replace.

Note: Replacing a connection cancels all in-progress and queued jobs for that flow.

Replace the connection for a single flow step

Use this option to change the connection for one specific step without affecting the rest of the flow.

  1. Go to your integration app tile and select Flows.
  2. Select the flow you want to update.
  3. In Flow Builder, select the step (import, export, or listener) you want to change.
  4. From Connection, select the new connection.

If you added a new connection for the same endpoint type, it appears in the connection list automatically.

Remove a secondary connection

You might need to remove a secondary connection that was created with the wrong store name, or one you created for testing and no longer use. Only remove a secondary connection if it is no longer used by any flow steps. Do not delete the primary connection; doing so can break your integration app.

Identify the primary connection: The primary connection is created automatically during installation. Its name follows the format <App name> Connection (for example, Shopify Connection). For NetSuite, the format includes additional detail (for example, NetSuite Connection (Shopify Integration App)). The primary connection name cannot be edited.

To delete a secondary connection:

  1. Go to Connections in your integration app tile.
  2. In the Actions column of the connection you want to remove, select Actions elipses-button.png and then select Used by.
  3. Confirm the connection is not used by any resources. If it is, unlink it from those resources first.
  4. After confirming the connection is unused, delete it using the integrator.io API:

DELETE /v1/connections/<connection_id> Host: api.integrator.io Authorization: Bearer <your_api_token>

A 204 response confirms the connection was deleted.

The request fails if the connection is still used in the integration app or has an external ID or source ID.

If you accidentally delete the primary connection, restore it using:

POST /v1/recycleBinTTL/connections/<connection_id> Host: api.integrator.io Authorization: Bearer <your_api_token>

A 204 response confirms the connection was restored.

Note: To create an API token, see Create and manage API and Personal Access tokens.