Automations
Make.com Trigger Node
3 min readnode-make
Trigger a Make.com (formerly Integromat) scenario via a custom webhook and pass data to it.
Make.com Trigger Node
Sends a POST request to a Make.com custom webhook URL, passing any data you specify as the JSON body. The Make scenario receives the payload and continues its own flow.
When to use it
- Trigger a Make scenario that updates a Google Sheet when a lead is qualified.
- Hand off to Make for complex integrations FlowMaticX doesn't natively support.
---
Required fields
| Field | Type | Required | Description |
|---|---|---|---|
| webhookUrl | string | Yes | Make.com custom webhook URL (from your scenario's webhook module) |
| data | JSON object | Yes | Data to send — {{variables}} and {{lead.xxx}} supported in values |
---
Variables available
This node does not produce output variables.
---
How to get a Make webhook URL
- Open Make.com and create a new scenario.
- Add a Webhooks → Custom webhook module as the trigger.
- Click Add → give it a name → copy the URL shown.
- Paste it into the
webhookUrlfield of this node.
---
Step-by-step setup
- Create the Make scenario with a custom webhook trigger.
- Add a Make.com Trigger node to the automation canvas.
- Paste the webhook URL.
- Build the data object with the fields Make needs.
- Save and run a test — check Make's scenario history to confirm the payload arrived.
---
Example config
json
{
"webhookUrl": "https://hook.eu1.make.com/abc123xyz",
"data": {
"email": "{{lead.email}}",
"name": "{{lead.firstName}} {{lead.lastName}}",
"score": "{{variables.score}}",
"source": "flowmaticx"
}
}
---
Tips & gotchas
- Make webhooks accept any JSON structure — design the payload to match what your Make modules expect.
- Make scenarios must be active (not paused) to receive webhooks.
- For two-way communication (Make sends data back), use a Make → HTTP Request node to POST back to a FlowMaticX inbound webhook.