AI Automation
Pro

What is a Webhook and why is it useful?

A Webhook is a unique URL that lets external systems "knock on the door" and pass you data in real time — without frequent polling. Instead of Make.com checking every two minutes whether something new happened, the third-party system sends an HTTP request the moment the event occurs. The result: much faster automation, with far fewer wasted API quotas.

Examples of common uses: receiving a new lead from a Typeform form, receiving a payment from Stripe, receiving a new message from Slack, updating an order status from WooCommerce, and hundreds of other services that support sending Webhooks.

Creating a Webhook in Make.com — step by step

Code: sending data to a Webhook in Make.com

If you want to test your Webhook from JavaScript code (Node.js, browser, or any other environment), here is a full example:

// sending data to a Webhook in Make.com
const webhookUrl = 'https://hook.eu1.make.com/YOUR_WEBHOOK_ID';

const data = {
  name: 'John Doe',
  email: 'israel@example.com',
  phone: '050-1234567',
  source: 'landing_page',
  timestamp: new Date().toISOString()
};

const response = await fetch(webhookUrl, {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify(data)
});

console.log('Status:', response.status); // 200 = success
const text = await response.text();
console.log('Response:', text); // "Accepted" = Make.com received successfully

Common mistakes and how to avoid them

Router Module — routing by conditions

The Router is one of the most powerful tools in Make.com. It lets you split the Scenario into several branches, each of which runs under different conditions. Think of it like an switch-case in code — each Branch gets a Filter with an activation condition.

Example: a lead coming from Facebook is sent to an immediate WhatsApp chat, a lead from the website gets a detailed email, a lead from LinkedIn is fed directly into the CRM. Each Branch runs independently and in parallel.

Setting Filter Conditions

Fallback Route — "otherwise"

Every Router needs at least one Branch with a Fallback (Otherwise). This is the Branch that runs all the data that did not pass any other Filter. Without a Fallback, data that does not match any Branch is silently lost — and you won't know about it. The right way: add a final Branch as Otherwise → send yourself an alert + save to an Error Log.

Nested Routers

You can nest Routers within Routers to create complex logic. For example: a first Router splits by country (Israel / abroad). The Israel Branch goes to a second Router that splits by city. Main use: complex Escalation processes in Sales Pipelines.

Automation in production will encounter errors — it's not a question of if, but when. Make.com offers a powerful error-handling mechanism that lets you control exactly what happens when a module fails.

The four directives

Error Handler Routes

Right-click any module and choose Add error handler. This adds a special Branch that runs only when the module fails. There you can put: sending an email to the admin, adding a row to Google Sheets with the error details, sending a Slack message, and then choosing the appropriate directive.

Retry — automatic retry

For temporary network errors, set up Retry inside the Break directive. Set the number of attempts (up to 5) and the interval in seconds between each attempt. This is ideal for API calls that can fail due to Rate Limiting.

{
  "errorHandler": "resume",
  "retryCount": 3,
  "retryInterval": 60,
  "fallbackValue": null
}

Data Stores — a built-in database in Make.com

A Data Store is a minimalist database built directly into Make.com. It lets you save and retrieve data between different runs of the Scenario — something you cannot do with regular variables. Main uses: preventing duplicate processing (Deduplication), storing statuses, data cache, tracking a lead over time.

Each Data Store is defined with a Schema — the structure of the fields it will contain. For example: a field email (Text, Unique), status (Text), last_seen (Date).

Aggregators — collecting items from an Iterator

When an Iterator produces multiple items (for example: 50 rows from Google Sheets), an Aggregator collects them back into a single item. The three common Aggregators: