Leadnodes uses webhooks in four directions: receiving leads, forwarding leads, reporting complaints and registering users automatically. Which webhook is the right one depends on whether data is to flow into Leadnodes or out of Leadnodes.
Overview: which webhook for which task?
| You want to … | Direction | Guide |
|---|---|---|
| receive leads from your own source (form, landing page, partner) | incoming | Import leads into Leadnodes via webhook |
| test incoming leads first and map fields | incoming | Webhook import with test mode and mapping |
| receive leads from Heyflow | incoming | Heyflow incoming webhook |
| receive leads from Enpal.pro | incoming | Enpal.pro webhook integration |
| receive leads from WordPress forms (WPForms) | incoming | Connect WPForms with Leadnodes |
| send assigned leads to your CRM or a third-party system | outgoing | Set up the webhook integration |
| know which data is transmitted when forwarding | outgoing | Payload structure of the webhook export |
| report new and processed complaints to a third-party system | outgoing | Service webhooks for complaints |
| have buyer or supplier accounts created automatically | incoming | Registration webhook |
Receiving leads (incoming webhooks)
Every user in Leadnodes can receive leads via their own webhook URL. The URL contains the user's API token so that Leadnodes assigns the lead to the correct supplier:
https://app.leadnodes.com/hooks/lead/{User-API-Token}
The data arrives as JSON. The fields Leadnodes understands by default are listed in the standard lead parameters. You generate the API token in the user account under API tokens.
If you do not yet know the fields of a new source, use the test mode of the webhook import: Leadnodes accepts the data without importing it. You map the fields in the mapping and then switch to live operation.
For some sources there are dedicated guides with a ready-made URL and field mapping: Heyflow, Enpal.pro and WPForms.
Forwarding leads (outgoing webhooks)
With the webhook integration, Leadnodes automatically sends every lead to a URL of your choice after assignment, for example to a buyer's CRM. Several URLs can be created per user, each for all lead types or only for a specific one.
Leadnodes transmits the data as JSON via POST. The article on the payload structure shows exactly which fields are included.
Reporting complaints
In the system settings under Webhooks, you store two service webhooks: one reports newly created complaints, the other reports when a complaint has been processed. This keeps third-party systems up to date with the status of a complaint.
Registering users automatically
The registration webhook creates a buyer or supplier account as soon as an external system sends the sign-up data to your webhook URL. You activate it in the branding settings under “SignUp Routes”.
Without your own development?
If you cannot set up a webhook yourself, there are two alternatives: the Zapier integration connects Leadnodes with many other apps without any programming, and the import via email reads leads from formatted emails.