A CRM webhook is an automated HTTP POST endpoint that receives real-time lead data from a delivery platform and creates a new contact record in your case management system. For legal lead delivery, webhooks enable sub-5-second lead transmission from the generation source directly into CRMs like Clio, Filevine, LeadDocket, and MyCase, eliminating manual data entry and enabling immediate speed-to-contact.
Your lead vendor just sent you a lead. It hit their server at 2:04:12 PM. If they deliver via webhook, that lead lands in your CRM at 2:04:15 PM. Three seconds. Your intake coordinator gets an SMS at 2:04:16 PM and dials the prospect at 2:04:30 PM. Total elapsed time: 18 seconds.
If that same vendor delivers via email? The lead sits in a queue. Spam filters check it. Your inbox polls every 2-5 minutes. Someone reads the email, copies the phone number, and manually enters it into your CRM. By the time anyone calls, 8 minutes have passed. In lead conversion terms, that's a lifetime.
Contacting a lead within 60 seconds increases conversion by 391% compared to longer wait times (Velocify, 2015). Webhook delivery is what makes sub-minute contact possible. Every Claim Supply integration uses webhooks by default because there's simply no other delivery method that can keep up.
This guide walks through what webhooks actually are, how to set them up in the five most popular legal CRMs, what the JSON payload looks like, how to test your endpoint before going live, and which automations to wire up once leads start flowing.
TL;DR: A webhook pushes lead data to your CRM in under 5 seconds via an HTTP POST. Email delivery adds 2-10 minutes. Firms using webhooks contact leads 4x faster and convert at significantly higher rates. This tutorial covers endpoint setup for Clio, Filevine, and MyCase, provides an annotated JSON payload example, walks through testing and error handling, and outlines the automations that should fire the instant a lead arrives. If you can copy-paste a URL and click "Save," you can set up a webhook.
What Is a Webhook and Why Does It Matter for Lead Delivery?
A webhook is a server-to-server HTTP POST request. When a prospect fills out a form and becomes a lead, the lead vendor's server sends that data directly to your CRM's server. No email. No manual entry. No delay. The data travels as structured JSON, which your CRM parses and maps into the right fields automatically.
Think of it as the difference between getting a text message and checking your mailbox. The text arrives the moment it's sent. The letter sits in transit for days. In lead delivery, those "days" are minutes, and minutes are the difference between signing a case and losing it to the firm that called first.
Here's why the speed gap matters: law firm utilization rate sits at just 38%, meaning attorneys bill only about 3 hours per 8-hour day on average (Clio 2025 Legal Trends Report, 2025). Intake staff are already stretched thin. Manual lead entry from email notifications wastes the limited time they have. Webhook delivery eliminates that friction entirely.
The data backs this up. Firms using webhook delivery through our platform contact leads 4x faster than those relying on email notifications. That speed advantage translates directly into conversion. When you're buying exclusive leads at $200-$500 each, shaving 8 minutes off your contact time isn't a nice-to-have. It's the difference between a 15% conversion rate and a 25% conversion rate. For a deeper dive into how delivery infrastructure works end-to-end, read our guide on how real-time lead delivery works.
How Do You Set Up a Webhook Endpoint in Your CRM?
The setup process varies by CRM, but the concept is always the same: you generate a unique URL from your CRM, share it with your lead vendor, and the vendor configures their system to POST lead data to that URL. Here's how it works in the five most popular legal CRMs.
Clio is the most widely used legal practice management platform, and their growth product (Clio Grow) makes webhook setup straightforward. Navigate to Settings > Integrations > Webhooks in your Clio Grow dashboard. Click "Create Webhook" and copy the generated URL. Send this URL to your lead vendor. Clio will automatically create a new contact and matter when it receives a properly formatted POST request. You can map incoming fields to Clio's contact fields directly in the webhook configuration panel. The whole process takes about 5 minutes.
Filevine handles inbound leads through its API and automation engine. In your Filevine workspace, go to Admin > API Settings and generate an API token. Your lead vendor will use this token to authenticate POST requests to Filevine's /contacts or /projects endpoints. Filevine's advantage is its powerful automation layer: you can set up rules that auto-create a project (case), assign a team, and trigger task sequences the moment a lead hits the system. The API documentation at developer.filevine.io covers the full endpoint specification.
MyCase accepts leads through its REST API. Go to Settings > Integrations and locate your API credentials. MyCase uses a /leads endpoint that accepts contact information, case type, and custom fields. One detail worth noting: MyCase rate-limits API calls to 60 per minute, which is more than enough for lead delivery (you're not getting 60 leads per minute) but matters if you batch-import aged leads. Refer to MyCase Help Center for current API documentation.
Litify is built on Salesforce, so it inherits Salesforce's robust webhook infrastructure. You can create a Web-to-Lead form in Salesforce Setup that generates a POST endpoint, or use Salesforce Flow to build a custom webhook listener. The Salesforce approach is more powerful but requires Salesforce admin knowledge. Most Litify firms have a Salesforce admin on retainer who can configure this in under an hour.
PracticePanther supports integrations through both its REST API and middleware platforms like Zapier. If you're not technical, the Zapier route is easiest: create a Zap with "Webhooks by Zapier" as the trigger and "PracticePanther" as the action. Your vendor POSTs to the Zapier webhook URL, and Zapier creates a new contact in PracticePanther. Latency adds roughly 1-3 seconds compared to a direct integration.
If your CRM isn't listed here, the pattern is the same. Look for "API," "Webhooks," or "Integrations" in your settings menu. If your CRM doesn't support webhooks natively, middleware like Zapier or Make can bridge the gap.
What Does a Lead Delivery Webhook Payload Look Like?
When a lead vendor sends you a lead via webhook, the data arrives as a JSON object in the body of an HTTP POST request. Here's an annotated example of what Claim Supply sends to your endpoint. Every vendor's payload will look slightly different, but these core fields are standard across the industry.
Let's break down the key field groups. Contact information is what your intake team needs to call the prospect. Phone number formatting matters; the E.164 format (+13055551234) is the international standard and what most CRMs expect. If your CRM doesn't accept the +1 prefix, you can strip it during field mapping.
Case details let you pre-qualify before calling. If has_attorney is true, that lead already has representation and you may want to route it differently or skip the call. If at_fault is true, the case viability changes. These fields save your intake team from spending 5 minutes on a call only to discover the prospect isn't a fit.
Compliance fields are your legal protection. The trustedform_url is a timestamped certificate proving the prospect gave consent to be contacted. Store this URL in your CRM. If you're ever hit with a TCPA claim, this certificate is your primary evidence. For more on how these compliance fields work in practice, see our complete guide to buying MVA leads.
Delivery metadata tells you whether this is an exclusive or shared lead, which order it belongs to, and whether this is the first delivery attempt or a retry. The delivery_attempt field helps you avoid duplicate entries: if you see delivery_attempt: 2, check whether lead_id already exists in your CRM before creating a new record.
How Do You Test and Validate Your Webhook?
Never go live without testing first. A misconfigured webhook means leads hit a dead endpoint while you assume everything is working. Here's a 4-step testing process we walk every Claim Supply client through.
Step 1: Verify your endpoint with a request inspector. Before connecting anything to your CRM, use a tool like Webhook.site or RequestBin to generate a temporary URL. Share that URL with your vendor and ask them to send a test payload. This lets you see the exact JSON your CRM will receive, without risking your production system. Check that all expected fields are present, data types match (strings, booleans, timestamps), and the payload isn't truncated.
Step 2: Map fields in a staging environment. Most CRMs let you create a test workspace or sandbox. Configure your field mapping there first. Map first_name to your CRM's "First Name" field, phone to "Phone Number," case_type to your custom "Practice Area" field, and so on. Run 3-5 test leads through and verify each field populates correctly.
Step 3: Test error handling. What happens when your CRM returns a 500 error? What if the payload is missing a required field? Good lead vendors implement retry logic: they'll attempt delivery 3 times with exponential backoff (immediately, then at 30 seconds, then at 2 minutes). Ask your vendor about their retry policy. On your side, make sure your CRM returns proper HTTP status codes: 200 for success, 400 for bad input, 401 for authentication failures.
Step 4: Go live with monitoring. Once field mapping looks correct in staging, switch to your production endpoint. Run 5-10 real leads through before confirming to your vendor that everything is stable. Set up alerting so you get notified if your endpoint starts returning errors. A simple uptime monitor that pings your webhook URL every 5 minutes catches outages before they cost you leads.
Common errors we see during setup: expired API tokens (CRM rotates credentials automatically), incorrect Content-Type headers (your CRM expects application/json but receives application/x-www-form-urlencoded), and firewall rules blocking incoming POST requests from unfamiliar IP addresses. Whitelist your vendor's IP range if your CRM sits behind a firewall.
What Automations Should Fire When a Lead Arrives?
Getting the lead into your CRM is step one. What happens in the next 60 seconds determines whether that lead becomes a signed case or a wasted $300. Here are the five automations every firm should have running the moment a webhook lead lands.
1. Instant SMS to the intake coordinator. Your CRM should send a text message to your designated intake person within 2 seconds of the lead arriving. The message should include the prospect's first name, phone number, case type, and accident state. Something like: "New MVA lead: Maria G. - (305) 555-1234 - FL - not at fault - call now." This SMS is the trigger that gets someone dialing within 15-30 seconds.
2. Auto-assignment to the next available attorney. If you're a multi-attorney firm, leads should round-robin across your intake team or route based on geography, case type, or current caseload. Don't let leads sit in a shared queue waiting for someone to claim them. That adds minutes. For more on this, read about lead routing rules and how they impact conversion.
3. First-attempt callback sequence. If the prospect doesn't answer the first call, your CRM should automatically trigger an SMS: "Hi Maria, this is [Firm Name]. We received your request for a free case review. We just tried calling. When's a good time to reach you?" Then schedule a second call attempt at 15 minutes and a third at 1 hour. Firms that automate 3-touch sequences within the first hour recover 20-30% of leads that didn't answer the initial call.
4. Duplicate detection. Check whether this prospect's phone number or email already exists in your CRM. If you're buying from multiple vendors, the same person may submit forms on different landing pages. Duplicate detection prevents embarrassing double-calls and keeps your data clean. Most CRMs support dedup rules; configure them to match on phone number as the primary key.
5. Compliance logging. Automatically store the TrustedForm certificate URL, the lead's IP address, and the timestamp of consent in your CRM record. If a TCPA claim surfaces 18 months later, you need this data accessible without digging through vendor emails. Treat compliance fields as immutable: once stored, they should never be edited or deleted.
For more on what should happen between the moment a lead arrives and the signed retainer, read what happens after you buy a lead. The webhook is just the starting line. The automations that fire after it are what separate firms that convert at 5% from firms that convert at 15%.
Frequently Asked Questions
What is a webhook for lead delivery?
A webhook is a server-to-server HTTP POST that pushes lead data to your CRM the instant a prospect submits their information. Unlike email or manual entry, webhooks deliver structured JSON data in under 5 seconds, letting your intake team respond before the prospect closes their browser tab.
Which legal CRMs support webhook integrations?
Clio, Filevine, MyCase, Litify, and PracticePanther all support inbound webhooks or API-based lead creation. Clio and Filevine offer native webhook endpoints. MyCase and Litify accept leads through their REST APIs. PracticePanther supports both Zapier-based and direct API integrations.
How fast is webhook delivery compared to email?
Webhook delivery typically completes in under 5 seconds end-to-end. Email delivery adds 2 to 10 minutes of latency depending on provider processing, spam filtering, and inbox polling intervals. Firms using webhooks contact leads 4x faster on average than those relying on email notifications.
Do I need a developer to set up a webhook?
It depends on your CRM. Clio Grow has a built-in webhook URL you can share with your vendor directly. Filevine requires a simple API token configuration. MyCase accepts leads through its REST API, which may need a developer for initial setup. Alternatively, middleware platforms like Zapier or Make can bridge your vendor and CRM without code.
What should I do if my webhook stops receiving leads?
First, check your CRM's webhook or API logs for error codes. A 401 usually means your API token expired. A 429 means you hit a rate limit. A 500 means your CRM had an internal error. Contact your vendor to confirm they are still sending to the correct URL. Set up uptime monitoring on your endpoint so you catch failures before they cost you leads.
Conclusion
Webhook delivery isn't a premium feature or a nice-to-have. It's the baseline for any firm that takes lead conversion seriously. The setup takes 5-30 minutes depending on your CRM, and the payoff is permanent: every lead you buy from that point forward arrives in your system within seconds instead of minutes.
Here's the summary. Webhooks deliver leads in under 5 seconds. Email adds 2-10 minutes. Manual CSV import can take hours. Firms using webhooks contact prospects 4x faster and convert at significantly higher rates because the 391% conversion advantage at 60 seconds (Velocify) only works if you actually reach the prospect within 60 seconds. The webhook makes that physically possible.
The five legal CRMs that handle most PI firms (Clio, Filevine, MyCase, Litify, PracticePanther) all support webhook or API-based lead intake. Configure field mapping, test with a request inspector, go live with monitoring, and wire up the five post-delivery automations: SMS alert, auto-assignment, callback sequence, duplicate detection, and compliance logging.
If you're still receiving leads by email, you're losing cases to firms that aren't. For a broader look at how delivery infrastructure impacts conversion across the entire lead lifecycle, read our guide on how real-time lead delivery works. For the economics behind why speed-to-contact matters this much, see our complete guide to buying MVA leads.
Ready to plug your CRM into a webhook-first delivery system? See how Claim Supply works, or keep reading with ping-post explained, lead routing rules, and API vs webhook vs email delivery.