Jobber + FirstFiveMin
New Jobber requests become FirstFiveMin leads.
Jobber connects through its Zapier app: when a new client or request appears there, the Zap forwards it to FirstFiveMin the moment it lands.
Endpoint
POST https://firstfivemin.com/api/speed-to-lead/channel-inbound.phpSteps
- In FirstFiveMin, create a connection key (Integrations → Connections, "Send leads in").
- In Zapier, choose Jobber as the trigger app — "New Client" or "New Request".
- Add a "Webhooks by Zapier" POST action to the URL below, JSON payload, with the Authorization header from the Zapier recipe.
- Map: client first name → first_name, last name → last_name, phone → phone, email → email, and the request details → property_ref.
- Map idempotency_key to MATCH your trigger: for a new-request trigger use the request ID, never the client ID — a repeat client's second request would carry the first request's key and be silently swallowed as a duplicate.
- This recipe deliberately sends NO consent block: a new client record is not, by itself, consent to an AI call. The lead is captured and visible on your dashboard, and nobody is auto-dialed. If your own intake genuinely records call consent, add the consent block exactly as in the Zapier recipe.
About 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. Leave it out and we still capture the lead — we just will not have the AI call them.
Sample payload
{
"source": "zapier",
"first_name": "Avery",
"last_name": "Sample",
"phone": "+15550170005",
"email": "avery.sample@example.invalid",
"property_ref": "Lawn service request \u2014 new client",
"language": "en",
"source_event_at": "2026-08-27T15:04:05Z",
"idempotency_key": "jobber-recipe-example"
}