Webhooks are one of the most powerful features in Make.com, and also one of the most confusing for beginners. If you’ve seen the word “webhook” and immediately felt lost, this guide is for you. By the end, you’ll know exactly what a webhook is, how to set one up in Make.com, and how to use it in three practical automations.
What Is a Webhook? (Plain English Explanation)
A webhook is a way for one app to automatically notify another app when something happens.
Think of it like this: instead of your Make.com scenario constantly asking “Did anything happen yet? Did anything happen yet?” (that’s called polling), a webhook means the other app taps Make.com on the shoulder and says “Hey, something just happened — here’s the data.”
Normal Make.com triggers using polling check for new data every 1–15 minutes. A webhook is instant — the moment the event happens, Make.com receives the data and your scenario runs.
Real-world analogy: Polling is like checking your mailbox every hour. A webhook is like having the postal worker ring your doorbell the moment they drop something off.
When does a webhook make sense?
- You need immediate response (payment received, form submitted, user signed up)
- The app you’re using supports webhooks (most modern SaaS tools do)
- You want to receive data from a custom source (your own website, app, or form)
How Webhooks Work in Make.com
In Make.com, there are two types of webhook scenarios:
1. Make.com as the receiver (Custom Webhook): Make.com gives you a unique URL. You paste that URL into another app’s webhook settings. When the event happens in that app, it sends data to Make.com’s URL, and your scenario runs.
2. Make.com as the sender (HTTP module): Your Make.com scenario sends data to another app’s webhook URL. This is less common for beginners and not what we’re covering in detail here.
For this guide, we’re focusing on Make.com as the receiver — the most common use case for small business automation.
Step-by-Step: Setting Up a Webhook in Make.com
This walkthrough takes about 10 minutes the first time. After that, it takes 2 minutes.
Step 1: Create a new scenario
Log in to Make.com and click “Create a new scenario.” You’ll see a blank canvas with a “+” in the center.
Step 2: Add a Custom Webhook trigger
Click the “+” to add your first module. Search for “Webhooks” in the app list. Select the “Webhooks” app, then choose “Custom Webhook” as the trigger type.
Step 3: Create your webhook
Click “Add” to create a new webhook. Give it a descriptive name (e.g., “Contact Form Submissions”). Make.com will generate a unique URL — it looks something like: https://hook.make.com/abc123xyz789
Copy that URL. This is the address you’ll paste into whatever app is sending you data.
Step 4: Send a test request
Make.com needs to see a sample data packet to know what fields it’ll be receiving. Go to the app that will be sending data (your form tool, your website, your payment processor) and submit a test entry while Make.com is in “listening” mode.
Click “OK” in Make.com to start listening. Submit your test. Make.com will show you the data structure it received.
Step 5: Add your action modules
Now add the modules that should run when webhook data arrives. For example: add a Google Sheets module to log the submission, or a Gmail module to send a notification.
Step 6: Turn on the scenario
Flip the toggle at the bottom left from “OFF” to “ON.” Your scenario is now live and will run instantly every time the webhook receives data.
3 Practical Webhook Examples for Beginners
Example 1: Website Contact Form to CRM
Setup: Your website’s contact form (Gravity Forms, WPForms, or a custom HTML form) posts to your Make.com webhook URL. Make.com receives the name, email, and message, creates a contact in HubSpot or Pipedrive, and sends you a Slack notification.
Why webhooks instead of polling: Form submissions are time-sensitive. You want the CRM contact created instantly, not up to 15 minutes later when polling would catch it.
Modules needed: Custom Webhook → HubSpot (Create Contact) → Slack (Send Message)
Estimated setup time: 20 minutes
Example 2: Stripe Payment Confirmation
Setup: In your Stripe dashboard, go to Developers → Webhooks → Add endpoint. Paste your Make.com webhook URL and select the “payment_intent.succeeded” event. When a customer pays, Stripe instantly sends data to Make.com, which logs the payment to Google Sheets and emails the customer a receipt.
Why webhooks instead of polling: Stripe doesn’t have a standard polling trigger in Make.com for payment events. Webhooks are the right tool for real-time payment processing.
Modules needed: Custom Webhook → Google Sheets (Add Row) → Gmail (Send Email)
Estimated setup time: 30 minutes (including Stripe webhook configuration)
Example 3: GitHub Issue Alert to Slack
Setup: In your GitHub repository settings, add your Make.com webhook URL as a webhook and select the “Issues” event. When someone opens a new issue, Make.com receives the data and posts a formatted summary to your team’s Slack channel — including the issue title, reporter, and link.
Why webhooks instead of polling: GitHub has a native Make.com integration, but webhooks give you instant delivery rather than polling every few minutes.
Modules needed: Custom Webhook → Slack (Send Message)
Estimated setup time: 15 minutes
Common Webhook Mistakes (and How to Avoid Them)
Mistake 1: Forgetting to send a test request before building
Make.com needs to see a sample payload to determine the data structure. If you skip the test step and just start building, you’ll have no fields to map. Always send a test submission first.
Mistake 2: Leaving the scenario in OFF mode
Make.com scenarios must be active to receive webhooks. A common mistake is building the scenario and testing it, then forgetting to flip the toggle to ON before going live. Webhooks sent to an inactive scenario are queued but can be lost if the queue fills up.
Mistake 3: Using the wrong webhook URL
Each Make.com webhook has a unique URL. If you have multiple scenarios, make sure you’re using the URL that corresponds to the right one. Paste the URL immediately after generating it — don’t try to remember it.
Mistake 4: Not handling unexpected data
If the sending app changes its payload structure (renamed field, added/removed data), your Make.com scenario may break silently. Use the “Error Handler” module on critical scenarios so you get notified when something goes wrong.
Mistake 5: Thinking webhooks require coding
They don’t. Make.com’s Custom Webhook module generates the URL and parses incoming JSON automatically. You don’t write any code. The only “technical” part is pasting the URL into the sending app’s settings.
Next Steps After Your First Webhook
Once you’ve set up your first webhook scenario, you’ll start seeing webhooks everywhere — almost every modern SaaS tool supports them. Stripe, PayPal, Shopify, Typeform, Gravity Forms, GitHub, GitLab, Slack, and hundreds of others all let you send webhook events.
For more scenario ideas that use webhooks and other Make.com features, see our collection of Make.com templates for beginners. And if you want to build more complex automations beyond webhooks, the Make.com beginner tutorial covers the full scenario builder in depth.
Webhooks feel intimidating at first because the word sounds technical. But the concept is simple — one app pings another app with data — and Make.com makes the implementation genuinely beginner-friendly. Build your first webhook scenario today, and you’ll wonder how you got by without it.