Zapier

Built inAutomation

If your tool is on Zapier, your bookings can reach it.

Add a signed webhook in your dashboard, pointed at a Zapier webhook trigger. Every event you pick arrives as JSON your Zap can pass on to anything Zapier connects to.

From a caught lead

Into Zapier

  • New bookingTrigger for your Zap
  • Appointment heldTrigger with the revenue you entered
  • New lead, escalation, call endedTriggers for anything else you build

Built into CaughtLeads and working today.

How it connects

Working from day one

This connection is part of the product itself. You switch it on from your dashboard, and we will walk you through it if you want a hand.

  1. Start a Zap with a webhook trigger

    In Zapier, start a Zap with the Webhooks by Zapier Catch Hook trigger and copy the URL it gives you.

  2. Add it in CaughtLeads

    Open Connections in your dashboard, choose Webhook, paste the URL, and pick the events.

  3. Send a test event

    One click sends a test event, so Zapier has a sample to map from.

  4. Finish the Zap

    Map the fields into the app you want. The Zap is yours to change anytime.

Questions about the Zapier connection

Do I need a Zapier account?

Yes. The Zap runs on your own Zapier account, so you own the automation. Check Zapier's plans for webhook triggers.

Can I check a request really came from CaughtLeads?

Yes. Every request is signed to the Standard Webhooks spec, and the signing secret is shown once, when you create the connection.

What data is sent?

Ids, the service, times, the business name, and the caller's number on events about reaching them. A new booking also carries what a field-service tool needs to book the job: the caller's name, email, and service address as captured on the call, and a short call summary. Never the transcript.

Stop losing leads in the handoff.

Twenty minutes. We will show you a call getting answered, booked, and landing in Zapier.

Try it free