What is the maximum payload size for a Zapier webhook?
Zapier's documentation says the maximum webhook payload is 10MB for webhook triggers and 2MB for Catch Raw Hook. Anything larger is rejected, so a sender that posts whole files or long histories must be changed to send less.
The number matters because a payload that works in testing with one small record can fail in production with a batch of records or a long text field. Here are the limits, the reasons they bite, and how to design a flow that stays under them.
What counts toward the limit?
The whole request body counts, including every record in an array and every field's text. Headers are passed through with the Catch Raw Hook but the body limit still applies to the body.
A sender that posts a batch of 500 contacts with notes can exceed 2MB quickly, even though each contact is small. The Catch Hook (parsed) allows 10MB, so the choice of hook changes the limit as well as what Zapier does with the data. Check the sender's typical payload with a real export, not a single test record.
What happens when a payload is too big?
The request is rejected, so the Zap does not run for that event. The sender may retry, and it may not show an error on its side. A rejected payload is therefore a silent loss unless you watch for it.
Ask the sender for its error log or response code. A flow that runs for small records and fails for large ones usually shows exactly this pattern. Fix it in the sender where possible: send one record per request instead of a large batch, and leave out fields the flow does not use.
How do you design a flow that stays under the limit?
Send only the fields you use, send one record per request where you can, and split large batches on the sender side. Keep the heavy processing inside the flow, not in the payload.
- Trim the payload. A lead needs a name, phone, email, source and the record ID. It rarely needs the full notes history.
- Split batches. A sender that can post an array can often post smaller arrays. Zapier starts one run per object, so smaller arrays give you the same runs with less risk.
- Store large content elsewhere. Send a link to the file or record, not the file itself.
- Move heavy flows to n8n. n8n's webhook default is 16MB, and self-hosted n8n can raise it. A flow that needs large payloads or long processing is often better there; see our n8n automation service.
How does this affect the cost of a Zapier flow?
Payload size does not change the task price directly, but a flow that is split into many small requests runs more often, and each successful action step still counts as a task.
Count the actions in the flow and the number of records per month before you decide how to split a batch. The Zapier pricing guide has a worked example, and the cost calculator compares Zapier and n8n on the same volume.
Related questions and services
- What is a Zapier Catch Hook?
- How do you set up an n8n webhook?
- Why is my GoHighLevel inbound webhook not firing?
- Zapier pricing in 2026: what a real business pays each month
- Zapier vs n8n cost calculator
- API integrations
Sources and further reading
- Zapier help: Catch Hook (webhooks) (10MB trigger and 2MB Catch Raw Hook limits, checked 2026-10-04)
- n8n documentation: Webhook node (16MB default, self-hosted setting, checked 2026-10-04)
These limits are vendor documentation at the time of writing. Confirm them on the current pages before you design a flow around them.
