GoHighLevel integration

Yes — delivered leads can flow straight into GoHighLevel. Our platform POSTs each lead to a webhook URL you set; GoHighLevel's workflow Inbound Webhook trigger receives that POST and creates or updates a contact. There's no native app to install — you wire our webhook to GHL's inbound trigger, which works on any plan that exposes it.

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

How to receive it in GoHighLevel

1. Create a workflow with an Inbound Webhook trigger. In GoHighLevel, build a workflow and add the Inbound Webhook trigger. Copy the webhook URL it generates.
2. Set that URL in our Settings. Paste it into Webhook URL in your portal Settings and save.
3. Generate a signing secret. Click Generate secret — shown once, so store it. Delivery won't fire until a secret exists.
4. Send a sample and map fields. Use Send test in Settings to give the trigger a request, then map lead.email, lead.full_name, and lead.phone to contact fields using the production payload shape above.
5. Add your workflow actions. Add Create/Update Contact, then any follow-up (SMS, pipeline stage, notification). Use delivery_id to avoid duplicates on a retry.
6. Publish the workflow. Turn it on. Leads now create GHL contacts the moment they're delivered.

What this will not do

• No native GoHighLevel marketplace app — you use the workflow Inbound Webhook trigger.
• GHL can't verify the HMAC signature natively — add middleware if you require verification.
• No two-way sync — leads flow one direction, into GHL.
• No automatic field mapping — you map fields once in the workflow.

Common questions

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