Skip to main content
Follow this step-by-step guide to configure your outbound webhook dispatcher, send your first payload, and handle the returned lead ID.

3-Step Setup Overview

1

Obtain Your Partner Source Token

Your 3i client or account manager provides your dedicated x-source-token (UUID).
Where Agents Find This in 3i CRM:
The agent opens Data & Integrations → Lead Sources, clicks on their vendor source, and copies the token displayed under Gateway URL (per-vendor token).
2

Configure Your Webhook Dispatcher

Configure your server or webhook engine with the following destination parameters:
  • Endpoint URL: https://api.3i.life/functions/v1/inbound-lead-gateway
  • HTTP Method: POST
  • Headers:
    • Content-Type: application/json
    • x-source-token: <YOUR_ASSIGNED_TOKEN>
    • Idempotency-Key: <UNIQUE_UUID_PER_DELIVERY>
3

Dispatch Your Payload & Store lead_id

Send your lead data. 3i processes the payload, creates or updates the record, and returns a JSON response containing our internal lead_id. Store this ID in your database to correlate future updates.
Already have an existing JSON payload format? You can send your existing field names without rewriting your dispatcher! 3i’s ingestion engine automatically detects aliases (e.g. cellphone, coverage_requestedcoverage_amount) and preserves all custom parameters in custom_fields with zero data loss.

Using No-Code Tools? (Zapier, Make, n8n, GoHighLevel)

Prefer visual setup over custom code? Follow our step-by-step guides for connecting Webhooks by Zapier, Make.com HTTP modules, n8n, or GoHighLevel workflows.

Code Examples

Select your programming language or tool below for a complete, production-ready dispatch script:

Response Verification

Every successful request returns HTTP 200 with the assigned lead_id:
Best Practice: Save response.data.lead_id in your local database or CRM tracking table. When reviewing conversions, checking delivery receipts, or querying status, this UUID links the record directly across both platforms.