What is a Zapier Catch Hook?
A Catch Hook is a Zapier trigger that gives you a unique URL. Another system sends a GET, PUT or POST request to that URL, and Zapier starts the Zap with the data it receives. It is the usual way to connect a tool that can send webhooks but has no native Zapier app.
Zapier offers two versions. The standard Catch Hook parses the request body into separate fields you can use in later steps. Catch Raw Hook passes the body unparsed and includes the request headers. Use the standard version for most flows, and the raw one when you need the headers or the body in its original form.
How do you get the Catch Hook URL?
Create a Zap, choose Webhooks by Zapier as the trigger app, pick Catch Hook (or Catch Raw Hook), and copy the URL Zapier shows. Paste that URL into the sending system and send a test request.
- Create a new Zap and search for Webhooks by Zapier in the trigger step.
- Choose Catch Hook for parsed fields, or Catch Raw Hook for the raw body and headers.
- Copy the URL from the setup screen. It contains your Zapier account ID.
- In the sending system, set the URL and the method. Zapier's Catch Hook accepts GET, PUT or POST.
- Send a test request, then use Zapier's "Find data" to load the sample so later steps can read the fields.
What does the URL do and how long does it last?
The URL is unique to the Zap. It changes only if the Zap is transferred to another account. Turning the Zap off makes the URL return a 404, and the change can take several hours to take effect.
Two practical points follow. A URL you paste into a live system stays valid as long as the Zap exists, so keep a record of which system uses it. And if you turn a Zap off for maintenance, the sending system will get 404 errors until it is turned back on. Plan a maintenance window rather than switching a live flow off mid-week.
How does Zapier handle more than one record in a request?
If the sender posts an array of JSON objects, Zapier triggers once for each object. A single request with twenty leads starts twenty runs.
That is useful for batch senders, but it also means one bad request can start many runs. Check the sender's batch size before you turn the Zap on. You can also point several Catch Hook URLs at different Zaps, so one event starts several flows, each with its own filters and actions.
When is a Catch Hook the wrong trigger?
A Catch Hook is best when the sender can push data. When you need to pull data on a schedule, or when the payload is larger than Zapier accepts, another approach works better.
Zapier's trigger payload limits are covered in the payload size question. For flows that need custom branching, retries or large payloads, an n8n webhook is often the better tool; see how to set up an n8n webhook. Our Zapier automation service builds Catch Hook flows with filters, alerts and a clear list of which systems send what. For the cost side, the Zapier pricing guide explains how each action step counts.
Related questions and services
- What is the maximum payload size for a Zapier webhook?
- How do you set up an n8n webhook?
- What is the difference between n8n's test and production webhook URLs?
- Why is my GoHighLevel inbound webhook not firing?
- Zapier pricing in 2026: what a real business pays each month
- Zapier automation service
Sources and further reading
- Zapier help: Catch Hook (webhooks) (methods, parsed and raw hooks, array behaviour, checked 2026-10-04)
Zapier's interface and limits change. Confirm on the current help article before you rely on a specific label or number.
