Course A · Module A3 No-Code Automation · Lesson 10 of 17

Webhooks: Connecting Anything deep dive

When there's no ready-made connector between two apps, a webhook bridges the gap — and it's mostly just copy and paste.

~16 min · Have Make or Zapier open · Prereq: A9 multi-step automation complete

Every automation platform has hundreds of built-in app connectors. But sooner or later you'll hit one that isn't listed. Maybe it's your booking system, your custom client portal, or a niche industry tool. That's when people say "you'd need a developer." They're usually wrong. Your single win: by the end of this lesson you'll understand what a webhook is, when to reach for one, and that setting one up is almost always copy a URL, paste it somewhere, save. That's the whole job.

What a webhook actually is

Imagine a doorbell at your house. You don't stand at the window watching for visitors — you wait until the bell rings. The moment someone arrives, it sends you a signal automatically.

A webhook works exactly the same way. Instead of your automation tool constantly asking "did anything happen yet?" — which is slow and wasteful — the other app rings the doorbell the instant something occurs. It sends a small packet of data ("a new order just came in — here are the details") straight to a URL your automation tool is listening on. No polling. No delay. Instant.

That URL your automation tool gives you is called a webhook URL. It's the address of your doorbell. You copy it, go to the other app's settings, and paste it into a field usually labelled "Webhook URL" or "Callback URL". Done.

When you'd reach for a webhook

Good webhook candidates

  • An app that's not in your platform's connector list
  • Any app with a "Webhooks" or "Integrations" section in its settings
  • Your own website or landing page (most page builders can send webhooks on form submit)
  • Payment processors not natively supported (many support webhooks as a fallback)

Try the connector first

  • If your platform lists the app natively, use that connector — it's pre-tested and handles authentication for you
  • If the app has no "Webhooks" or "API" section in its settings, it may not support them at all — check their docs

The basic flow — step by step

  1. Create a webhook trigger in your automation tool. In Make: add a module → Webhooks → Custom webhook → Create. In Zapier: choose "Webhooks by Zapier" as the trigger → Catch Hook. The tool generates a URL for you.
  2. Copy that URL. It looks something like https://hook.eu2.make.com/abc123xyz. Copy the whole thing.
  3. Paste it into the other app's webhook settings. Every app labels this slightly differently — look for "Webhook URL", "Callback URL", "Notification URL", or "Endpoint". Paste and save.
  4. Trigger a test event. Do the thing in the other app that should fire the webhook (submit a form, create an order). Go back to your automation tool and click "Determine data structure" or "Test trigger" — it should show you the packet of data that just arrived.
  5. Map the fields and build the rest of your scenario. Now that your tool can see the incoming data, the rest is normal automation — use the fields just like any other trigger.
The reassuring truth: the data that arrives in a webhook is just text — a list of labelled values like name: "Acme Corp", amount: 450. You don't need to understand how it's structured beforehand. Run the test, let your automation tool parse it, and all the fields appear as clickable options. Technical knowledge not required.

What can go wrong — and how to fix it

No data arrivedMake sure you triggered an actual event in the other app after pasting the URL. Webhooks don't backfill — they only capture events that happen from that point forward.
Fields missingThe other app only sends what it sends. Check its docs for which fields are included — sometimes you need to enable "full payload" in its settings.
URL expiredSome platforms give you a temporary URL for testing that expires. Use your tool's permanent webhook URL (not the one-time test URL) in the other app's settings.

Check yourself

Answer before opening. Recalling it now is what makes it stick.

What is a webhook URL, in plain English?

It's the address of a "doorbell" your automation tool is listening on. When you paste it into another app, that app rings the bell — sends data instantly — the moment an event happens. No polling, no delay.

You paste the webhook URL, trigger a test form submission, but no data shows up in Make. What's the most likely cause?

You triggered the form before clicking "determine data structure" — or you used a temporary test URL that expired. Paste the permanent webhook URL, click the "listen" button in Make first, then trigger the event in the other app.

Your booking system isn't in Zapier's app list. A colleague says you need a developer. What's your first move?

Check the booking system's settings for a "Webhooks" or "Integrations" section. Most modern booking tools support webhooks as a standard fallback. If there's a webhook field, you can connect it yourself in minutes — no developer needed.

Read this next (primary source)

What Are Webhooks? — Zapier Blog — the clearest plain-English explainer available, with annotated diagrams. ~10 min. See RESOURCES.md for more.

I'm your teacher — ask me anything. Tell me which two apps you're trying to connect and I'll walk you through the exact steps: where to find the webhook field in the sending app, which trigger module to use in Make or Zapier, and what the data will look like when it arrives.

Terms from this lesson — trigger, action, automation — are defined in the course glossary. Keep it open.