Integration Patterns

Overview

Lead Distro AI integrates with your existing tools through three patterns: direct integrations (Google Sheets, Meta Ads, Blacklist Alliance — managed in Settings → Integrations), per-buyer webhook delivery (HubSpot, Salesforce, Clio, GoHighLevel, and any other CRM that accepts incoming webhooks), and automation platforms (Zapier, Make, Pabbly) that bridge to systems without native webhook support.

Pick the simplest pattern that works. If the destination CRM accepts webhooks, send directly. If it doesn't, route through Zapier or Make. Every lead carries the full JSON payload from your campaign's field mapping plus standard system fields.

Webhook Delivery (any CRM)

When a buyer's delivery method is set to Webhook, accepted leads are POSTed to their webhook URL as a JSON payload. This works with any CRM, dialer, or automation platform that accepts incoming webhooks — HubSpot, Salesforce, Clio, GoHighLevel, Pipedrive, Close, Zoho, or a custom internal endpoint.

Sample Webhook Payload

{
  "lead_id": "lead_abc123",
  "campaign_id": "campaign_xyz789",
  "buyer_id": "buyer_def456",
  "supplier_id": "supplier_ghi789",
  "status": "ACCEPTED",
  "accepted_at": "2026-05-22T14:32:11Z",
  "first_name": "Maria",
  "last_name": "Garcia",
  "email": "maria@example.com",
  "phone": "+15551234567",
  "state": "TX",
  "zip_code": "75001",
  "source": "facebook_lead_ad",
  "custom": {
    "incident_date": "2026-05-15",
    "case_type": "auto_accident"
  }
}

HubSpot

Send accepted leads into HubSpot as Contacts (and optionally as Deals) using HubSpot's incoming webhook workflow. HubSpot has no native concept of an inbound webhook for Contact creation, so the recommended path is a HubSpot Workflow triggered by a custom webhook.

Setup Steps

• In HubSpot: Go to Automation → Workflows → Create workflow. Choose Start from scratch → Contact-based.
• Set the enrollment trigger to Webhook and copy the webhook URL HubSpot provides.
• Add workflow actions: Create or update contact mapping email (primary identifier), firstname (from first_name), lastname (from last_name), phone, state, plus any custom HubSpot properties you've created.
• In Lead Distro AI: Edit the buyer, set Delivery Method to Webhook, paste the HubSpot webhook URL.
• Optional: add custom headers in the buyer's webhook config if HubSpot requires an authentication header.
• Send a test lead from the buyer's Test Send tool to confirm the contact appears in HubSpot.

Salesforce

Push leads into Salesforce as Lead records using Salesforce's Web-to-Lead endpoint or a Flow with a webhook trigger. Both work; Web-to-Lead is simpler for standard fields, Flow is more flexible for custom fields and validation.

Path A: Web-to-Lead (simplest)

• In Salesforce: Go to Setup → Web-to-Lead and generate a Web-to-Lead form. Note the oid value (your Salesforce org ID).
• Copy the field names Salesforce expects: first_name, last_name, email, phone, company, plus any custom Lead fields.
• In Lead Distro AI: Edit the buyer, set Delivery Method to Webhook, set the URL to https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8.
• Set the Content-Type to application/x-www-form-urlencoded and map your Lead Distro fields to Salesforce field names (including the required oid value).
• Test with a single lead and confirm it appears under Leads in Salesforce.

Path B: Salesforce Flow with HTTP trigger (more flexible)

• In Salesforce: Build a Flow triggered by an HTTP Callout or an Apex REST endpoint. This handles custom fields, validation, and de-duplication on the Salesforce side.
• Generate an authenticated webhook URL (typically requires a Connected App + OAuth flow for production).
• In Lead Distro AI: Set the buyer's webhook URL to your Salesforce endpoint and add the Bearer token in Custom Headers.

Clio (law firm CRM)

Clio is the dominant case-management platform for personal injury and other law firms. Lead Distro AI sends new leads into Clio as Contacts (or Matters if you're pre-creating intake records) via Clio's API or via Clio Grow's webhook intake.

Path A: Clio Grow inbound webhook (recommended for intake)

• In Clio Grow: Go to Settings → Inboxes → Create inbox. Select Webhook as the source.
• Copy the webhook URL Clio Grow generates. Clio Grow auto-creates a new lead in your intake pipeline for every POST.
• Map the Clio Grow fields: first_name, last_name, email, phone, state, referral_source, practice_area.
• In Lead Distro AI: Edit the buyer (the law firm receiving these leads), set Delivery Method to Webhook, paste the Clio Grow URL.
• Set custom field mappings so MVA-specific fields (incident date, case type, vehicle type, attorney representation status) land on the right Clio Grow fields.

Path B: Clio Manage API (post-intake automation)

• Use Clio Manage's API at https://app.clio.com/api/v4/contacts.json for direct Contact creation. Requires an OAuth access token from a Clio app you register.
• In Lead Distro AI: Set the buyer's webhook URL to the Clio API endpoint and include the OAuth token in Custom Headers as Authorization: Bearer .
• Map fields per Clio's Contact schema (name, email_addresses, phone_numbers, addresses, custom_field_values).

Google Sheets

Connect Google Sheets to deliver leads as spreadsheet rows. This is the simplest delivery method for buyers who don't run a CRM — every accepted lead appends as a new row with timestamps and field-mapped columns.

• In Lead Distro AI: Go to Settings → Integrations → Google Sheets and click Connect.
• Authenticate with the Google account that owns the destination spreadsheet.
• Edit the buyer, set Delivery Method to Google Sheet, and select the target spreadsheet + tab.
• Columns auto-populate from your campaign's field mapping. Reorder via the column-mapping UI.

Slack Notifications

Set up Slack notifications two ways: a global Slack webhook for system-wide alerts (set in Settings → Notifications), or per-event automations that fire only on specific triggers like a lead acceptance from California.

• In Slack: Create an incoming webhook via Slack apps → Incoming Webhooks → Add to Slack. Pick the channel and copy the webhook URL.
• In Lead Distro AI: For global alerts, paste the webhook into Settings → Notifications. For event-triggered alerts, create an Automation with action type Slack and add conditions (e.g., lead.accepted AND state == CA).
• Customize the message template with merge fields like {{first_name}}, {{buyer.name}}, {{revenue}}.

Zapier / Make / Pabbly

If your destination CRM doesn't support inbound webhooks, route through an automation platform. Two flow directions are supported: inbound (automation platform → Lead Distro AI ingest API) and outbound (Lead Distro AI webhook → automation platform → CRM).

Inbound: Send Leads INTO Lead Distro AI

Use the ingest API as a destination in any automation step. Useful when your lead source is a Typeform, Calendly intake, Facebook Lead Form not connected via Meta integration, or a legacy CRM.

Method:    POST
URL:       https://app.leaddistro.ai/api/v1/ingest
Headers:   Content-Type: application/json
           x-api-key: <your supplier API key>
Body:      JSON with flo_campaign_id, flo_supplier_id, and lead fields

Outbound: Send Leads from Lead Distro AI to a Tool Without Webhook Support

Set the buyer's delivery method to Webhook with the Zapier/Make catch-hook URL. The automation platform receives the JSON and fans out to whatever destination it supports (Airtable, Notion, Monday, ClickUp, etc.).

Meta Ads (Ad Spend + CAPI + Lead Forms)

Meta Ads is a deeper integration with its own dedicated page — covers ad spend sync, server-side conversion events via the Conversions API (CAPI), and direct ingestion from Facebook Lead Form ads.

See the Meta Ads Integration doc for the full setup walkthrough.

Blacklist Alliance (TCPA scrub)

Connect Blacklist Alliance with your own API key in Settings → Integrations. Every ingested lead is checked against Blacklist Alliance's TCPA litigator database before being distributed. Matches are rejected at the campaign level before reaching any buyer. You pay Blacklist Alliance directly using your account.

• Override the campaign default per-supplier — always scrub a risky supplier or skip a trusted one.
• Set a daily lookup cap so a runaway supplier can't run up your Blacklist Alliance bill.
• Get a Slack alert the first time the daily cap is hit each day.

TrustedForm (consent certificates)

Connect TrustedForm with your own API key in Settings → Integrations. When a lead arrives with a trustedform_cert_url, Lead Distro AI claims the consent certificate and verifies the lead's email and phone against what the consumer typed on the form. Mark the field required to reject leads with a failed or mismatched certificate, or leave it optional to capture the signal. You pay TrustedForm directly. Full walkthrough in the TrustedForm Integration doc.

Jornaya (LeadiD consent tokens)

Connect Jornaya (LeadiD) with your own API key in Settings → Integrations. When a lead arrives with a jornaya_leadid token, Lead Distro AI verifies the token is authentic and pulls back consent metadata, storing the result on the lead. Many buyers accept either a TrustedForm certificate or a Jornaya token, so supporting both lets you take leads from any supplier. You pay Jornaya directly. Full walkthrough in the Jornaya Integration doc.

Trestle (phone validation + identity)

Connect Trestle with your own API key in Settings → Integrations. Trestle validates phone numbers and grades lead quality at ingest, with five products you can toggle (Phone Validation, Real Contact A to F grade, caller ID, reverse phone, reverse address). Results are stored on the lead and feed AI scoring. Enable it per campaign and set a daily lookup cap to control spend. You pay Trestle directly. Full walkthrough in the Trestle Integration doc.