Back to Integrations

Go High Level

Use a Custom Webhook action in a Go High Level (GHL) workflow to send JSON to the LeadExec v2 receiver with API key authentication. Ideal for form submissions, pipeline events, or contact creation triggers.

Source Type:
CRM/Website Forms/Workflows

Delivery Method:
JSON Webhook (v2)

Integration Type:
Workflow/Form → LeadExec ingestion

Overview

Use a Custom Webhook action in a Go High Level (GHL) workflow to send JSON to the LeadExec v2 receiver with API key authentication. Ideal for form submissions, pipeline events, or contact creation triggers.

How it works
  1. Trigger: Form submission / contact created / workflow event.
  2. Action: Workflow Custom Webhook posts JSON to LeadExec v2.
  3. Processing: LeadExec authenticates via API key, validates, and routes.
Prerequisites
  • GHL account with access to Workflows
  • LeadExec v2 Posting Instructions and an API Key (Access Keys)
  • Target LeadExec campaign/source prepared for v2 ingestion
Setup
  1. In LeadExec, generate/copy your v2 endpoint and API Key from Posting Instructions.
  2. In GHL Workflows, choose a trigger (e.g., Form Submission).
  3. Add Custom Webhook action:
    • Method: POST
    • URL: LeadExec v2 receiver
    • Headers: Authorization: , Content-Type: application/json
  4. Build the JSON body using GHL merge fields mapped to LeadExec field names.
  5. Save, publish, and test.
Example (JSON – v2)
POST https://leads.leadexec.net/v2/insert/general
Authorization: <YOUR_API_KEY>
Content-Type: application/json

{
  "source": { "vid": 1234, "aid": 1234, "lid": 1234, "sendDelay": 0.0, "returnUrl": "" },
  "leads": [
    {
      "properties": { "reference": "", "noSell": false, "orderID": "", "offerIds": "[]" },
      "fields": {
        "FirstName": "{{contact.first_name}}",
        "LastName": "{{contact.last_name}}",
        "Email": "{{contact.email}}",
        "Phone": "{{contact.phone}}"
      }
    }
  ]
}
Testing
  • Use a test contact or submit a form tied to the workflow.
  • Confirm receipt in LeadExec; review v2 logs for payload/auth errors.
Troubleshooting
  • 401/403: Check API Key header and scope.
  • 400: Validate JSON structure and required fields.
  • Incorrect routing: Confirm vid/aid/lid values.
FAQs

Can I batch leads? Yes—include multiple items inside "leads": [...].
Do I have to use v2? Recommended for JSON-based webhook flows and advanced control.

See also / CTA

Amazing support is at the heart of everything we do.

ClickPoint provides 24 hour chat support, extensive product documentation, and weekly training sessions.