Zap step setup and testing using the Zap editor
Zap startup - turning a Zap on
Zap step execution when a Zap runs

The following pages describe the operating constraints of these run-time modes, the errors your integration users could run into, and best practices. Developers in the Platform CLI development environment and those using Code Mode in the Platform UI will find these pages most relevant. Many errors can be viewed in your integration’s log monitoring in the Platform UI, or if using the Platform CLI, by using zapier-platform logs (or deprecated zapier logs) command.

Important Zapier constraints summary

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

Note: 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

Need help? Tell us about your problem and we’ll connect you with the right resource or contact support.

Add an instant trigger using REST Hooks in Zapier Platform CLI Troubleshoot trigger timeouts

⌘I

​Important Zapier constraints summary

Important Zapier constraints summary