Webhooks guide for Make.com

This step-by-step guide explains how to create, configure, and use webhooks in make.com so you can trigger scenarios, capture data, and automate tasks efficiently.

Webhooks let other apps send data to your scenarios instantly, without polling. In this tutorial, you will learn how to set up a webhook trigger, map incoming data, and keep your automations stable and secure.

What are webhooks in Make.com?

In make.com, a webhook is a special URL that receives HTTP requests from another application or service. When data is sent to this URL, it triggers a scenario and passes the payload into your modules.

Key points about webhooks in this platform:

They act as triggers at the start of a scenario.
They listen for incoming HTTP requests from external services.
They capture data such as headers, query string, and body.
They can be customized with response codes and advanced settings.

Using a webhook trigger is one of the most flexible ways to integrate external systems with your automations.

How webhooks work in Make.com scenarios

When you add a webhook module at the beginning of a scenario, the system generates a unique URL. External services send data to this URL with an HTTP request, usually POST. The platform receives the request, starts the scenario, and exposes the payload as data items for the subsequent modules.

The basic lifecycle is always the same:

You add a webhook module to a scenario.
You generate or copy the webhook URL.
You configure another service to send data to this URL.
The webhook receives a request and triggers your scenario in real time.

Types of webhook modules in Make.com

The platform offers several webhook-related modules, each with a specific purpose. While the exact names may vary by app or connector, the core behavior is similar.

Custom Webhook — a generic module that creates a unique URL for receiving any kind of structured or unstructured JSON, form data, or query parameters.
App-specific webhooks — some apps have dedicated webhook triggers that handle the authentication or signature verification for you.
Webhook response modules — modules that let you control the HTTP response returned to the caller.

Most integrations start with a Custom Webhook because it is easy to configure and supports a wide range of payload formats.

How to create a webhook in Make.com

Follow these steps to create and configure a webhook trigger in a new or existing scenario.

Step 1 — Create or open a scenario in Make.com

Sign in to your account.
From your dashboard, create a new scenario or open an existing one.
In the scenario editor, click the plus icon to add a new module.

Step 2 — Add a webhook trigger module

Search for the Webhooks app or the relevant service that supports webhooks.
Select a Custom Webhook or the appropriate webhook trigger module.
Click to add it as the first module in your scenario so that it acts as the trigger.

Step 3 — Create a new webhook

In the module configuration, choose the option to Add or Create a new webhook.
Enter a meaningful name so you can recognize it later.
Confirm to create the webhook; the system generates a unique URL.

Copy this URL. You will use it in the external application that sends data to your scenario.

Step 4 — Send a test request to the webhook

Before you can map incoming fields, send a sample payload to the generated URL.

Keep the scenario editor open with the webhook module selected.
In another tool or application, configure it to send an HTTP request to the webhook URL.
Send a test payload (for example, JSON or form data) with the fields you expect.
Return to the editor and let the module finish capturing the sample.

Once the sample request is captured, the webhook module will display the detected structure so you can start mapping fields in the following modules.

Step 5 — Map data from the webhook in Make.com

After capturing a sample, the incoming data becomes available as bundles of items. You can now connect additional modules and map the fields:

Click the next module in the scenario.
Open the mapping panel.
Choose values from the webhook output (such as body parameters, headers, or query values).
Save the mapping and run the scenario again with real data.

Every new request to the webhook URL will trigger the scenario and pass the mapped data through the workflow.

Configuring webhook responses in Make.com

Sometimes the calling service expects a specific HTTP response. You can control this using dedicated webhook response modules.

Typical response options include:

Custom HTTP status codes (e.g., 200, 201, 400, 500).
Plain text, JSON, or other structured response bodies.
Response headers such as content type or custom metadata.

Place the response module near the end of your scenario and map any data you want to return from previous steps.

Security tips for webhooks in Make.com

Because webhooks expose URLs that receive external requests, it is important to secure them appropriately.

Keep URLs secret — treat each webhook URL like a password and do not share it publicly.
Use signing or tokens — if the external app supports signatures or tokens, validate them in your scenario.
Filter by IP or source — some providers allow you to restrict outgoing webhook calls to known IP ranges.
Validate payloads — check the structure and required fields before processing data further.

These measures help ensure only authorized systems can trigger your automations.

Troubleshooting webhooks in Make.com

If your webhook is not triggering as expected, check the following areas.

Verify the webhook URL

Confirm that the external service is using the exact URL from the webhook module.
Make sure there are no extra spaces or changes in protocol (HTTP vs HTTPS).

Check request logs and history

Review the scenario execution history to see if runs were triggered.
Inspect input bundles to confirm that the payload matches what you expect.

Confirm content type and data format

Verify that the external app is sending JSON, form data, or another format your module can parse.
Ensure headers like Content-Type are set correctly.

If needed, you can compare your setup with the official webhook documentation for this platform at the Make webhook help page.

Best practices for managing Make.com webhooks

As your workspace grows, you may manage many different webhooks. Use these best practices to keep things organized and reliable.

Use descriptive names so you can quickly find the correct webhook for each integration.
Document each endpoint with the source application, purpose, and expected payload.
Test changes in a separate scenario before updating live webhook URLs.
Monitor failed runs and add error handling modules to gracefully manage invalid requests.

Good organization helps avoid confusion and keeps production scenarios stable.

Next steps and additional resources

Once you are comfortable working with webhooks, you can combine them with filters, routers, and advanced modules to build powerful, event-driven workflows. For strategic automation planning and scenario design, you can also consult experts, for example at Consultevo.

To dive deeper into advanced options such as custom responses, detailed examples, and app-specific webhook setups, refer to the official documentation at Make.com webhook documentation.

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