ZAPIER WEBHOOKS

Zapier webhook not triggering: Zap is not receiving webhooks

You built a Zap that starts with a webhook. The other app says it sent the data. Zapier shows nothing. Either Test trigger finds no record, or the Zap is switched on and never runs.

Zapier's own help page splits the cause in two. Either the app sending the webhook has wrong settings or is not sending at all, or the data arrives in a format Zapier cannot process. That gives you one question to answer: is the problem before Zapier, or inside it? The steps below answer it in the cheapest order.

Start with what you can see

The Test tab finds no record. Zapier is not receiving anything at that URL, or what it receives is not readable. Go to step 1.

The Zap is on but never runs. Same causes, plus the chance that the live event is not the event you tested. Check Zap history first. If there is no run at all, the request is not arriving.

Runs appear but the data is empty or wrong. The request is arriving. Format or field names are the problem, so go to step 3.

The checks, in order

1. Compare the two URLs. Open the webhook step in your Zap and copy its URL. Open the webhook settings in the other app and compare them character by character. Zapier lists this first: the URL in the Zap editor has to match the URL in the app. Our suggestion: if you ever duplicated the Zap or rebuilt the trigger, the new step may have a new URL while the app still points at the old one.
2. Check the request type. If the app sends a POST request, the Zap needs a Catch Hook or Catch Raw Hook trigger. If it sends a GET request, Zapier says to use the Retrieve Poll trigger instead. A mismatch looks exactly like silence.
3. Check the format. The payload must be XML, JSON or form-encoded. If the sender uses something else, Zapier cannot process it.
4. Check security on the sending side. Zapier notes that some services need Zapier's IP addresses allowed before they can send. It also says Webhooks by Zapier supports only basic authentication; if the API on the other end needs something stronger, the route is a custom app on the Zapier Developer Platform, which is a build job, not a setting.
5. Retest properly. Open your app in one browser tab and the Zap's trigger step in a second tab. In the app, do the thing that should send data, such as creating a record. Switch to Zapier, open the Test tab and click Test trigger. For instant triggers Zapier says to test straight after the event. If it missed, repeat the event and click Test trigger again. A record appearing proves Zapier can hear the app.
6. Send a request yourself. This separates the Zap from the app. Two ways, both from Zapier's page:
   • In Postman, make a POST request to the Zap's webhook URL with a small JSON, XML or form body, then click Test trigger in Zapier.
   • Or paste the webhook URL into a browser tab and add test values on the end, for example ?field_name=this_is_a_test_value. A working endpoint answers with a short message containing "status":"success". Then check Zap history, or retest the trigger.

   If your test request arrives, Zapier is fine and the sending app needs fixing: wrong URL, webhooks not enabled in that app, or an unsupported format. If it does not arrive, look at the URL and trigger type again.

7. See what the app really sends. Zapier suggests Webhook.site. Copy the unique URL it gives you, paste it into the app as the destination, trigger the event, and watch the page. If a request shows up there, the app is sending and Zapier probably cannot process the payload. If nothing shows up, the app is not sending, and only that app's settings or support can fix it.

What the results mean (our suggestion, built from the steps above)

How to know it is fixed

Do the real event once, not a test. Open Zap history. A new run with the real data in it is the proof. A passing Test trigger alone is not.

When to hand it over

Stop and get help if the sender needs advanced authentication, can only send in an unsupported format, or sits behind an IP allowlist you do not control. Those usually need a build or someone else's settings changed. A wrong URL or wrong trigger type is a quick fix.

If you'd rather have it fixed: $299 for one defined problem. We start with a diagnosis, and the $99 for that is credited to the fix. Tell us which Zap, which app sends the data and what should happen: tidewellsystems.com/#contact

Questions

Does Test trigger always find the record?

No. Zapier says to test straight after the event.

Can I use GET?

Yes, but with the Retrieve Poll trigger, not Catch Hook.

Is Webhook.site safe to use with real data?

Our suggestion: use a test record with fake values, since it is a public inspection tool.

Do I need to write code?

Not for the checks above.