Zapier Webhook Setup
4 min read
Send Made For Law lead events to Zapier with Webhooks by Zapier and a Catch Hook URL.
Overview
Made For Law sends new calculator leads to Zapier using a webhook. In Zapier, the trigger app is Webhooks by Zapier and the trigger event is Catch Hook. After Zapier catches the sample lead, you map those fields into your CRM, spreadsheet, inbox, or team chat tool.
Do not search for "Made For Law" as the trigger app in Zapier. Use Webhooks by Zapier -> Catch Hook unless your firm has been given a separate private Zapier app invite.
Prerequisites
- A Made For Law account with lead routing access
- A Zapier account
- Access to the destination app you want to update, such as Google Sheets, Slack, HubSpot, Salesforce, or Clio
Fastest proof: Google Sheets
If this is your first Zap, start with Google Sheets. It is the fastest way to prove that Zapier caught the MFL test lead and that your field mapping works.
Setup
Create a Zapier Catch Hook
- In Zapier, click Create Zap.
- For the trigger app, choose Webhooks by Zapier.
- For the trigger event, choose Catch Hook.
- Continue to the trigger test step.
- Copy the webhook URL Zapier gives you.
Paste the URL in Made For Law
- Log in to your portal at portal.madeforlaw.com.
- Navigate to Settings > Integrations > Lead Routing.
- Select Zapier.
- Paste the Zapier webhook URL.
- Save the integration.
Send a test lead
- In Made For Law, click Send test lead.
- Return to Zapier's trigger test screen.
- Confirm Zapier caught a
lead.createdsample payload.
Add your destination action
- In Zapier, add an action step.
- Choose your destination app, such as Google Sheets, Slack, HubSpot, or Salesforce.
- Choose the action, such as Create Spreadsheet Row, Send Channel Message, Create Contact, or Create Lead.
- Connect the destination account.
Map fields
Use Zapier's field picker to map Made For Law lead fields into your destination app. Required fields vary by destination, so check the required-field labels in Zapier before publishing.
Publish
- Test the destination action.
- Confirm the row, message, contact, or lead appeared in the destination app.
- Click Publish to turn on the Zap.
Field reference
The exact payload can change as MFL adds fields, but the standard lead test uses this shape:
| Field | Type | Meaning |
|---|---|---|
event |
string | Event name, usually lead.created |
tenant.id |
string | Your MFL tenant/account identifier |
tenant.name |
string | Firm name |
lead.id |
string | MFL lead identifier |
lead.created_at |
datetime | Lead creation time |
lead.first_name |
string | Prospect first name |
lead.last_name |
string | Prospect last name |
lead.email |
string | Prospect email |
lead.phone |
string | Prospect phone |
lead.state |
string | State or jurisdiction selected |
lead.calculator |
string | Calculator used, such as probate |
estimate.total |
number | Estimate total, when available |
estimate.currency |
string | Estimate currency, usually USD |
source.page_url |
string | Page where the lead started |
source.utm_source |
string | UTM source, if present |
pdf.url |
string | Estimate PDF URL, if generated |
Troubleshooting
Zapier did not catch the test lead
- Confirm the trigger app is Webhooks by Zapier.
- Confirm the trigger event is Catch Hook.
- Copy the current hook URL from Zapier's trigger test step and paste it again in Made For Law.
- Send another test lead from Made For Law.
Zapier caught the lead, but the destination app did not update
- Check Zapier's Zap History for the action step error.
- Confirm required destination fields are mapped.
- Confirm the connected destination account has permission to create the record, row, or message.
Required CRM fields are missing
- Use a Zapier Formatter step to split
lead.nameinto first and last name if your CRM requires separate fields. - Create custom fields in the CRM before mapping probate-specific details.
- For Salesforce, set a static Company value if your Lead layout requires one.
Hook URL changed
Zapier Catch Hook URLs can change if the Zap is rebuilt, transferred, or duplicated. Copy the new URL from Zapier and update Made For Law.
Support boundary
Made For Law can confirm whether the webhook was sent and what HTTP response it received. Zapier's Zap History shows whether Zapier processed the trigger and action steps. Destination app support handles destination-specific permissions, required fields, and object setup.