Connect Make.com to LeadFlow
Answer: You can connect LeadFlow to Make.com via outgoing webhooks (every plan) or inbound POST with a Business API key: send lead events like created, moved, and won to a Make scenario, or push leads back into LeadFlow.
Connect LeadFlow to Make.com via outgoing webhooks (every plan) or inbound POST with a Business API key. Send lead events (created, moved, won) to a Make scenario, or push leads back into LeadFlow. Includes the exact JSON payloads Make receives and sends.
Make.com is an automation platform (like Zapier) that connects apps by triggering scenarios. You can hook LeadFlow into Make in two directions: LeadFlow can send lead events to Make (most common), and Make can push new leads back into LeadFlow.
Direction 1 — Send LeadFlow events to Make (recommended)
This is the direction most people want: a new lead, a stage change, or a won deal in LeadFlow can start a Make scenario you configured (for example: post to Slack, add a row to Google Sheets, or send a follow-up email).
- 1In Make.com, create a new scenario.
- 2Add the Webhooks app and choose the Custom webhook module.
- 3Click Add next to the Webhook field, then click Save. Make generates a unique URL like `https://hook.make.com/abcdef123456`.
- 4Leave Make open and copy that webhook URL.
- 5In LeadFlow, open the Integrations view and scroll to Outgoing webhooks (Zapier / Make.com).
- 6Paste the Make webhook URL into the Webhook URL field.
- 7Tick the events you want sent: New lead added (`lead.created`), Lead moved stages (`lead.status_changed`), Deal won (`lead.won`), or New quote generated (`quote.created`).
- 8Click Add webhook.
- 9Back in Make, click OK on the webhook module, then Run once and wait (it needs to be listening).
- 10Trigger the event in LeadFlow — create a test lead or move one to Won — and Make's scenario will fire.
What Make receives
LeadFlow POSTs a JSON object to your Make webhook. It always contains an `event`, a `timestamp`, and a `data` object with the record. To use fields downstream in Make, use the JSON.parse function on the request body and map `data.name`, `data.email`, `data.company`, and so on.
{
"event": "lead.created",
"timestamp": "2026-08-22T09:00:00.000Z",
"data": {
"id": "clx...",
"name": "Ada Lovelace",
"email": "ada@example.com",
"company": "Analytical Engines",
"phone": "+1 555 0101",
"status": "New",
"source": "web",
"score": 65
}
}Direction 2 — Push leads from Make into LeadFlow
A Make scenario can also create or update leads in LeadFlow by POSTing JSON to LeadFlow's webhook receiver: `https://leadflow.live/api/integrations`. Use the HTTP module in Make with method POST and the JSON body below.
{
"event": "create_lead",
"data": {
"name": "Grace Hopper",
"email": "grace@example.com",
"company": "Compilers Inc",
"phone": "+1 555 0102",
"jobTitle": "CTO",
"source": "Make.com",
"status": "New",
"value": 0,
"notes": "Imported via Make",
"tags": "automation;warm"
}
}- `create_lead` — adds a new lead (name and email required). Score starts at 0; Pro recalc runs after create. A client-supplied score is ignored.
- `update_lead` — updates an existing lead; include `data.id` (the LeadFlow lead ID) plus the fields to change.
- Authenticate with a Business API key (Bearer or X-API-Key), or a signed-in session. Server-to-server automation should use the API key.
Useful Make scenarios to start with
- 1New lead → Slack alert — trigger on `lead.created`, send a message to your team's Slack channel.
- 2Lead won → Google Sheets — trigger on `lead.won`, append the company and value to a sales sheet.
- 3New lead → Create task — trigger on `lead.created` in Make, then call LeadFlow's `/api/integrations` with `update_lead` or use a task-creating app.