Every trigger field, POSTed as JSON to a URL you control, the moment a lead is captured. No middle app required beyond Zapier itself running the trigger.
Field reference
| Lead Recorder field | JSON key | Notes |
|---|---|---|
| id | id | string |
| submittedAt | submittedAt | ISO 8601 timestamp |
| status | status | string |
| type | type | "form" | "phone" | "email" | "booking" |
| formPage | formPage | path |
| nameField | nameField | one combined string |
| emailField | emailField | null when absent |
| phoneNumber | phoneNumber | null when absent |
| utmSource | utmSource | |
| utmMedium | utmMedium | |
| utmCampaign | utmCampaign | |
| utmTerm | utmTerm | |
| referrer | referrer | |
| landingPage | landingPage | |
| device | device | |
| city | city | |
| country | country | |
| region | region | |
| gclid | gclid | |
| gbraid | gbraid | |
| fbclid | fbclid |
The raw payload
{
"id": "lead_8f3a2c",
"submittedAt": "2026-08-08T22:14:03Z",
"status": "new",
"type": "phone",
"formPage": "/emergency-plumber",
"nameField": null,
"emailField": null,
"phoneNumber": "+61412345678",
"utmSource": "google",
"utmMedium": "cpc",
"utmCampaign": "emergency-plumbing-sydney",
"utmTerm": "emergency plumber near me",
"referrer": "https://www.google.com/",
"landingPage": "/emergency-plumber",
"device": "mobile",
"city": "Parramatta",
"country": "AU",
"region": "NSW",
"gclid": "Cj0KCQjw...",
"gbraid": null,
"fbclid": null
}A real phone-click lead: no name, no email, real UTM and geo data attached.
Setting it up
Open the Zap template
Trigger: Lead Recorder, new lead. Action: Webhooks by Zapier, POST.
Point it at your endpoint
Enter your URL. Add custom headers if your endpoint needs auth, an API key, a shared secret, whatever you've built it to expect.
Send a test lead
Submit a form or click-to-call on your own site and check your endpoint's logs for the raw payload below.
Retry behaviour
What happens when your endpoint is down
Zapier retries a failed delivery automatically a limited number of times before marking the task as an error in your Zap history. It doesn't queue indefinitely. If your endpoint is down for an extended stretch, check the Zap's task history and replay the failed tasks manually rather than assuming everything caught up on its own.
Stop building a scraper.
Start recording.
Your next lead is about to hit your website. Get the full payload, structured, the moment it happens.
No credit card required · Included on every plan
Found you via Google Ads · "best plumber near me"
Found you via Organic Search · "emergency electrician"
Found you via Facebook Ads