Help for owners
The data Zapier receives from my webhook is missing fields or looks wrong
Short answer
A Zapier Catch Hook splits the request into fields when you click Test trigger, so the fields you see are those of the last test request. If fields are missing, the sender may differ from the sample, or the data may be nested. Catch Raw Hook returns the body unparsed.
Does this sound like your situation?
- The Zap shows only some of the fields I send.
- Fields I mapped are empty in live runs.
- Test data looks right but live data does not.
- The sender sends a list and the Zap runs many times.
- The webhook works in one system and not another.
Why does this happen?
Fields come from a test request
Zapier separates each field in your webhook data after you click Test trigger, so the field list reflects what that test request contained. A live request with different fields leaves mapped steps empty.
Confirmed by help.zapier.com
Catch Hook and Catch Raw Hook differ
Catch Hook parses the request body and suits most cases, accepting GET, PUT and POST. Catch Raw Hook returns the body unparsed with headers, and its payload limit is 2MB.
Confirmed by help.zapier.com
A list becomes many runs
An array of JSON objects in one request runs the Zap once per object. A sender that sends batches therefore creates many runs.
Confirmed by help.zapier.com
Size and rate limits
Zapier states a 10MB maximum payload for triggers, and that rate limits apply to Webhooks by Zapier, with heavy traffic delaying later steps.
Confirmed by help.zapier.com
The sender changed its format
A renamed or removed field in the sending system breaks every step that uses it, without any error at the trigger.
What can I do about it today?
- Look at one live requestOpen the Zap history, pick a live run and read the raw data it received.
- Compare it with the test sampleNote which fields differ in name, position or type.
- Ask the sender what it really sendsThe vendor or developer of the sending system should supply an example payload.
- Do not edit mapped steps in a hurryChanging field mappings in a live Zap can send wrong data to invoices or contacts. Copy the Zap and test on the copy.
- Keep one good exampleSave a working payload for later.
When should I bring someone in?
- The data feeds payments, invoices or customer records.
- You cannot see the sender's side.
- Payloads are large or arrive in bursts.
How do I handle it?
- Capture real payloadsI log actual requests from the sender and keep a few as reference.
- Define the expected shapeI write down which fields are required, optional or nested.
- Validate before usingA step checks required fields and routes bad payloads aside, instead of passing empty values on.
- Re-test after each changeThe sender's format is retested on every change, because Zapier's field list is rebuilt from a test request.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why does Zapier show fewer fields than I send?
Fields come from the test request you picked. Send a complete request, then test the trigger again.
Which hook should I choose?
Zapier recommends Catch Hook for most cases and Catch Raw Hook when you need the raw request data.
Does Zapier handle nested data?
The webhook article does not describe nested objects, so check how your data appears in a test before relying on it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.