Connect your own systems with webhooks.
Two building blocks cover most custom connections. A lead endpoint takes leads from any form, app or server with a token. An HTTP request step sends DueDoor events to any URL you choose, from any automation, with the body you write.
What moves between your own systems and DueDoor
Here is exactly what each side accepts and sends today.
| What | Direction | How it works |
|---|---|---|
| Leads | Into DueDoor | POST JSON or form data with a form token: name, and a phone or email. Optional: message, company, source page. |
| Click and campaign data | Into DueDoor | gclid, gbraid, wbraid, fbclid and UTM tags are saved, and the lead is marked as paid where they apply. |
| Checks on arrival | Into DueDoor | Phone numbers are checked against your country, and tokens can be locked to your website's origins. |
| Events from DueDoor | From DueDoor | An HTTP request step calls your URL with the method, headers and body you set. |
| Placeholders | From DueDoor | The body can use lead and trigger fields, such as the name, phone, stage, source or message text. |
| Errors | From DueDoor | A call that times out or returns an error fails the step, and it shows in the run history. |
What a call looks like
Your form or server posts the lead. DueDoor answers with the new lead's ID and your flows begin.
- Each form or site can have its own token, and a token can be turned off without touching the others.
- The source page you send becomes a tag, so flows and reports can tell forms apart.
- Leads created through the endpoint fire the same "New lead" automations as any other lead.
- Outgoing calls can go to your ERP, a sheet tool, Zapier, Make, n8n or a chat app's webhook.
- Need something the endpoint does not do? We build and host custom endpoints as part of our work.
How to connect your own systems
We set it up with you and test it end to end before it runs on real leads.
- 01
Get a token
We create a form token for your workspace, optionally locked to your website's domains.
- 02
Post a test lead
Send name and phone with the token from your form or server and check the response.
- 03
Check the lead
The lead appears in the pipeline with the source page as a tag.
- 04
Add outgoing webhooks
In an automation, pick a trigger and add an HTTP request step to your URL.
- 05
Watch the runs
Run history shows each call and any error, so issues are found fast.
What it does not do
We would rather you know the edges before you start. These are the honest limits today.
There is no general REST API for reading or editing all DueDoor data today. The lead endpoint creates leads; the HTTP request step sends events out.
Tokens locked to website origins will refuse server calls that send no origin; use a separate token for servers.
Outgoing calls wait about 15 seconds before they give up, so your URL should answer quickly.
For two-way sync with a specific system, we design and build the connector with you.
How businesses use webhooks with DueDoor
A few examples by industry. Each links to what DueDoor does for that kind of business.
Software development agencies
Send leads from client apps into DueDoor and push won deals to your project tool.
SaaS companies
Post trial sign-ups from your product and alert your team chat when a lead qualifies.
Manufacturing units
Send confirmed dealer orders from DueDoor to your ERP's webhook.
Hospitals
Bring enquiries from a booking site into DueDoor with the department as the source page.
Universities and colleges
Post application forms into DueDoor and send enrolled students to your student system.
Freight and logistics
Accept quote requests from your website and send booked jobs to your operations system.
See every industry we work with on the industries page.
Questions about the Webhooks and API integration
Does DueDoor have a public REST API?
Not a general one today. There is a lead endpoint that creates leads from any form or server with a token, and automations can send events to any URL with an HTTP request step. For more, we build custom endpoints.
What fields does the lead endpoint accept?
A token and a name are required, with a phone or an email. Optional fields include message, company, source page, Google and Meta click IDs and UTM tags. JSON and form data both work.
How is the endpoint protected?
Each form has its own token, which can be turned off. A token can also be locked to your website's origins, so other sites cannot post with it. Phone numbers are checked on arrival.
What can trigger an outgoing webhook?
Any automation trigger, such as a new lead, a stage change, an inbound message, a call outcome, a finished AI call or a booked meeting, with conditions if you need them.
What happens if our server is down?
The HTTP request step fails for that run and the error shows in the run history, so you can see it and run it again.
Can you build a two-way sync with our system?
Yes, as a build project. We design the endpoints, the mapping and the error handling, and we host and run them with your DueDoor workspace.
Connect your systems to DueDoor
Book a call or message us on WhatsApp. We will look at what you use today and tell you plainly how the connection would work. You can also write to support@duedoor.com.