What we do
Tools
Industries
Department
How we workLet's talk →
Home/Zapier/Zapier Webhook Setup
Zapier

How to Use a Zapier Webhook: Catch Data In, Send POST or GET Requests Out

When the app you need isn't in Zapier's directory, Webhooks by Zapier is the way in or out. A Catch Hook trigger gives you a URL that starts the Zap when something sends data to it. POST, GET, PUT and Custom Request actions call any URL you give them. One thing first: it's a premium app, so it isn't on the Free plan.

Which webhook step you need

Another app should start the Zap: use Catch Hook. It parses the incoming body into fields. Use Catch Raw Hook if you need the body untouched plus the headers.

The other app can't send webhooks: use Retrieve Poll, which has Zapier check a URL for new entries with a GET request.

The Zap should send data somewhere: use POST (or PUT to update), GET to fetch, or Custom Request for PATCH, DELETE or a raw JSON body.

Plan: Webhooks by Zapier is on Professional, Team and Enterprise.

Catching a webhook in Zapier

  1. 1

    Add the trigger

    Trigger Webhooks by Zapier Event Catch Hook

    Click Continue. If the sender wraps what you need inside a larger object, enter that key in Pick off a child key so only that part comes through.

  2. 2

    Copy your webhook URL

    On the Test tab, Zapier shows a unique URL. Copy it and keep it private: anyone who has it can start the Zap.

  3. 3

    Paste it into the sending app's webhook settings

    Add a new webhook in the other app, paste the URL, choose the events to send and save.

    Watch for: apps that ask for a response to confirm the URL. Zapier always replies with a standard 200 and the reply can't be customized, so a sender that expects a handshake won't be satisfied.

  4. 4

    Send a real event and test

    Create a test record in the other app, then click Test trigger. Zapier splits the payload into fields you can map in later steps. If nothing arrives, send a fresh event and check the URL was saved exactly.

Sending data out with POST or Custom Request

  1. 1

    Pick the action event

    Action Webhooks by Zapier Event POST

    Use POST for most sends. Choose a payload type: Form, JSON, XML or Raw.

  2. 2

    Fill in the URL and data

    Map fields into Data as key-value pairs. A double underscore makes a nested object, so item__price becomes {"item": {"price": ...}}. Leave Data blank and Zapier sends every field from the previous step.

  3. 3

    Add authentication

    Use Basic Auth for a username and password or API key, or add an Authorization header with a token.

    Watch for: the token's expiry date. Zapier won't refresh it for you.

  4. 4

    Switch to Custom Request when POST falls short

    Custom Request handles PATCH and DELETE, deep nesting and empty values. You write the raw body yourself, so check the JSON is valid. It can't send files.

Why a Zapier webhook stops working, or works too well

One request ran the Zap twenty times

How you'll know: Task usage jumps and Zap history shows a burst of runs from a single delivery.

Fix: The sender posted a JSON array, and Catch Hook runs the Zap once per object in it. Pick off a child key, or use Catch Raw Hook and split the array yourself.

The sender thinks everything worked

How you'll know: The other app shows the webhook as delivered, but a later step in the Zap failed.

Fix: Zapier replies 200 as soon as it receives the request, before the steps run. Check Zap history, and turn on Autoreplay so errored runs are replayed.

A Zap you switched off is still being called

How you'll know: The sender keeps posting to the old URL.

Fix: An off or deleted Zap returns 404, but that can take a few hours to start. Remove the webhook in the sending app too.

Anyone could be triggering it

How you'll know: Runs show up that don't match anything in the sending app.

Fix: Catch Hook doesn't check who sent the request. If the sender signs its payloads, use Catch Raw Hook to get the headers and check the signature in a code step before anything acts.

A big payload never arrives

How you'll know: Small events trigger, large ones don't.

Fix: Triggers accept up to 10MB, Catch Raw Hook up to 2MB including headers, and actions 5MB. Send a file link instead of the file.

Questions people ask

What is Webhooks by Zapier?

A built-in Zapier app for talking to anything that speaks HTTP. Its triggers (Catch Hook, Catch Raw Hook, Retrieve Poll) start a Zap from an incoming request or a polled URL. Its actions (GET, POST, PUT, Custom Request) send requests out.

How do I catch a webhook in Zapier?

Add a trigger, choose Webhooks by Zapier and the Catch Hook event, and copy the URL from the Test tab. Paste it into the other app's webhook settings, send a test event and click Test trigger. The steps above have the detail.

Is Webhooks by Zapier a premium app?

Yes. It isn't available on the Free plan. You need Professional, Team or Enterprise.

What's the difference between a Zapier webhook and the Zapier API?

A webhook step lives inside your own Zap and sends or receives HTTP requests as part of your workflow. Zapier's developer platform is for software companies publishing an app into Zapier's directory, or building a private app when you need more authentication options than Webhooks by Zapier offers.

Does Zapier verify that a webhook actually came from who it claims?

No. A Catch Hook URL accepts requests from anyone who has it. If the sender signs its requests, you have to check the signature yourself, or put a verified endpoint in front of Zapier.

Can Custom Request handle OAuth2 authentication?

It can send an OAuth2 access token in a header, but it won't refresh the token when it expires. Built-in authentication is Basic Auth only. For anything more, Zapier points to building a private app on its developer platform, or the connection is built outside Zapier.

Why did my Zapier webhook stop working with no error shown?

Common causes: the sending app changed its payload so mapped fields are now empty, an access token in a Custom Request header expired, the webhook was removed or re-created in the sending app with a new URL, or the Zap was switched off. Zap history shows each run and what it received.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.