Beginning
Sooner or later, every automation builder runs into the same wall. A client asks you to connect their system — and it turns out their system isn't Gmail, isn't Google Sheets, isn't Slack. It's some custom-built booking form their developer made three years ago, or a payment tool nobody's heard of, or an app so niche it doesn't even show up when you search for it inside Make.
Most beginners stop right there. They assume that if an app isn't in Make's list, it simply can't be automated. That assumption is wrong, and this lesson is where you find out why.
Webhooks are the tool that breaks that limitation open. Once you understand them, "Make doesn't support this app" stops being a dead end — it just becomes a slightly different way of connecting things.
In this lesson, you'll learn:
- What a webhook actually is, in plain terms
- Why a webhook reacts instantly, while the triggers you've used so far don't
- How to create a custom webhook in Make and get its URL
- How to send it test data and read what comes back
Core Concept: The Direct Phone Line
Tool Walkthrough: Setting Up Your First Webhook
Step 1 — Create a New Scenario
Start a new scenario, click the "+" to add your first module, and search for "Webhooks." Select the "Custom webhook" option.
Step 2 — Name It and Save
Give the webhook a clear name — something like "Order Form Intake" — so you can recognize it later if you build several. Once you save, Make generates a unique URL tied specifically to this webhook.
Step 3 — Copy the URL
This URL is what you'd hand over to whatever app is going to send data — a form tool, a booking page, a custom script, anything capable of sending a request. In a real project, this is usually a setting inside that other app ("send submissions to this URL"). For practice purposes, you can send a simple test request to it yourself.
Step 4 — Send a Test Request
Make waits for its first piece of real data before it can understand the shape of what's coming. Send one test submission to the URL — the exact method depends on what tool you're using to send it, but the goal is simply to get some data to hit that webhook once.
Step 5 — Redetermine the Data Structure
Back in Make, click "Redetermine data structure." This tells Make to look at the test data you just sent and work out what fields exist inside it — names, emails, whatever the data contained. Without this step, Make has no idea what fields are even available to map later.
Step 6 — Add an Action and Map the Data
Add a module after the webhook — Google Sheets, for example — and map the fields it just detected into your destination, the same way you've mapped data in every automation so far.
Step 7 — Activate and Confirm
Toggle the scenario to Active, send another test submission, and watch it flow through automatically — no manual "Run once" required this time, because the webhook is now listening on its own.
Real Example: The Freelancer's Secret Weapon
Picture a client who runs a custom booking page built by a web developer years ago — no plugin, no popular form builder, nothing Make has ever heard of. A beginner looks at that and says, "Sorry, I can't connect that." Someone who understands webhooks says something very different: "No problem — just have it send its data to this URL."
That single sentence is often the difference between an automation builder who can only take on simple, pre-supported jobs, and one who can take on any client, regardless of what software they happen to be using. It's one of the most valuable, least talked-about skills in freelance automation work.
Common Mistakes
Mistake 1: Exposing the webhook URL publicly
A webhook URL is like a password: sharing it somewhere allows for anyone to send data to the link. So, if you share the URL on a public forum, comment section, or another place freely accessible on the internet, anyone could post random data to your webhook. Hence, don’t share your webhook URL publicly.
Mistake 2: Skipping “Redetermine data structure”
If you skip this step, Make won’t have anything to map the data to, and your next module’s fields will be empty because Make doesn’t yet know what data structure to expect.
Mistake 3: Forgetting to activate the scenario
As lesson 4 teaches, Make scenarios need to be activated to run automatically. The same mistake applies here: Make will only run the scenario if it is in the Active state, even if you have it set to run on a schedule.
Try This Yourself
Before moving to Lesson 9, build and test one on your own:
- Create a custom webhook and send it one test submission
- Run "Redetermine data structure" and see exactly what fields it finds
- Map that data into a Google Sheet and confirm a new row appears
Key Takeaways
- A webhook is an instant, real-time trigger — the opposite of a polling trigger like Gmail's
- Its biggest strength is connecting apps that have no official Make integration at all
- "Redetermine data structure" is the step that makes the incoming fields available to map
- A webhook URL should be treated as private, since anyone with it can send data to your scenario
Frequently Asked Questions
Does a webhook URL ever expire?
No — once generated, it stays active for as long as the module exists in your scenario, unless you delete it yourself.
Can one scenario have more than one webhook?
Yes, though each webhook needs its own module and its own unique URL — you can't reuse a single webhook URL for two different purposes.
Is there a limit to how many webhooks I can use on the free plan?
The free plan allows a generous number of webhooks for learning and small projects; the real constraint to watch is your monthly operations limit, since every webhook trigger still counts as one.
Next Lesson Preview
With webhooks under your belt, you're ready to open up a whole new layer of automation. In Lesson 9, we start Phase 3 by breaking down APIs and API Keys in plain, beginner-friendly terms — the foundation you'll need before connecting Make to AI tools like ChatGPT.
Navigation:
← Previous: Lesson 7 — Testing & Debugging Your Automations
→ Next: Lesson 9 — Understanding APIs & API Keys (Beginner-Friendly)