EZCRM + Custom Inbound Webhooks
Generic webhook capture from any system — build a custom lead source in minutes with our developer docs.
How it works
Set up once, then it just runs.
Generate a webhook endpoint
Create a unique inbound webhook URL for a new custom lead source directly inside EZCRM.
Point your system at it
Configure whatever system you’re integrating — a landing page tool, another CRM, an internal app — to POST to that URL.
Map fields and go live
Map the incoming JSON payload to EZCRM lead fields once, and every future submission follows the same mapping.
Why it matters
What this integration actually fixes.
Connect anything, not just listed integrations
If a lead source isn’t natively supported, a webhook usually gets it connected without waiting on a custom build.
Full field mapping control
Map any field in the incoming payload to any field in EZCRM, including custom fields.
Secure by design
Each webhook endpoint is unique and can be authenticated, so only your system can post to it.
No waiting on a native integration
Useful for internal tools, less common lead sources, or a system EZCRM doesn’t yet support out of the box.
Custom Inbound Webhooks integration, answered.
Do I need to write code to use this?
Basic setup (creating the endpoint, mapping fields) requires no code; sending the webhook itself requires whatever system you’re connecting to support outbound webhooks.
Is there developer documentation?
Yes — full webhook and field-mapping documentation is available for developers setting this up.
What authentication is supported?
Webhook endpoints support token-based authentication so only authorized systems can submit data.
Can I map custom fields, not just standard ones?
Yes, any custom field configured in your EZCRM account is available as a mapping target.
See the Custom Inbound Webhooks integration on your own pipeline.
30-minute demo, no slideware.