Skip to main content

I am having lots of difficulty testing webhooks in zapier due to “Find new records” rarely working as expected, as well as, data hydration that prevents me from verifying output and often cannot be rehydrated.


I send a webhook, click “Find new records” there is the output. I make a change and send the webhook again, click “Find new records”… nothing new. This goes on for long periods then suddenly works 2 more times, then stops working again. I know the webhook was sent, why wont zapier show it to me. Testing is not the time to be hiding things.

Why would zapier dehydrate when it knows the output will be too large to hydrate?

Hi ​@slejeune 

Help us have more info by posting screenshots about what you are referring to.

Are you using a Zap trigger step?

Are you configuring a Zap app integration using the Zapier Developer Platform?


I am attempting to use the webhooks by Zapier block to catch a hook sent from looker. I sent a test hook with many entries yesterday, the 2nd, I saw it in requests C-J. I sent another test hook and it never found any more new records. I also sent a new one, with todays data, and it still has not been received here. This is while editing a zap and using the test portion of the catch hook action.


@slejeune 

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

There is built in deduplication for Zap webhook triggers.

Try appending a UNIX timestamp to be used to make each request unique.


Ok, that explains the first time it doesnt work.

When I send data on subsequent days, it is certainly a different data set, the data changes, the dates change, etc. So why am I not seeing any inbound webhooks here for the past 2 days, after sending several unique data sets? Enforcing this sort of thing during TESTING is also a bit of a bad idea, during TESTING it is important to see everything that occurs.


Hi ​@slejeune,

 

To ensure a smooth testing experience, verify that your webhook URL is correctly configured and error-free. Check Zapier's task History to confirm if the webhook is triggering, and review logs or filters that might be blocking incoming data. Ensure your testing environment mirrors production closely, and temporarily turn off filters if necessary. Look into potential rate limits that may affect webhook reception, and confirm that the data format aligns with your Zap'sZap's configuration to prevent silent failures. If issues persist, providing more setup details or contacting Zapier Support can help pinpoint the problem.