Skip to content

← All help articles

Automation recipes: Zapier, Make, n8n, webhooks and field-service apps

Automation recipes

Wherever your leads are born, a website form, a CRM, a field-service platform, an ad account, FirstFiveMin captures them the moment they arrive. The Automation recipes page (linked from Integrations under "Step-by-step recipes") has a tested recipe per platform: Zapier, Make, a native webhook, n8n, Housecall Pro and Jobber. Every recipe on that page is exercised by our own tests against the real endpoint, so the steps you read are steps that work.

The pattern every recipe follows

  1. On Integrations → Connections, create a connection key with Send leads in ticked. Copy it once.
  2. In your automation, add an HTTP step that POSTs JSON to the endpoint shown on the recipe page, with the header Authorization: Bearer <your key>.
  3. Map the lead fields (name, phone, email, what they asked about) and an idempotency key that is unique per submission: the Zap run id, the Make bundle id, the n8n execution id, your form's submission id. Never a customer or record id, or a second submission by the same person would be dropped as a replay.
  4. Send a test. The lead appears on your Leads page within seconds.

The consent block

Only fill in the consent block if the person actually agreed to be contacted and you can produce the record that proves it: where they agreed, the reference, and when. With a complete block the lead is callable and your claim window opens. Leave it out and we still capture the lead; the assistant just will not call them.

The Housecall Pro and Jobber recipes connect through Zapier and deliberately send no consent block: a "new customer" or "new request" event in those apps is not consent to be called.

n8n

Three ready-made workflows are importable in one click: intake → FirstFiveMin (with per-execution idempotency), new lead → a spreadsheet (phone last four only), and opt-out → your CRM's do-not-call list.

Common problems

  • 401 from the endpoint: the key was revoked, or it lacks the Send leads in permission.
  • "replay protection degraded" on the connection: fix the idempotency mapping to a per-submission id.
  • The lead arrived but was never called: no consent block, or the block was incomplete. A half-filled block is refused, never guessed.
Get started