Zapier, Make, and n8n

Zapier, Make, and n8n use the same signed webhook runtime as a direct endpoint. That gives each platform background retries, delivery history, test delivery, and a stable versioned payload without requiring a separate leadmaps app.

The shared webhook runtime completed production verification. Automation bridges are supported on Hobby, Pro, and Business and use one integration hub connection slot.

Start an outbound workflow

Zapier

1. Create a Zap with Webhooks by Zapier, then choose Catch Hook.
2. Copy the Zapier hook URL.
3. In leadmaps, open Settings, Integrations, then Zapier.
4. Paste the URL, add a strong signing secret, and save.
5. Choose Send test, then use that request as the Zapier sample.
6. Add filters and actions in Zapier, test them, and publish the Zap.

Make

1. Create a scenario and add Webhooks, then Custom webhook.
2. Copy the generated URL.
3. In leadmaps, open Settings, Integrations, then Make.
4. Paste the URL, add a strong signing secret, and save.
5. Put the Make webhook into listening mode and choose Send test.
6. Finish the scenario, test it, and turn scheduling on.

n8n

1. Create a workflow with a Webhook trigger using POST.
2. Use the n8n test URL while building and the production URL after activation.
3. In leadmaps, open Settings, Integrations, then n8n.
4. Paste the URL, add a strong signing secret, and save.
5. Choose Send test, inspect the received data, then activate the workflow.

The platform may parse JSON before a workflow can inspect the original body. When it exposes the raw request, verify the signature as described in Outbound webhooks. When it does not, keep the generated hook URL private, restrict who can edit the workflow, and avoid placing sensitive actions directly behind an unverified trigger.

Send a safe action back to leadmaps

Hobby, Pro, and Business workflows can call the inbound bridge action endpoint with an API key that has only the integrations:write scope:

POST https://api.leadmaps.nl/workspaces/<workspace-slug>/integrations/bridge/actions
Authorization: Bearer <integration-api-key>
Content-Type: application/json

{
  "schema": "leadmaps.integration.action@1",
  "action": "lead.signal",
  "lead_id": "019f84c2-c0b5-7d13-b5f8-99ac768f2aa5",
  "signal": "meeting_booked",
  "idempotency_key": "zap-run-12345"
}

Allowed signals are qualified, contacted, meeting_booked, and follow_up_required. The endpoint records an activity signal. It cannot change contact details, prices, entitlements, arbitrary notes, or arbitrary events.

Create a separate key for each automation platform. Name it after the workflow, store it in that platform’s secret store, and revoke it when the workflow is no longer used. Sending the same idempotency key again returns the original result without recording the action twice.

Troubleshooting

• The test never appears: put the platform trigger into listening or test mode, then send a fresh leadmaps test.
• The production workflow stopped: confirm that you switched from a test URL to the platform’s production URL and activated the workflow.
• The bridge action returns 401: replace the API key or give it the integrations:write scope. Do not use an ingest-only or read-only key.
• The bridge action returns 404: confirm that the lead id belongs to the workspace in the request URL.
• A workflow ran twice: make the downstream action idempotent with the delivery id or idempotency key.