Zap isn't receiving webhooks

1. Try to load samples

In the Zap editor, after you’ve started building your Webhooks Zap, the Zap immediately starts listening for webhooks being sent to that URL. Even before you turn your Zap on, Zapier stills track the data that URL receives, to make it easier for you to debug.

You can see those payloads at the end of the Webhooks step by clicking to pull in samples. Here's how to make sure you see the new payloads:

1. Create your Zap and copy your webhook URL
2. Outside of Zapier, go into the app that you want to send the webhook to the Zap
3. Take the action that will trigger a webhook (usually, that’s creating a record)
4. Return to Zapier and click to load in sample webhooks at the end of the Webhooks step.

Tip

Even if you’ve done the action that would trigger a webhook before, you’ll need to do it again after you’ve started building the Zap to get a new webhook pulled in!

Do you see the new values coming in? Great! You can finish editing your Zap and enable it.

If you don’t see the samples, then we need to do a little more debugging. Let's try the next step.

2. Generate your own request

To determine whether the issue is with the Zap, the third party app, or the data being sent, you can trigger a Zapier webhook on your own. There are a few tools that help you do that (for example, curl) but we generally recommend an app like Postman.

If you’re using Postman for this, enter the webhook URL from the Zap into Postman, and choose the POST option. Note that Zaps work best with JSON payloads.

If you’re using curl or hurl.it, you’ll also want to use a POST request with a JSON payload. Here’s a quick curl example to get you started:

curl -v -H "Accept: application/json" \
    -H "Content-Type: application/json" \
    -X POST \
    -d '{"first_name":"Bryan","last_name":"Helmig","age":27}' \
    https://zapier.com/hooks/catch/n/Lx2RH/

After attempting to send that request through Postman or another app, go back to the Zap, and try loading samples again.

If the webhook you sent does show up, that confirms the Zap is working properly, which means the third party app that you originally tried isn’t working well with the Zap.

You’ll want to go back into the third party app, and check the configuration there to see what may be keeping that from going through properly. If you’re not able to determine what’s keeping that from going through properly, move on to the next step.

3. Inspect the request data

Next, you’ll check if the webhooks are actually getting sent, and if so, what format they might be in. For that, we will step out of Zapier completely - we recommend an app like this one. Unlike Zaps, it doesn't try to interpret the payloads, it just prints them to your screen as it receives them, making it easy to see what is going on. To use this site:

• Copy the URL you are given as your Unique URL.
• Go to your third party app that you’d like to send webhooks to trigger the Zap.
• Paste that Unique URL into the URL field for webhooks in your third party app (replacing the URL you got from Zapier).
• Still in your third party app, take the steps necessary to trigger the webhook once again (usually creating a record).
• Finally, go back to your webhooks testing site page, and refresh to show new data.

If records show up: This means Zapier is getting the webhooks, but couldn't interpret the data included in them.

To fix this, you should contact our support team and send us the data that came into the webhooks testing site or, if you are a programmer, you can always try parsing the payload yourself via our Developer Platform.

If records do not show up: This means the app isn't sending the webhook data at all! Usually this means that app may not have webhooks enabled for the records you’d like to send. Alternately, sometimes you may need to check another checkbox within the app, or reconfigure it somehow.

To fix this, we recommend contacting the third party app first, to make sure your webhook setup is correct.