Developers

Zapier Webhook Guide: Connect Any App With Catch Hooks (No Server Needed)

How to use a Zapier webhook to connect apps without writing a server: Catch Hook vs Catch Raw Hook, setting up the trigger, mapping fields, security and signatures, sending webhooks out, and real examples with SMS and WhatsApp.

On this page
  1. How it works
  2. Catch Hook or Catch Raw Hook?
  3. Step by step
  4. Example 1: log incoming SMS to a spreadsheet
  5. Example 2: post WhatsApp messages to a team channel
  6. Example 3: Tekservix account events
  7. Sending webhooks out of Zapier
  8. Security
  9. Reliability tips
  10. When to use Zapier, and when not to
  11. A worked example

Most apps can send webhooks, but receiving them usually means running a server. Zapier removes that step: it gives you a URL, catches whatever is posted to it, and lets you do something with the data in any of thousands of apps, such as adding a spreadsheet row, posting to Slack or creating a CRM contact. A Zapier webhook is often the fastest way to connect a tool that has webhooks to one that doesn't have a direct integration.

How it works#

With a Catch Hook trigger, Zapier creates a unique URL for your Zap. When another app sends an HTTP POST to that URL, Zapier reads the data and starts the Zap, passing the fields to the next steps. Zapier's help centre explains the details in Trigger Zaps from webhooks. Webhooks by Zapier is a premium app, available on paid plans.

Catch Hook or Catch Raw Hook?#

  • Catch Hook parses the incoming JSON or form data into fields you can pick from in later steps. It's the right choice almost every time.
  • Catch Raw Hook also gives you the exact raw body and headers. Use it when you need to verify a signature, which must be computed over the raw body.

Step by step#

  1. Create a Zap and choose Webhooks by Zapier as the trigger, with the Catch Hook event.
  2. Copy the webhook URL Zapier shows you.
  3. Paste it into the other app's webhook settings, and choose which events to send.
  4. Trigger a real event, such as sending a test SMS to your gateway phone or placing a test order.
  5. Test the trigger in Zapier so it picks up the sample and shows its fields.
  6. Add actions and map fields from the sample, such as the sender's number into a spreadsheet column.
  7. Add a filter if you only want some events, for example only sms.received.
  8. Turn the Zap on and send one more real event to confirm.

Example 1: log incoming SMS to a spreadsheet#

With SMS Gora, add your Catch Hook URL as a webhook for the sms.received event. Each incoming text arrives with fields such as event, data.from, data.message and data.received_at. In Zapier, add a Google Sheets "Create spreadsheet row" action and map those fields to columns. Every reply from a customer now lands in a sheet your team can filter and share, without any code.

Example 2: post WhatsApp messages to a team channel#

WAservix can send a messages.received webhook for each incoming WhatsApp message. Point it at a Catch Hook, filter for messages from customers, and post the sender and text to a Slack or Teams channel. The team sees new enquiries where they already work. Our guide to WhatsApp webhooks explains the event fields.

Example 3: Tekservix account events#

The Tekservix developer platform has a ready-made Zapier / Make / n8n app in its app marketplace: paste your Catch Hook URL, choose the events, and Tekservix sends each one, signed, to your Zap. See the developer platform for the list of events.

Sending webhooks out of Zapier#

Webhooks by Zapier also works as an action: a POST step sends data from any Zap to a URL. That lets you trigger an API that has no Zapier app. For example, when a new row appears in a sheet, POST to an SMS API to send a text. Add the API key as a header in the step, never in the URL, and keep the Zap private, since anyone with access to it can see the key.

Security#

A Catch Hook URL accepts data from anyone who knows it. Treat it like a password:

  • Keep the URL private. Don't paste it into public code, screenshots or shared documents.
  • Filter on expected values, such as the event name and your device ID, so random posts do nothing.
  • Verify signatures when it matters. Use Catch Raw Hook and a Code by Zapier step to compute the HMAC of the raw body and compare it with the signature header. Our guide to webhook signature verification shows the logic.
  • Use a real server for sensitive actions, such as issuing refunds or changing account data. Zapier is excellent for notifications and logging; payments deserve stricter checks.
  • Avoid passing personal data to more apps than necessary.

Reliability tips#

  • Check Zap history regularly; failed runs show there with the error.
  • Handle duplicates: senders retry when they don't get a quick response, so the same event can arrive twice. Use a unique field, such as the message ID, to avoid duplicate rows or posts.
  • Watch task usage: each run uses tasks from your Zapier plan, and busy webhooks can use a lot.
  • Keep one Zap per job, which makes problems easier to find than one giant Zap.

When to use Zapier, and when not to#

Zapier webhooks are ideal for connecting tools quickly, prototyping workflows, and jobs where a few seconds of delay don't matter. For high volumes, strict security or complex logic, a small webhook handler on your own server is cheaper and gives you more control. Many teams start in Zapier and move a workflow to code once it's proven and busy.

A worked example#

Imagine a clinic whose patients reply to SMS reminders with YES or NO. The clinic adds a Catch Hook as an SMS Gora webhook for sms.received. The Zap filters for messages containing YES or NO, adds a row to the day's appointments sheet with the patient's number, reply and time, and posts NO replies to the reception team's channel so they can offer the slot to someone else. It took an afternoon to build, with no server and no developer, and reception now sees cancellations the moment they arrive.

Frequently asked questions

What is a Zapier webhook?

It's a Zapier trigger or action that sends or receives data over a URL. With a Catch Hook trigger, Zapier gives you a unique URL; any app that can send webhooks posts data to it, and that starts your Zap.

Is Webhooks by Zapier free?

Webhooks by Zapier is a premium app available on paid Zapier plans. Check Zapier's current plans, since the details change over time.

Can Zapier verify a webhook signature?

Not directly in the Catch Hook trigger. You can add a Code by Zapier step to compute and compare an HMAC, or keep the Catch Hook URL private and treat it as a secret. For sensitive actions, a small server that verifies signatures is safer.

Share this article
Written by

The team behind Tekservix

The Tekservix Team builds and supports Tekservix: WhatsApp and SMS APIs, AI tools, invoicing, PDF and SEO tools for growing businesses. We write practical, tested guides based on what we see our customers do every day.

More articles from the Tekservix Team

Get new guides in your inbox

One short email when we publish something useful: WhatsApp and SMS marketing, AI tools, SEO and running a business online. No spam, unsubscribe anytime.