Fix: Zapier webhook not working

    A Zapier webhook usually fails because the hook URL, HTTP method, payload, authentication, or Zap publication state is wrong. I use this diagnostic order to isolate the failure.

    Last updated 2026-11-10~6 min read
    ZapierWebhooksHTTPJSON

    Last updated: 2026-11-10 · Approximately 5 min read

    Symptoms — what you're seeing

    • You send data to a Zapier webhook URL, but the Zap does not trigger
    • The Zapier editor test works, but live requests never appear in the Zap
    • Zapier shows an empty sample, missing fields, or an error when you test the webhook
    • Your sending system reports a failed request, timeout, or non-success HTTP response
    • The webhook worked before, then stopped after the Zap was edited, duplicated, or replaced

    If you have already spent 30 minutes checking the URL and payload, book a 30-min scope call. I will inspect the request path and tell you whether the fault is in Zapier or the sending system.

    Why this happens

    A Zapier webhook has two separate failure points: the request must reach the correct Zapier trigger URL, and the Zap must be turned on and able to process the received data. I check them in that order.

    1. The webhook URL is wrong or stale. A Zapier Catch Hook URL belongs to a specific Zap trigger. Copying a URL from another Zap, using a test URL after replacing the Zap, or leaving whitespace in an environment variable sends the request somewhere else. The sender can still report a successful HTTP request while the intended Zap receives nothing.

    2. The request uses the wrong HTTP method. A webhook trigger configured to receive a POST will not behave like a browser GET request. Opening the URL in a browser is not a valid test for a POST-based webhook. The method, URL, and request body must match the trigger and the sending application.

    3. The payload is not valid or does not contain the fields the Zap expects. Zapier can receive a request but produce an empty or unusable sample when the body is malformed, nested differently from the test payload, or sent with the wrong Content-Type. Later steps can then fail because a mapped field is missing.

    4. The Zap is off. Testing a trigger in the editor does not publish the Zap for live traffic. The Zap must be switched on after the trigger and action steps are configured.

    5. Authentication is being sent to the wrong place. If the receiving endpoint requires an API key, bearer token, Basic Auth, or a signature header, put it where that endpoint expects it. A token in the JSON body does not authenticate a request that expects an Authorization header. For a standard Zapier Catch Hook, the unique hook URL is the routing credential; do not add invented authentication requirements to a basic test.

    6. The sender is not accepting Zapier's response. A custom integration, n8n HTTP Request node, or application may treat a timeout or non-2xx response as failure. Check the sender's response log instead of assuming that a request was accepted because the code executed.

    The fix, step by step

    1. Confirm the trigger type. Open the Zap and identify whether the trigger is a Webhooks by Zapier event such as Catch Hook, Catch Raw Hook, or a webhook action. Do not troubleshoot a trigger URL as if it were an outbound webhook action.
    2. Copy the current webhook URL from the Zap. Copy it directly from the trigger step and replace the URL stored in the sending system. Check for a hidden space, a line break, a truncated environment variable, or a URL copied from a different Zap. Treat the value as a secret because anyone with the hook URL can submit data to it.
    3. Send a deliberate POST request. Use a real test payload with the same field names that production will send. Replace the bracketed URL below with the current URL copied from your Zap; it is an explicit placeholder, not a value to send literally:
      curl -i -X POST "[PASTE_CURRENT_ZAPIER_CATCH_HOOK_URL]" \
        -H "Content-Type: application/json" \
        -d '{"event":"webhook-test","contact":{"email":"test@example.com"},"source":"manual-curl"}'

      Use a real test address that you control. Do not send a customer's personal data while diagnosing the hook.

    4. Check the trigger's test data. Return to the Zapier trigger step and run the test or refresh the sample. Confirm that the request appears and that the fields are individually available. If the request arrives as one raw string, the sender's content type or body format does not match the selected trigger.
    5. Turn the Zap on. Save the Zap, publish the latest changes, and confirm the live status is on. A successful editor test does not mean the production Zap is active.
    6. Inspect Zap History. Look for the exact time of the test. No history entry means the request did not reach this Zap or used a different URL. An entry with an error means the webhook reached Zapier and the failure is in parsing, field mapping, authentication, or a later action.
    7. Compare the live payload with the tested payload. Check the HTTP method, Content-Type, JSON structure, field names, and authentication headers. A test with email at the top level does not prove that a live payload with contact.email will map to the same field.
    8. Test the next action separately. If Zap History shows the webhook trigger succeeded, the webhook is working. Open the failed action and inspect its input, API response, status code, and required fields. Fixing the downstream app is a different task from fixing the webhook trigger.

    Still blocked? Book a 30-min scope call and I will trace the request from the sender through Zapier's trigger history. You can also email Basit with the HTTP status, timestamp, and redacted payload.

    Common variations

    • "Zapier webhook URL not working" — copy the URL again from the current trigger step. A URL from a duplicated, replaced, or different Zap will not populate the intended Zap's history.
    • "Zapier webhook trigger not firing" — verify POST versus GET, send the request while the trigger test is listening, then check Zap History after the Zap is switched on.
    • "Zapier webhook authentication failed" — inspect the exact header or query parameter required by the receiving endpoint. For a Catch Hook trigger, first prove delivery with the unique hook URL and a simple JSON POST before adding custom authentication.
    • "Zapier webhook response is empty" — distinguish the trigger from a webhook action. A trigger receives data for a Zap; a webhook action makes a request to another service and its response depends on that service's endpoint and response body.
    • "Zapier webhooks free" — Zapier's help center lists Webhooks by Zapier as available on the Professional, Team and Enterprise plans, not the Free plan (How to get started with Webhooks by Zapier). If the account is on Free, fix the plan before debugging the request. Plan availability can change, so check that page for the current list.

    When this isn't the issue

    If the request appears in Zap History, stop debugging the URL. The webhook reached Zapier. Continue through these forks:

    • The trigger succeeds but a later action fails: inspect the action's mapped fields, authentication, response body, and HTTP status. The fault is in the destination app or its request configuration.
    • The request reaches Zapier but fields are missing: compare the production JSON structure with the sample used to configure field mapping. Update the sample, then remap fields that moved or were renamed.
    • The sender times out while Zapier records the request: the sender's timeout or retry policy is the problem. Add idempotency handling before enabling retries so one business event does not create duplicate Zap runs.
    • Only some requests fail: compare the failing payloads for missing required fields, invalid encoding, oversized values, or an authentication header that changes between environments.

    Related pages

    Need this workflow customized or debugged? Book a 30-min scope call →

    Stuck configuring this workflow?

    I build and fix n8n workflows for agencies and SaaS teams. 30-minute scope call — bring the problem, leave with an estimate.

    Related pages