Make Webhook

What this is

Make is a visual automation platform (formerly Integromat) with hundreds of pre-built integrations. LeadRails fires a POST to a Make Custom Webhook URL; your scenario then routes the data through whatever modules you've configured. Make uses a tree-based execution model that's friendly for branching logic.

Where to find your webhook URL

1. Sign in to make.com
2. Create a new scenario (or open an existing one)
3. Click the + at the start of the scenario to add the first module
4. Search for "Webhooks" → pick "Custom webhook"
5. Click "Add" to create a new webhook → give it a name (e.g. "LeadRails")
6. Make generates a URL on a regional subdomain — looks like https://hook.us1.make.com/abc123xyz (or eu2, eu1, etc.)
7. Copy the URL exactly
8. Click "Save" then "Re-determine data structure" (Make needs at least one inbound request to learn your payload shape)

Domain note

LeadRails validates the URL host is *.make.com or *.integromat.com (the legacy domain still works for older accounts).

Set up your destination in LeadRails

1. Sign in → Destinations → New
2. Adapter type: "Make Webhook"
3. Webhook URL: paste the URL from Make
4. Click Create

Train Make on the payload shape

Make needs to see at least one real payload to know what fields are available downstream. Without this, subsequent modules can't reference fields.

1. In your Make scenario, with the Custom Webhook module selected, click "Re-determine data structure"
2. In LeadRails: Sources → your source → click "Send test event"
3. Make's webhook module captures the payload and learns the field schema
4. Add subsequent modules; LeadRails fields are now selectable in the field picker

Activate the scenario

Make scenarios are inactive by default — the toggle is at the bottom-left of the scenario editor. Turn it ON or the webhook just queues events without processing.

Scenarios on the free Make plan run on a schedule (every 15 min), not real-time. Paid plans process webhooks instantly.

What gets sent

LeadRails POSTs the raw lead event JSON (the lead_event.v1 shape: schema_version, event_type, source, lead, submitted_at) as the request body. Make's Custom Webhook module accepts any JSON, so forwarding the event verbatim keeps every source field available to downstream modules.

Set a per-route mapping in LeadRails when you'd rather send a flat, renamed set of fields — the mapped object replaces the raw event as the body. Each request also carries an X-Idempotency-Key header (the delivery job id) so a Router or Filter module can drop replays; Make itself does not deduplicate webhook triggers.

Verifying the connection

"Verify connection" POSTs a small recognizable body ({ "_lead_rails_verify": true }) to your webhook URL. Because Make has no dry-run mode for webhooks, this fires the connected scenario once — branch on the _lead_rails_verify flag if you want to ignore the ping. A plaintext Accepted or any 2xx means the webhook is active; a 404 means Make no longer recognizes the URL (scenario deleted); a 400/410 mentioning "deactivated" means the scenario is turned off.

Troubleshooting

invalid_make_webhook_url

URL host isn't *.make.com or *.integromat.com. Copy the URL exactly from Make.

Scenario doesn't run but 2xx response

Scenario is inactive. Turn ON the toggle.

Fields show as Collection 1, Collection 2 etc. in Make

Make hasn't learned the payload shape yet. Click "Re-determine data structure" → send a test event from LeadRails.

Free plan delay

15-minute polling on free tier. Upgrade for real-time.

Make operations pricing

Make charges per "operation" — each module run consumes one. A scenario with 5 modules running on every lead costs 5 operations per lead.

Like Zapier, consider per-route filtering in LeadRails so you only invoke Make for qualified leads.