Zapier Catch Hook Not Picking Receiving Tests in Template Builder

Question

I have been able to successfully test a Zapier Webhook Trigger when building a “Zap”. But when I attempt to test the same Zapier Webhook setup in the template builder none of my postman requests get through. Anyone else having this issue?

sample data:

curl --location --request GET 'https://hooks.zapier.com/hooks/catch/10099658/blahblahblah' \

--header 'Content-Type: application/json' \

--data-raw '{

"title": "this is my title",

"Description": "this is the description we are going to use",

"Date": "10/jun/2021"

}'

icon

Best answer by Zane 16 June 2021, 19:11

View original

Zane · Accepted Answer

Ah ha!I understand what y’all are asking now. Sorry, took me a bit to connect on it.The Zap Template builder relies on the static sample data you provide when you develop your triggers and actions. It does not make a live request for data at all, or spin up an actual listener to wait for hook messages like the real Zap editor does (only if you don’t configure performList - which you should always do).The user interfaces look the similar, but what you’re building is different than a real Zap. It’s a template for other users to create actual Zaps, with settings and auths specific to their accounts. So everything you configure has to be totally common to all users. Note that the Zap Template creator doesn’t allow you to configure a connected account, which is something necessary to even access your API or other APIs.That’s the purpose of the static sample object - to provide a “contract” for the data available for field mapping that’s going to be there every time a Zap runs, for any and all users who make Zaps out of the template.For this reason making a template or even a shared Zap with a Webhooks by Zapiertrigger isn’t supported today.

Zane · Answer

When you say “template builder” - which tool do you mean? The Zap Template builder?

In order to test your rest hook trigger, you’ll need a real Zap running to do it. When a user enables a Zap that uses a rest hook trigger, we turn on an endpoint to listen for incoming hook messages to forward to your Trigger’s perform handler. Each endpoint is unique to the Zap. If a Zap is not enabled there’s not going to be anything listening for messages.

So I think what you’re seeing is somehow going to be an outcome of this. To test make sure you are testing with an enabled Zap.

Sign up

Use your Zapier credentials

Log in to the Community

Use your Zapier credentials

Scanning file for viruses.

This file cannot be downloaded