HubSpot integration

Yes — but honestly: HubSpot needs a middleware step. Our platform POSTs each delivered lead to a webhook URL you set. HubSpot has no no-code trigger to catch an arbitrary webhook and create a contact, so you route our webhook through Zapier or Make (both have HubSpot actions) or a small custom endpoint that calls the HubSpot API. There's no native app — and we'd rather say the middleware step is required than let you find out after purchase.

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 HubSpot app and no marketplace listing — there's a documented, retrying, signed webhook that HubSpot (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 HubSpot on-ramp.

How to receive it in HubSpot

A middleware step is required for HubSpot: it doesn't ingest an arbitrary inbound webhook into the CRM directly. Zapier or Make is the fastest route; a custom serverless endpoint that verifies the signature and calls the HubSpot API is the developer route.

1. Choose your connector. Zapier or Make (no-code), or a custom endpoint calling the HubSpot CRM API (developer).
2. Create the receiving hook. In Zapier use Catch Hook; in Make use a Custom webhook; for custom, expose an HTTPS endpoint. Copy its URL.
3. Set that URL in our Settings. Paste it into Webhook URL and save; click Generate secret (shown once). Delivery won't fire without a secret.
4. Add the HubSpot action. In the connector, add HubSpot → Create/Update Contact and map lead.email, lead.full_name, lead.phone from the production payload above. Use delivery_id for idempotency.
5. Turn it on. Enable the connector; leads now create HubSpot contacts on delivery.

What this will not do

• No native HubSpot app and no one-click install.
• HubSpot can't receive our webhook directly — a middleware connector is required.
• No two-way sync — we don't read from HubSpot.
• No automatic field mapping — you map fields once in the connector.

Common questions

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