Mark an FTP connection as a trading partner – Celigo Help Center

When you create a connection to an FTP server in integrator.io, it is counted as one of the endpoint entitlements under your subscription by default. If the server is external to your organization, consider designating it as a trading partner connection instead. The connection will count as one of your trading partners instead of consuming an endpoint entitlement.

Notes:

This option applies for customers on the endpoint pricing model only. These options are not visible in accounts on the flow-based model.
You must be an account owner, administrator, or user with account-level manage permissions to access this option.
Your subscription must have an available trading partner entitlement in order to mark an FTP connection as a trading partner.
If you mark a connection as a trading partner/not a trading partner, all other connections that reference the same FTP server IP address and port are also updated.

To mark an FTP connection as a trading partner

From the Resources menu, select Connections.
-or-
Within an integration, navigate to the Connections tab.
Locate the FTP connection and open its Actions menu on the far right. Select Mark as trading partner.
A confirmation message listing the FTP connection(s) that will be marked appears. Click Confirm to proceed.

To mark an FTP connection as 'not trading partner' (consume an endpoint entitlement)

From the Resources menu, select Connections.
-or-
Within an integration, navigate to the Connections tab.
Locate the FTP connection open its Actions menu on the far right. Select Mark as not trading partner.
A confirmation message listing the FTP connection(s) that will be marked appears. Click Confirm to proceed.

Note: Beginning with the February 2022 integrator.io release, connections to the integrator․io API are no longer counted as part of the endpoint entitlement calculation. Previously if your subscription was consuming all available endpoints, you could be prevented from certain operations that required special use of the integrator.io endpoint (for example, cloning some templates and integration apps, and accessing flow errors via integrator.io error APIs). Now that it is no longer counted, these issues will not occur.

Related articles