Send Zapier leads into SnapCoat
Marketing agencies can connect form fills, ad leads, booking pages, and landing pages with one webhook URL. SnapCoat accepts common field labels, so setup does not require perfect developer-style mapping.
Secure URL
Each company has a private token in its webhook URL. No companyId is needed.
Creates leads
Successful submissions create a New Lead in the sales pipeline.
Only 2 things required
Send a lead name plus either phone or email. Source and notes are strongly recommended.
Quick Setup
Copy your SnapCoat webhook URL
Log into SnapCoat, click Connect to Zapier in the header, open Lead Creation, then copy the webhook URL.
Create a Zap
Choose the app that starts the automation, like Facebook Lead Ads, Google Forms, Typeform, or another form tool.
Add Webhooks by Zapier
Add an action step, choose Webhooks by Zapier, then choose POST.
Paste the URL and send JSON
Paste your SnapCoat webhook URL, set Payload Type to JSON, then map Full Name and either Phone or Email.
Test and turn it on
Run Zapier's test. A successful test creates a new lead in the New Lead pipeline stage.
Zapier Action Settings
Fields To Map
Required
Full NameSimplest option. SnapCoat automatically splits this into first and last name.
Phone or EmailOnly one is required. Send both when available for cleaner follow-up.
Recommended Optional Fields
sourceWhere the lead came from, such as Google LSA, Facebook Ads, Website, or Angi.
notesProject type, customer request, or form notes.
addressStreet address. Include city, state, and zip when available.
cityCity for the job/customer address.
stateState abbreviation or full state name.
zipZIP/postal code.
estimatedValueOptional estimated project value.
tagsOptional list of tags for filtering or automation.
source whenever possible. It keeps lead attribution clean for ads, website forms, referrals, and campaign reporting.Accepted Field Labels
Zapier fields can be named naturally. SnapCoat normalizes common labels from ad platforms, forms, and landing page tools.
Example JSON Payload
{
"Full Name": "Jane Smith",
"phone": "(555) 123-4567",
"source": "Facebook Lead Ads",
"notes": "Exterior repaint estimate",
"address": "123 Main Street",
"city": "Austin",
"state": "TX",
"zip": "78701"
}What Happens After A Successful Test
A new lead is created in the New Lead pipeline stage.
Phone numbers are normalized when possible.
Source is saved for attribution. If omitted, SnapCoat uses Zapier Integration.
If address fields are included, SnapCoat can create the related customer/address record.
Response Codes
Lead created
The webhook worked and the lead was added to SnapCoat.
Missing required fields
Send a lead name plus either email or phone. Full Name is enough for the name.
Invalid webhook URL
The token in the URL is wrong, expired, or was regenerated. Copy the URL again from SnapCoat.
Duplicate blocked
The same name, email, and phone were submitted again within the duplicate-prevention window.
Server error
SnapCoat could not process the request. Retry once, then contact support if it continues.
Security Notes
Do
- +Keep the webhook URL private.
- +Store it only inside Zapier.
- +Regenerate the token if it was exposed.
- +Use the webhook activity/status tab to monitor usage.
Do Not
- -Post the webhook URL publicly.
- -Share screenshots that show the full token.
- -Commit the URL into code or docs.
- -Reuse another company webhook URL.
Troubleshooting
Zapier says required fields are missing
Map Full Name and either Phone or Email. If your trigger app separates names, firstName and lastName still work.
Invalid webhook token
Copy the full webhook URL from SnapCoat again and replace the whole URL in Zapier. Do not edit the token by hand.
Lead is not showing in the pipeline
Check Zapier Task History for the HTTP response. If it returned 201, search the pipeline by name or email and clear filters.
Duplicate lead error
SnapCoat blocks accidental double-submissions for a short window. Check whether the first lead already created successfully.
Need help?
Include the Zapier Task History response code and request ID when contacting support. If sharing a token, send only the first 10 characters.