Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Zapier offers a relatively unique run-time environment for your integration and its requests to your API. The environment is stateless and restricts both execution time and payload size to offer normalized reliability and running time. There are three distinct contexts of this run-time that your integration will need to consider.
zapier-platform logs (or deprecated zapier logs) command.
| Time Limits | |
|---|---|
| Zap editor test step: request(s) + scripting | 30 seconds |
| Polling trigger: request(s) + scripting | 30 seconds |
| REST Hook trigger: ingest and payload processing scripting | 30 seconds |
| Create/search action: requests(s) + scripting | 30 seconds |
| Size limits | |
|---|---|
| Deduplication table | 105,000 rows per Zap |
| Custom fields | 1000 |
| Webhook payload | 10 MB |
| Trigger/Action input payload | 6 MB (35 MB with v17.2.0+) |
| HTTP response payload | 20 MB |
| Downloaded files | ~120 MB |
File inputs are handled via dehydration when passed between Zap steps, meaning the actual file contents don’t count against the Trigger/Action input payload limits. Files are referenced by URL and fetched as needed by the receiving action.
| Throttles | |
|---|---|
| Polling trigger | Default: 100 new items/poll |
| REST Hook trigger | 10000 webhooks/5 minutes |
| 30 webhooks/second | |
| More on throttles here. |
| TCP/IP | |
|---|---|
| Integration assigned IP | AWS-East |
Was this page helpful?
Suggestions