Skip to main content

We have a simple three-step Zap that’s causing a dehydration problem. The specific error is this:

This Webhooks by Zapier (1.0.18) step hit an error
Oops! You passed too much data (49707 bytes) to your dehydration function - try slimming it down under 12000 bytes (usually by just passing the needed IDs).

 

The steps are simple: Gmail Message Trigger → Delay for an hour → Webhook posts some of the values from the email.

The issue is that the delay seems cause the dehydration/hydration and there’s too much data in the email message. I’ve tried extracting just the three fields I need from the message using the Formatter step and using those for the Webhook but that doesn’t work either, probably because I need to pass in the body and it is larger than the limit of 12K bytes.

Any suggestions to working around this?

Hi ​@BrianVallelunga 

For us to have more info, post these screenshots:

  • how your Zap steps are outlined
  • how your Zap steps are configured in EDIT mode with the field mappings visible
  • the encountered error for the Zap step

Here’s the overall flow

 

The three formatter steps just trim one field each:
 

 

The webhook POST uses the trimmed values from the formatters and maps to JSON:.

 


@BrianVallelunga 

Help links for using Webhooks in Zaps: https://zapier.com/apps/webhook/integrations#help

Make sure you are using the most updated version of the Webhooks by Zapier Zap app.

You may want to try opening a ticket with Zapier Support: https://zapier.com/app/get-help

 


Thanks for the guidance, but this doesn’t really address the issue. I’ll open a support ticket.


Hey there, ​@BrianVallelunga 👋

Sorry to hear your Zap is running into “You passed too much data...” errors. I can see our Support team identified that you’re running into a bug with the Webhooks app. We can’t give any estimate as to when it will be resolved but they’ve added you to the list of folks being affected by this which will ensure you get an email notification as soon as it’s resolved.

Let us know if there’s anything else I can help with, and thanks for your patience in the meantime. 🙏


Hi all, just circling back in here to share that the bug has been fixed! 🎉🎉🎉

Thanks so much for bearing with us while the team worked on getting it sorted. As Zaps should no longer be getting those “You passed too much data...” errors, I’ll be closing out this topic now.

If you continue to see any errors or run into further issues, please start a new topic in the Community here or contact Support directly. In the meantime, happy Zapping! ⚡️