Housecall Pro + FirstFiveMin
New Housecall Pro customers become FirstFiveMin leads.
Housecall Pro connects through its Zapier app: when a new customer or job appears there, the Zap forwards it to FirstFiveMin so nothing waits in a queue you have to remember to check.
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 Housecall Pro as the trigger app — "New Customer" (or "New Job" if you want each job to open a fresh follow-up).
- Add a "Webhooks by Zapier" POST action to the URL below, JSON payload, with the Authorization header from the Zapier recipe.
- Map: customer first name → first_name, last name → last_name, mobile number → phone, email → email, and the job description → property_ref.
- Map idempotency_key to MATCH your trigger: for a "New Customer" trigger use the customer ID; for a "New Job" trigger use the job ID. Never pair New Job with the customer ID — a repeat customer's second job would then carry the first job's key and be silently swallowed as a duplicate.
- This recipe deliberately sends NO consent block: a new customer 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": "Morgan",
"last_name": "Sample",
"phone": "+15550170004",
"email": "morgan.sample@example.invalid",
"property_ref": "Water heater replacement \u2014 new customer",
"language": "en",
"source_event_at": "2026-08-27T15:04:05Z",
"idempotency_key": "hcp-recipe-example"
}