Custom or in-house CRM
Some companies run their own system, a database a developer built, or a CRM we have not seen before. We can usually connect to it in one of two ways.
Option A: your system accepts a webhook
Section titled “Option A: your system accepts a webhook”If your system has a link that accepts a JSON POST (a “webhook”, “inbound endpoint”, or “lead post URL”), paste that link into your portal under Finish setup, then CRM connection, choose Other, and add a note with any field names your system expects if they differ from ours.
We send one POST per lead with this body:
{ "first_name": "Maria", "last_name": "Lopez", "phone": "+12485550143", "email": "maria.lopez@example.com", "address": "1427 Maple Ridge Dr", "city": "Flint", "state": "MI", "zip": "48503", "roof_need": "Full roof replacement", "property_type": "Single family", "roof_age": "15 to 20 years", "timeline": "Within 30 days", "priority": "Quality", "delivered_at": "2026-09-17 14:32", "lead_id": "VLN-2026-000431"}Your system should answer with any 2xx status. If it does not, we retry, and the lead still reaches you by email and text.
Option B: your system has an API key
Section titled “Option B: your system has an API key”If your system connects by key (like JobNimbus or HubSpot do), paste the key into the API key box with a note naming the system and, if you have it, a link to its API documentation. We map our fields to it and send the test lead.
Option C: it needs a login
Section titled “Option C: it needs a login”If the only way in is a username and password, do not paste those anywhere. Choose I do not have this handy, then use Book a call in your portal to schedule a 15-minute screen share with Sam, your customer success manager. He sets it up with you on the call.
Give your developer this
Section titled “Give your developer this”If a developer maintains your system, send them the lead fields page. It has every field name and a sample payload.