Send new leads to Zapier

Every time someone verifies their email or phone in Fern, we email you. Connecting Zapier lets that same lead flow anywhere else you want it — your CRM, a Google Sheet, a Slack channel, a text message to whoever is on call.

Before you start

Zapier's Webhooks by Zapier is a premium Zapier feature, so you'll generally need a paid Zapier plan to use it. If you're on Zapier's free tier and this doesn't work, email support@curbsight.ai — we'd like to know, because it affects what we build next.

You don't need Zapier at all if your tool can accept a webhook directly. See Webhook payload reference.

Set up your Zap

1. In Zapier, click + Create → Zaps.
2. For the trigger, search for Webhooks by Zapier.
3. Choose the event Catch Hook. Not “Catch Raw Hook” — that one gives you a single blob of text instead of usable fields.
4. Click Continue. Leave “Pick off a Child Key” blank.
5. Copy the webhook URL Zapier shows you, then paste it into a new integration in CurbSight under Integrations → New integration, and save.
6. Still in CurbSight, click Send test event.
   Do this before the next step — Zapier can't find a sample until we've sent one.
7. Back in Zapier, click Continue, then Test trigger. Your sample lead will be waiting.
8. Click Continue with selected record, then build your action — Google Sheets, HubSpot, Gmail, SMS — mapping fields like Lead Email and Lead Address.
9. Publish the Zap and turn it on.

Why step 6 comes before step 7

This trips up almost everyone, so it's worth spelling out. Zapier's Test trigger step doesn't ask us for a sample — it looks for requests that have already arrived at your webhook URL. If nothing has been sent yet, it fails with “We couldn't find a request” and you can't continue.

That's what the Send test event button in CurbSight is for. Click it first, and the sample will be waiting when Zapier goes looking. The sample has every field filled in, so you can map all of them even if a particular real lead leaves some blank.

What you can map

Once Zapier has your sample, you can map any of these into your action step. The full list with types and meanings is in the webhook payload reference.

• Contact — email, phone, and which one they verified.
• Property — street address, latitude and longitude, and whether it's in your service area.
• The brief — their goals, style, budget, requested features, and any free-text feedback.
• Media — the before photo, the generated concept image, and a link to their Design Vision PDF.

Lists like goals and features arrive two ways: a ready-made comma-separated string (Curb appeal, Low maintenance) and a separate list field. For Zapier, the comma-separated one is almost always what you want.

Checking it works

Open your integration in CurbSight and look at Recent requests. Every attempt is listed with the response code your endpoint returned, how long it took, and — if you expand a row — exactly what we sent and exactly what came back.

If a delivery fails we retry it six times over about seven hours, backing off between attempts. You'll see the retry count on the row. If an endpoint fails five leads in a row we pause the integration and show you why, so a dead Zap doesn't silently swallow your leads forever. Fix the URL and hit Resume.

Troubleshooting

• “We couldn't find a request” in Zapier — you skipped step 6. Click Send test event in CurbSight, then retry the trigger test.
• Fields show up as one blob of text — you picked “Catch Raw Hook” instead of “Catch Hook”. Start the trigger over.
• Some fields aren't offered in the mapper — Zapier builds its field list from the sample it caught. Send a fresh test event and re-run Test trigger.
• Nothing arrives for real leads — check the Zap is published and switched on. A Zap left in draft never runs.
• The integration paused itself — your endpoint returned errors on five leads in a row. The reason is shown on the integration page.

Deliveries can arrive out of order, and a redelivery you trigger by hand will create a second record in your connected app. If you need to guard against duplicates, use the id field in the payload — it's unique per delivery.