Webhooks and Zapier: send your leads, jobs and payments to other tools

Leads in from anywhere, and new leads, approved quotes, jobs and payments out to Zapier, Make or your own server.

Updated October 1, 2026

Set it up once and nothing gets typed twice: a lead from any form lands in CrewRobin, and what happens next goes to your other tools by itself.

Leads in

Leads › Lead form & settings has a lead address. Any form, or a Zapier "Webhooks by Zapier: POST" step, can send leads to it (name, phone, email, address, ZIP and what they need). Developers can use the lead API with an API key instead. Every lead gets a customer record, a text straight away and your speed-to-lead call.

Events out

Go to Settings › Webhooks (account owner only) and click Add webhook. Paste the address to send to and tick the events:

  • lead.created: a new lead comes in
  • quote.approved: a customer approves a quote (with the total and any deposit)
  • job.scheduled and job.completed
  • invoice.paid: an invoice is paid in full

Click Send a test to check it. Each webhook shows its last few deliveries and what came back; a failed one is tried again after 1 minute and after 10 minutes, and Send again retries it by hand. Pause stops sending without deleting it.

With Zapier

  1. In Zapier, start a Zap with Webhooks by Zapier › Catch Hook and copy its URL.
  2. In CrewRobin, Add webhook, paste it, tick your events and save.
  3. Click Send a test, then Test trigger in Zapier, and use the fields in your next steps (a Google Sheet, your email list, your accounting app).

For developers

Each POST is JSON {"id", "event", "created", "data"} with X-Webhook-Event, X-Webhook-Id, X-Webhook-Timestamp and X-Webhook-Signature headers. The signature is v1= and the hex HMAC-SHA256 of timestamp.body with the webhook's signing secret (shown on the page). Example bodies for every event are at the bottom of Webhooks.