Webhooks How-To with Make.com

Webhooks are one of the fastest ways to send data between apps in real time, and make.com gives you a simple no-code way to receive and use that data inside automated workflows. This step-by-step guide shows you exactly how to capture a webhook, test it, and turn it into actions without writing any code.

What is a webhook in Make.com?

A webhook is an HTTP callback URL that waits for data from another service. When an event happens in the sending app, it sends a message to this URL, usually in JSON or form-data format.

In the context of make.com, a webhook is used as a trigger module. When data arrives at the webhook URL, the scenario starts and processes the incoming payload according to the logic you design.

Why use webhooks with Make.com scenarios?

Using webhooks inside make.com offers several advantages over traditional polling-based integrations.

• Real-time: Data is pushed instantly when an event happens.
• More efficient: No need to check for updates every few minutes.
• Flexible: You can send any custom payload, not just predefined fields.
• Extensible: Connect services that do not yet have a native module in your automation platform by using their webhook or HTTP features.

How webhooks work before you use Make.com

Before connecting a webhook to make.com, it helps to understand the basic flow between two systems.

1. Event occurs: Something happens in the source app (a purchase, a form submission, a new message, and so on).
2. Request is sent: The source app sends an HTTP POST request to your webhook URL.
3. Data is received: The receiving system processes the payload and responds, usually with a 200 OK status.

The webhook URL is simply an endpoint ready to receive these requests. With make.com, that endpoint is provided for you, and the platform lets you map the payload to any modules you add next.

Step-by-step: Create a webhook in Make.com

Follow these steps to add a custom webhook trigger to your automation.

1. Create a new scenario in Make.com

1. Log in to your make.com account.
2. On the dashboard, click the option to create a new scenario.
3. You will see an empty canvas where you can place modules.

2. Add the Webhooks module

1. Click the plus icon on the canvas.
2. Search for the Webhooks app in the list of available modules.
3. Select the trigger type labelled something like Custom webhook or similar, depending on your account interface.

This module becomes the starting point for your make.com scenario. Each time it receives data, the entire scenario runs.

3. Create a custom webhook in Make.com

1. In the Webhooks module card, choose the option to Add or Add custom webhook.
2. Give your webhook a descriptive name, such as New Order from Shop or Form Submissions.
3. Save your changes. Make.com automatically generates a unique URL for this webhook.

Once created, the webhook URL appears in the module settings. This is the address you will send data to from your external service.

How to test your Make.com webhook

Testing the webhook ensures that the payload arrives correctly and that make.com can parse the data structure.

4. Switch the webhook module to listening mode

1. Open the Webhooks module settings.
2. Click the button that puts the module into a waiting or listening state (often labelled Run once on the scenario panel).
3. The scenario canvas shows that it is now ready to receive a single test request.

5. Send a test request to your Make.com URL

From the app or service that will send data, configure it to post to the webhook URL generated by make.com. If that app does not yet support webhooks natively, you can still send a test using an HTTP client.

Typical ways to send a test:

• Use a built-in webhook integration in your source app.
• Use a testing tool like Postman or a command-line curl request.
• Use a test or staging environment in the external service to avoid creating real records.

After the test request is sent, check the scenario in make.com. The trigger module should show that a bundle of data has been received.

6. Inspect and map the received data

1. Click the Webhooks module bubble on the canvas.
2. Open the list of output fields that were detected from the last request.
3. Verify all the important properties: IDs, email addresses, timestamps, amounts, and any nested objects.

Make.com stores this structure so you can reference each field in later modules. This mapping step is key to building a reliable automation.

Build an automation flow after the Make.com webhook

Once the webhook in make.com is validated, you can connect it to other modules to form a complete scenario.

7. Add modules to process webhook data

Consider using some or all of the following patterns:

• Filters: Add conditional filters after the webhook so the scenario only continues when certain conditions are met (for example, order total above a threshold or specific form responses).
• Data transformation: Use built-in tools to format dates, clean up text, or convert numerical values.
• HTTP module: Call external APIs if you need to enrich or validate data.
• App-specific modules: Send the data to CRMs, email tools, or databases supported in make.com.

8. Save, schedule, and activate the scenario

1. Save your scenario frequently as you add modules.
2. Decide whether the webhook-based scenario should run immediately on each incoming request or on a schedule combined with other logic.
3. Switch the scenario to ON so that make.com begins processing real events coming through the webhook.

Monitor the first few live runs in the execution log. This helps you confirm that the data mapping and downstream actions behave as intended.

Best practices for using Make.com webhooks

Keep these guidelines in mind to get stable, predictable behavior from your webhooks.

• Keep URLs secret: Treat your webhook URL as a secret. Anyone with the address can send data to it.
• Use test environments: Connect staging or sandbox accounts while you design and test your make.com scenario.
• Validate payloads: Where possible, add filters or checks that confirm required fields are present before acting.
• Handle errors gracefully: Add error-handling or alternative paths for unexpected or incomplete payloads.
• Document your map: Maintain a brief record of which fields from the webhook feed which modules, especially for complex scenarios.

Learn more about webhooks and Make.com

For deeper background on how webhooks operate and additional examples related to make.com, you can review the original article on the official blog at this webhook explanation.

If you need help planning complex automation architectures around make.com, or want consulting on broader integration strategies, you can also explore services from Consultevo, a specialist consultancy.

By combining clear webhook design with the visual scenario builder in make.com, you can build powerful integrations that react immediately to events in your business systems, all without traditional development work.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help