Skip to main content
Question

Webhook payload not being processed correctly

  • December 31, 2025
  • 0 replies
  • 22 views

I’ve created a Zap to expose a Catch Raw Hook webhook to then ultimately send an email with the attachment from the webhook payload. Going from the webhook directly to Gmail wasn’t working for me, so I’m trying to upload to GDrive instead so I can see what the output is like.

These are some of the fields coming through from the webhook:

Data from webhook

The attachment is a PNG file, and the header is set as such. You can see the PNG chunk details in the data - PNG, IHDR, IEND etc. along with the binary data.

I tried writing this directly to GDrive as a PNG file. It creates a file of some sort, but cannot be opened as a PNG. So I tried writing it to GDrive as a .bin file instead and then downloaded and opened in TextEdit to see the content - it looks like it does in Zapier:

bin file from Zapier in TextEdit
​​​​​

If I open a legit PNG file with TextEdit then it looks a little different. It still has the PNG chunk markers but the binary data is totally different:

Legit PNG file in TextEdit

So my guess is that the raw data from the webhook as actually being interpreted as ASCII/UTF-8 rather than as actual raw data, even though the header is set to image/png

Has anyone else seen this issue? Is there a way to fix it?

Thanks in advance!