Your account is allowed a certain number of entitlements, such as “active” integration flows, according to the limit set under your integrator.io subscription plan. An account owner or administrator can view a running total of these entitlements and the maximum values allowed in the account’s Subscription tab.
Key concepts
Production [or Sandbox] entitlements are the maximum values of each category, according to your subscription. Each category is gauged separately; no tradeoffs between categories are permitted. An account’s entitlements are categorized as follows:
- Endpoint apps describe a prebuilt connection to a “named” app; a prebuilt connection to a database; or a universal technology service connection, such as HTTP, REST API, and FTP. The endpoint is included in the count only if it is being used in an active flow.
-
Integration flows are currently active – meaning enabled or “On”
– and counted within a production environment, whether custom developed, installed from a template or other downloaded integration, or cloned; real-time or scheduled.
- Data loader flows are unlimited and do not apply toward your entitlements.
- All flows in an Integration app are included in the app’s subscription and therefore do not count against your account’s entitlements, even though active flows’ connections do appear in the endpoint apps total.
- Trading partners are designations that apply to an FTP or AS2 connection, typically for external B2B EDI transactions. They are tallied by identical server name or IP address, even if you mark additional connections to that FTP server as a trading partner.
- On-premise agent is a software program that runs on your server, typically behind the firewall and within the same network as the systems you want to connect to. The number of agents you’ve installed in your account is shown at Resources > Agents, and only those agents used in active flows count toward your entitlements.
You will receive an error message if you try to exceed any of your production entitlements. (An exception is for free account holders within their 30-day unlimited period.)
Flow builder clearly indicates at the top right when a flow is turned on: .
When you view all of your account’s integrations at the Home page, the summary value (such as “4 Flows,” below) indicates the number of active flows. The total number of flows could be much larger.
If you want to view all of the flows in an integration and toggle them on or off individually, select the integration from your Home page tile or list view:
The sums of the trading partners, agents, and total production entitlements are straightforward and relatively easy to reduce or increase. However, endpoint apps require further clarification, so that you can understand the calculations and adjust your account’s flows and connection resources to comply with the total amounts allowed for your current subscription.
How to calculate endpoint apps
The term “endpoint app” may be more familiar to integrator.io customers as a “connector” or an “application.” When installing an Integration app or template, one of the first steps is to set up the connections to the applications. And when creating an export or a connection resource, you are always required to select a value from the Application list, in one of three sections:
- Connectors, such as Acumatica and Salesforce, commonly referred to in Celigo documentation as “prebuilt” or “branded” connectors for “named apps”
- Databases, such as MySQL and Snowflake, often called “data warehouses”
- Universal connectors, such as FTP and HTTP, also known as “custom,” “generic,” or “technology services” connections
Endpoints are the sum of these three app connections.
- Webhooks are not considered endpoints because they are used to send an HTTP POST message over the web in real-time to an endpoint when an event occurs in an application, rather than as a destination for data.
- Data loader flows are not considered while counting endpoints.
You can trace the current endpoints by looking at each connection’s context within your account:
- Locate the connection within any of the lists in the Celigo platform:
- Resources menu > Connections
- The Connections tab of your integration
- The Connections tab at the bottom of Flow builder
- From the Actions overflow (...) menu, select Used by.
- Scroll to any flows entry, and click the link (more conveniently to a new tab) to see if the flow is active.
Named app connector totals
You are free to create as many connections to a named app as you like, and they are all considered to be a single “app.” These connections increment your endpoint app count when any of them is referenced in an active flow.
Example A
- Two NetSuite connections in the production environment
Total: 1 endpoint app
Example B
Two NetSuite connections with different account IDs/URLs
- One NetSuite connection with account ID: 113156
- One NetSuite connection with account ID: 668910
Total: 1 endpoint app
Example C
- One basic auth connection to Acumatica
- One OAuth 2.0 connection to Acumatica
Total: 1 endpoint app
Example D
- Three Shopify connections for three Shopify stores
Total: 1 endpoint app
Database connector totals
Multiple integrator.io connections configured for the same relational database management system (RDBMS) (except Google BigQuery) with the same host (domain or IP) count as a single endpoint. Your existing Google BigQuery connections count endpoints by client email.
In non-RDBMS systems, like DynamoDB, any integrator.io connection configured to the same AWS Access Key ID counts as a single connection. Your connections are added to your endpoint app summary when any of them is referenced in an active flow.
Your existing database connections are counted as one if they’re hosted on the same host server. In these cases, only one endpoint is consumed, and you can connect to more databases without defining the database.schema.table in all queries. You only consume one endpoint if you connect to more than one dataset under the same projectId. This way, you won’t go over the maximum number of endpoints when you create a new database connection on a single host server.
Relational Database Management Systems (RDBMS):
Example A – MySQL
- Two MySQL connections to host mysql.yoursql.io
Total: 1 endpoint app
Example B – MySQL
- Two MySQL connections to host mysql1.yoursql.io
- One MySQL connection to host mysql2.yoursql.io
Total: 2 endpoint apps
Example A – Snowflake
- Two Snowflake connections to account name https://<AccountName>.snowflakecomputing.com
Total: 1 endpoint app
Example B – Snowflake
- Two Snowflake connections to host https://<AccountName1>.snowflakecomputing.com
- One Snowflake connection to host https://<AccountName2>.snowflakecomputing.com
Total: 2 endpoint apps
Non-relational Database Management Systems (non-RDBMS):
Example A – DynamoDB
- Two DynamoDB connections with Access key ID 2304983904.
Total: 1 endpoint app
Example B – DynamoDB
- One DynamoDB connection with Access key ID: 2304983904.
- One DynamoDB connection with Access key ID: 0000000000.
Total: 2 endpoint apps
Example A – Amazon Redshift
- Two Amazon Redshift connections with the same cluster and region.
Total: 1 endpoint app
Example B – Amazon Redshift
- Two Amazon Redshift connections with the same cluster and region.
- One Amazon Redshift connection with a differing cluster and region.
Total: 2 endpoint apps
Universal connector totals
Text comparison determines how integrator.io identifies additional connections to the same endpoint:
- GraphQL, HTTP, and REST API (of all auth types) – Multiple connections to one of these three options are counted as a single endpoint app as long as the Base URI is identical
- AS2 and FTP (including SFTP and FTPS, internal or external) – Multiple connections configured for the same server (domain or IP) and port are counted as a single endpoint
- Wrapper – Each wrapper resource (essentially a custom connection to a server stack) used in an active flow is counted as a single endpoint
The universal connector count is also added to your endpoint app summary when any of them is referenced in an active flow.
Important: The URL comparison is case-insensitive, but it is otherwise very precise. The base URIs https://my-app-host.com/api/ and https://my-app-host.com/api/v3 for a token-based universal HTTP connection are not identical and will be counted separately. In most cases, you can simplify the base URI, adding Relative URI portions of the full path in the connection or flow steps, thereby reducing the endpoint app total.
Example A
- One basic auth HTTP connection to base URI https://my-app-host.com
- Three OAuth 2.0 HTTP connections to base URI https://my-app-host.com
Total: 1 endpoint app
Example B
- Two HTTP connections to base URI https://my-app-host.com/api/
- One HTTP connection to base URI https://api.my-app-host.com/
Total: 2 endpoint apps
Example C
- One universal HTTP connection to base URI https://api.fieldaware.net
- One prebuilt (“named app”) connection to FieldAware
Total: 2 endpoint apps
Example D
- Two FTP connections to host ftp://ftp.my-app-host.net
Total: 1 endpoint app
Example E
- One FTP connection to host ftp://ftp.my-app-host.net
- One FTP connection to host ftp://ftp.my-app-host.net/
Total: 2 endpoint apps
Tip: You may have opportunities to economize and reduce the number of endpoint app entitlements in examples B, C, and E, above. Be sure to have your account credentials – such as passwords and tokens – handy whenever you edit a connection.
Caution: Audit your account entitlements and make sure that your usage is within the maximum values that will be allowed before you make any changes to your subscription. For example, if you currently have five active endpoints and you reduce your limit to three endpoints, then two of those endpoints will be disabled when the new subscription takes effect, and the flows to or from those missing endpoint apps won’t be able to run.
Comments
0 comments
Please sign in to leave a comment.