Help · Leads and lead capture
Inbound webhooks: send leads from any system
Point any system that can make an HTTP request at the inbound endpoint and its data becomes a lead — the general-purpose route for tools with no built-in integration.
Updated August 2026
Not every source of leads has an integration, and waiting for one is rarely the right answer. If a system can send an HTTP request, it can create leads.
This is also how you keep a website form you are happy with instead of rebuilding it.
Who this is for
Technical users, and anyone with an existing form or system producing leads.
Before you start
- A system that can make an HTTP request — most form builders and website platforms can.
- Permission to manage inbound sources.
- A test submission you can fire repeatedly while getting the mapping right.
Get the mapping right before you point real traffic at it
Inbound data arrives shaped however the sending system shapes it, and mapping is what turns those fields into lead fields. Mis-mapped inbound traffic produces leads that look fine and cannot be routed or scored. Test with real payloads first, not with what you assume the payload looks like.
Set it up
- Create the inbound source
This gives you the endpoint to send to. Each source is separate, so you can tell which system produced what. - Look at a real payload first
Send one from the actual system and look at what arrived. What a form builder sends is often not what its documentation implies. - Map the fields
Point each incoming field at the lead field it belongs in. Name plus email or phone is the minimum a lead requires. - Point your form or system at it
Keep your existing Webflow, WordPress or custom form and change where it posts. Nothing about the form itself has to be rebuilt. - Set up routing for these leads
Inbound leads need an owner like any other. Confirm routing covers them so they do not land unassigned. - Submit a real one end to end
Fill in the actual form on the actual site and follow it through to an owned lead. That is the only test that proves the whole path.
What you get
- Leads from systems with no built-in integration.
- Your existing website form kept rather than rebuilt.
- Source recorded so you know which system produced what.
- A tested path from real submission to owned lead.
Frequently asked questions
Do I have to rebuild my website form?
No. That is the point of this route — keep the form you have and change where it posts.
What fields does the payload need?
Enough to create a lead: a name, and at least one of email or phone. Beyond that, whatever you want to map and use.
Why are my inbound leads missing information?
Almost always mapping. The sending system's field names rarely match by accident — look at a real payload and map explicitly.
How do I know which system a lead came from?
Each inbound source is separate and the source is recorded on the lead, so attribution works the same as any other capture route.
Related articles
Connect your own form (web-to-lead)
Keep the form you already built in Webflow, WordPress, or plain HTML — point it at the KudosCRM inbound endpoint and we'll map common fields onto a new lead automatically.
Read articleOutbound webhooks
Have KudosCRM POST to your endpoint the instant something changes. Every payload is HMAC-signed so you can verify it is genuinely from us, and failed deliveries are retried with backoff.
Read articleRound-robin, territory and default-owner routing
The three ways a new lead gets an owner the moment it arrives, how priority ordering decides between them, and why the default owner is the rule that matters most.
Read articleHave an account issue this guide doesn't cover?
Start free today
Ready to give your team a CRM they'll actually use?
Start free. Bring your whole team. Cancel whenever (you won't).