See the supported connectors for Application Integration.
Quotas and limits
This document lists the quotas and limits that apply to Application Integration.
A quota restricts how much of a particular shared Google Cloud resource your Cloud project can use, including hardware, software, and network components.
Quotas are part of a system that does the following:
- Monitors your use or consumption of Google Cloud products and services.
- Restricts your consumption of those resources for reasons including ensuring fairness and reducing spikes in usage.
- Maintains configurations that automatically enforce prescribed restrictions.
- Provides a means to make or request changes to the quota.
When a quota is exceeded, in most cases, the system immediately blocks access to the relevant Google resource, and the task that you're trying to perform fails. In most cases, quotas apply to each Cloud project and are shared across all applications and IP addresses that use that Cloud project.
There are also limits on Application Integration resources. These limits are unrelated to the quota system. Limits cannot be changed unless otherwise stated.
Resource quotasThe following quotas apply to Application Integration resources per Google Cloud project:
|Resource||Quota||Value||Can be increased|
|Application Integration provisioning||Number of provisioning requests per day||20||No|
|Integration execution||Maximum concurrent executions per project||10||No|
|Maximum concurrent executions per integration||10||No|
|Maximum task executions per day||10000||No|
|Number of integration execution requests per minute||300||No|
|Integration Connectors||Maximum number of connections per region per project||5||Yes|
|Maximum number of nodes per connection||2||No|
|Number of read connection schema requests per minute||120||No|
|Number of read connection requests per minute||120||No|
|Number of read region requests per minute||120||No|
|Integration execution logs and monitoring||Number of read executions requests per minute||120||No|
(This page lists all the available integrations in your project)
|Number of read integration requests per minute||240||No|
|Integration designer page
(This page loads a whole integration including all the integration versions and configured task entities)
|Number of read task entity requests per minute||240||No|
|Number of read integration version requests per minute||480||No|
|Number of write integration version requests per minute||480||No|
|Authentication profiles page
(This page lists all the available authentication profiles in your project)
|Number of read requests per minute||120||No|
|Number of write requests per minute||120||No|
|Salesforce trigger||Number of read Salesforce channel requests per minute||120||No|
|Number of write Salesforce channel requests per minute||120||No|
|Number of read Salesforce instance requests per minute||120||No|
|Number of write Salesforce instance requests per minute||120||No|
Usage limitsApplication Integration enforces the following usage limits. Your are responsible for tracking and ensuring that the values stay within the prescribed limits. Exceeding the limits might lead to reduced throughput, task failures, and increased latencies when running the integration.
|Applicable to the entire Application Integration||Maximum characters in the integration name||64 characters|
|Maximum cumulative size of all the integration data (including input and output variables)||10 MB|
|Maximum cumulative size of all the integration data (including input and output variables) sent and received from connections||8 MB|
Timeout for synchronous (SYNC) integration executions
The timeout duration includes any external system calls or sub-integration tasks of the integration during its execution. Examples of external system calls include, calling external endpoints, calling Salesforce using connectors, and calling Google Cloud functions.
Timeout for asynchronous (ASYNC) integration executions
If your sub-integration takes longer than 2 minutes to run, consider executing your integration in ASYNC mode.
Maximum time till which an older version of the integration can run after publishing the new version (system consistency)
This is because Application Integration is a distributed system that provides eventual consistency. It uses caches throughout the system that may take time to clear and refresh.
Maximum tasks in an integration
If there is a need for more tasks, it is recommended that you split your integration into multiple integrations.
|Maximum versions allowed for an integration||100|
|Apps Script task||Maximum active deployments for an Apps Script||50|
|Queries per second (QPS) for API executables||5000 per minute|
|Queries per second (QPS) for Webapp deployments||5000 per minute|
|Latency for API executables||1.5 seconds|
|Latency for Webapp||2.5 seconds|
|Maximum cumulative size of all the integration variables in an Apps Script||15 MB|
|Call REST Endpoint task||Maximum number of concurrent REST calls||10|
|Maximum size of the response from the REST endpoint||10 MB|
|While Loop and For Each Loop tasks||Maximum cumulative size of data processed||50 MB|
|Maximum number of iterations||100|
|For Each Parallel task||Maximum cumulative size of data processed||10 MB|
|Maximum number of parallel executions||10|
Data processing limits
We don't recommend using integrations in the following scenarios:
- Integration requires movement of bulk data or focus on extract, transform, and load (ETL) processes.
- Cumulative size of all the integration data is greater than
10 MBduring execution.
When calculating the cumulative data size, add the size of all types of data such as input variables, output variables, and other intermediate task variables.
Request a quota increase
To increase or decrease most quotas, use the Google Cloud console. For more information, see Requesting a higher quota.