Clio Integration
Connect Lead Distro AI to Clio for personal injury and law firm lead intake. Clio Grow inbound webhook setup, Clio Manage API, MVA-specific custom field mapping, and FAQs.
Last updated:
What This Integration Does
Sends accepted Lead Distro AI leads into Clio Grow (intake CRM) or Clio Manage (case management) so personal injury, MVA, and other law firm clients receive leads directly in the workflow attorneys already use. Two supported paths — Clio Grow's inbound webhook for intake, Clio Manage's API for post-intake automation.
Picking a Path
| Use case | Path | Why |
|---|---|---|
| MVA / PI firm lead intake (most common) | A — Clio Grow inbound webhook | Leads land in the intake pipeline attorneys actively review. Built for this exact use case. No OAuth setup. |
| Direct contact creation in Clio Manage | B — Clio Manage API | When the firm wants leads to bypass intake and land as Contacts immediately (rare — usually a firm with existing intake automation). |
| Both | Run both | Webhook to Clio Grow for intake + API to Clio Manage for instant Contact creation. Two delivery automations on the same buyer. |
Path A — Clio Grow Inbound Webhook (Recommended)
Step 1 — Create the Clio Grow Inbox
- In Clio Grow, go to Settings → Inboxes → Create Inbox.
- Choose Webhook as the source.
- Name the inbox something traceable like `Lead Distro AI — Spanish MVA`.
- Copy the webhook URL Clio Grow generates.
Step 2 — Configure Field Mapping in Clio Grow
Clio Grow auto-creates Lead records from incoming JSON. Map these fields per the Clio Grow Lead schema:
| Lead Distro AI field | Clio Grow field | Required? |
|---|---|---|
| `first_name` | First Name | Yes |
| `last_name` | Last Name | Yes |
| `email` | Yes (for de-dupe) | |
| `phone` | Phone | Yes |
| `state` | State | Recommended |
| `zip_code` | Zip | Optional |
| `source` | Referral Source | Recommended — defaults to 'Lead Distro AI' |
| `custom.case_type` | Practice Area | MVA-specific |
| `custom.incident_date` | Date of Incident | MVA-specific |
| `custom.vehicle_type` | Custom field | MVA-specific |
| `custom.attorney_representation` | Custom field | MVA-specific |
| `lead_id` | Reference (custom) | For tracing |
Step 3 — Wire the Webhook in Lead Distro AI
- In Lead Distro AI, edit the buyer (the law firm receiving these leads).
- Set Delivery Method to Webhook.
- Paste the Clio Grow Inbox URL from Step 1.
- Set Content-Type to `application/json`.
- Save.
Step 4 — Test Send and Confirm Intake View
Use Test Send to fire a sample lead. Within ~2 seconds the lead should appear in the firm's Clio Grow intake pipeline. Have the firm log into Clio Grow and confirm the lead shows up in the right Inbox with the right field mapping — including MVA-specific custom fields.
Path B — Clio Manage API (Direct Contact Creation)
- Register a Clio app at app.clio.com/settings/developer_applications to get a Client ID and Client Secret.
- Run the OAuth flow to get an access token for the firm's Clio Manage account.
- In Lead Distro AI, edit the buyer and set Delivery Method to Webhook.
- Set the URL to `https://app.clio.com/api/v4/contacts.json`.
- Set Content-Type to `application/json`.
- Add a Custom Header `Authorization: Bearer
`. - Map fields per Clio Manage's Contact schema: `name`, `email_addresses`, `phone_numbers`, `addresses`, `custom_field_values`.
Clio Manage OAuth access tokens expire after 7 days. Set up a refresh-token rotation job on your side that updates Lead Distro AI's custom header before each expiry, or use Path A (Clio Grow) which has no token rotation overhead.
Spanish-Language Lead Routing (MVA Vertical)
For Spanish-speaking MVA leads, include a `custom.preferred_language` field in your campaign field mapping. Clio Grow supports custom fields for language — when set, the firm's intake staff sees the language flag immediately and routes to Spanish-speaking intake specialists. This is especially important for Great Marketing AI agencies routing Spanish-speaking MVA leads to PI firms.
Frequently Asked Questions
Should I use Clio Grow or Clio Manage for Lead Distro AI integration?
Clio Grow is the right choice for ~95% of MVA and personal injury firms — it slots leads directly into the intake workflow attorneys already use, requires no OAuth setup, and supports custom MVA-specific fields out of the box. Clio Manage API is for firms that want to bypass intake and create Contacts directly (rare — usually firms with their own intake automation). When in doubt, start with Clio Grow.
Does Lead Distro AI's Clio integration support MVA-specific fields?
Yes. Configure your campaign's field mapping to include MVA fields (`incident_date`, `case_type`, `vehicle_type`, `attorney_representation`, `injury_type`, `medical_treatment`, `police_report`, `at_fault_party`, etc.) and map each to a corresponding Clio Grow custom field. Lead Distro AI's per-buyer webhook payload includes all custom fields nested under `custom`, so Clio Grow receives the full MVA context for intake staff.
How do I route Spanish-speaking MVA leads to the right Clio Grow Inbox?
Add a `preferred_language` custom field at the campaign level. Then either: (1) create a single Clio Grow Inbox and let the firm route by language internally (simpler), or (2) create two Clio Grow Inboxes — English Intake and Spanish Intake — and use two Lead Distro AI buyers with different filters (e.g., `preferred_language == 'es'` for the Spanish buyer). Path 2 gives the firm immediate language-routed intake; Path 1 is simpler for smaller firms.
Can I send a lead to Clio Grow AND another CRM simultaneously?
Yes. A single buyer in Lead Distro AI has one primary delivery method (webhook to Clio Grow) but unlimited automations attached to `lead.accepted` events. Add a second automation that posts the same lead to another CRM webhook in parallel. Both deliveries run independently — Clio Grow failure doesn't block the other CRM and vice versa.
Does the Clio integration support signed webhooks for HIPAA-adjacent verticals?
Lead Distro AI signs every webhook with HMAC-SHA256 (`X-LeadDistro-Signature` header). Clio Grow doesn't natively verify signatures inside Inbox webhooks, but for HIPAA-adjacent verticals you can route through Path B (Clio Manage API) which uses OAuth-authenticated requests — verifying the bearer token + TLS provides equivalent transport security. For full HIPAA compliance, a BAA between you and Clio is also required.
What's the latency between lead acceptance and the lead appearing in Clio?
Typically under 2 seconds end-to-end. Lead Distro AI POSTs the webhook within 500ms of acceptance; Clio Grow processes the inbound and creates the Lead record within another second. The firm's intake staff will see the lead in Clio Grow's intake view within seconds of the lead being ingested into Lead Distro AI.
Can multiple law firms receive leads from the same campaign in Clio?
Yes. Each law firm is a separate Lead Distro AI buyer with its own Clio Grow webhook URL (one per firm's Clio Grow account). Configure distribution method (Round Robin, Weighted, or Priority) at the campaign level to control how leads split across firms. Each firm receives only the leads routed to it and sees those leads in their own Clio Grow Inbox.
How do I track which Lead Distro AI campaign each Clio lead came from?
Map `campaign_id` and `source` to Clio Grow custom fields (or the built-in Referral Source field). Set the Referral Source default per Inbox to `Lead Distro AI`, then use a custom field to capture the specific campaign name. The firm can then segment performance by campaign inside Clio Grow's reporting.
Related Articles
Integration Patterns
Lead Distro AI integrations: Zapier, Make, Google Sheets, Slack, HubSpot, Salesforce, Clio, and custom webhooks. Connect your lead distribution pipeline to every tool in your agency stack.
HubSpot Integration
Send Lead Distro AI leads directly into HubSpot as Contacts or Deals using a HubSpot Workflow webhook. Step-by-step setup, field mapping, troubleshooting, and FAQs.
Salesforce Integration
Push Lead Distro AI leads into Salesforce as Lead records using Web-to-Lead or Flow with an authenticated webhook. Setup paths, daily volume limits, and troubleshooting for enterprise lead distribution.
GoHighLevel (GHL) Integration
Send Lead Distro AI leads into GoHighLevel (GHL) sub-accounts as Contacts, trigger pipelines and SMS sequences, and route per-sub-account using GHL's inbound webhook. Setup, multi-tenant, FAQs.
If you have any questions, send us an email at support@leaddistro.ai