Better Business Leads

Zapier integration

Point our signed webhook at a Zapier Catch Hook and route every delivered lead to 6,000+ apps.

Yes — you can send every delivered lead straight into Zapier. Our platform POSTs each lead to a webhook URL you control; set that URL to a Zapier "Catch Hook" and Zapier becomes the router to your CRM and everything else. There's no native app to install — Zapier is the integration layer, which is exactly what makes it work with any of its apps.

What you actually get

One thing, and it's the same for every CRM: a signed webhook. The moment a lead is delivered to your account, our platform sends an HTTP POST to the URL you set in Settings, with a JSON body and an HMAC-SHA256 signature so you can verify it came from us. There is no native Zapier app and no marketplace listing — there's a documented, retrying, signed webhook that Zapier (directly or through a middleware step) can receive. A webhook that works with anything is more than most lead vendors offer.

The payload

Every delivery POSTs this body (fake values; the structure is exactly what we send):

{
  "event": "lead.delivered",
  "delivery_id": "e3b0c442-98fc-1c14-9afb-4c8996fb9242",
  "lead_id": "9f1a2b3c-4d5e-6f70-8a9b-0c1d2e3f4a5b",
  "vertical": "business_loans",
  "delivered_at": "2026-08-04T18:24:07.512Z",
  "lead": {
    "full_name": "Jane Borrower",
    "email": "jane@example.com",
    "phone": "+18135550148",
    "amount_requested": 60000,
    "...": "the full borrower field payload — fields vary by vertical"
  },
  "trustedform_cert_url": "https://cert.trustedform.com/2vv…",
  "consent_version": "v2.0"
}

lead is the full borrower record — the same fields you see in the portal and email — and its contents vary by vertical. The request carries three headers: X-BBL-Timestamp (unix seconds), X-BBL-Signature (lowercase hex HMAC-SHA256 of `${timestamp}.${rawBody}` keyed with your signing secret), and X-BBL-Delivery-Id (use it as an idempotency key). The full reference — signature verification code, the retry ladder, and manual replay — lives on the webhook & CRM docs page; this page is just the Zapier on-ramp.

How to receive it in Zapier

Zapier is the middleware step here by design: our webhook is the trigger source, and Zapier's actions do the field mapping and delivery into your destination app.

  1. Create a Zap with a Catch Hook trigger. In Zapier, add a new Zap and choose Webhooks by Zapier → Catch Hook as the trigger. Zapier gives you a custom webhook URL — copy it.
  2. Set that URL in our Settings. Paste the Catch Hook URL into Webhook URL in your portal Settings and save.
  3. Generate a signing secret. Click Generate secret in Settings. It's shown once — store it in your Zapier account or password manager. Our platform won't send the webhook until a secret exists.
  4. Confirm delivery reaches Zapier. Use Send test in Settings to POST to your Catch Hook and confirm Zapier receives a request. Build your field mapping from the production payload shape above — not from the test sample, which is a reachability check only.
  5. Map the fields and add actions. In Zapier, map lead.email, lead.full_name, lead.phone and the vertical fields to your CRM's create/update action. Use delivery_id as the dedupe key.
  6. Turn the Zap on. Publish the Zap. New leads now flow to Zapier the second they're delivered.

What this will not do

  • No native or listed Zapier app — you use the generic Catch Hook trigger.
  • Zapier won't verify the HMAC signature without a Code by Zapier step.
  • No two-way sync — this is one-directional (leads out to you); we never read back from Zapier.
  • No automatic field mapping — you map fields in the Zap once.

Common questions

Can I send Better Business Leads to Zapier?

Yes. Create a Zap with the 'Webhooks by Zapier — Catch Hook' trigger, copy its custom URL, and set it as your webhook URL in our Settings. Every delivered lead is then POSTed to that Catch Hook, and you route it onward to any of Zapier's apps.

How do I map the fields in Zapier?

Map from the production payload paths: lead.email, lead.full_name, lead.phone, and the vertical-specific fields inside lead, plus vertical and delivery_id at the top level. Use delivery_id as an idempotency key so a retry doesn't create a duplicate contact.

Can Zapier verify the HMAC signature?

Not on its own. The Catch Hook accepts the JSON but can't recompute the HMAC. If you need to verify the X-BBL-Signature, add a 'Code by Zapier' step that recomputes it (see the webhook docs), or keep the Catch Hook URL secret and rely on the delivery_id for idempotency.

Is there a native Zapier app?

No — and you don't need one here. Zapier is the middleware: our signed webhook is the source, and Zapier fans it out to your CRM, spreadsheet, Slack, or anything else in its catalog.

Reference: the webhook & CRM docs. Pricing: lead pricing.