• 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 logs command.

​
Important Zapier constraints summary

Time Limits
Zap Editor test step: request(s) + scripting30 seconds
Polling trigger: request(s) + scripting30 seconds
REST Hook trigger: ingest and payload processing scripting30 seconds
Create/search action: requests(s) + scripting30 seconds
Size limits
Deduplication table105,000 rows per Zap
Custom fields1000
Webhook payload10 MB
Trigger/Action input payload6 MB (35 MB with v17.2.0+)
HTTP response payload20 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 triggerDefault: 100 new items/poll
REST Hook trigger10000 webhooks/5 minutes
30 webhooks/second
More on throttles here.
TCP/IP
Integration assigned IPAWS-East
Need help? Tell us about your problem and we’ll connect you with the right resource or contact support.