Integrate Webhook - Classic with LeadsBridge
Intro
The Webhook is a way to send or receive each collected lead from your Source or Destination to a specific URL, passing GET/POST parameters.
In this article, you'll learn how to connect your LeadsBridge account with Webhook - Classic.
Connect Webhook - Classic integration
Before you start
- Head over to the left sidebar and click on the Create new Bridge button
- Select your integrations in the selectors
- Click on the Continue button at the bottom right
Authorize Webhook - Classic integration
Setup your Webhook - Classic integration
- Click on Connect Webhook - Classic
- Click on Create new integration to connect your Webhook - Classic (or select an existing one from the dropdown if you already connected it)
- A popup wil be opened where you can authorize the Webhook - Classic integration
- Fill URL, Access Secret field to connect Webhook - Classic with LeadsBridge
- Click on the Authorize button
- You can choose a name for this Webhook - Classic and LeadsBridge integration (you can also edit it later)
- Once done, click on Continue button and you will get back to the bridge experience where you could choose additional integration settings
- Now that your Webhook - Classic is connected, you can continue with the set-up of your bridge
Configuration details for Webhook - Classic
How to get URL, Access Secret
In order to correctly recognize incoming data when the Webhook Integration is used as Source you should do the following:
1. Go into the Source step of your Incoming Webhook Bridge
2. If the Bridge says Waiting for New Lead… means that is on Listening Mode and that any data you submit to the Webhook URL will be read by the LeadsBridge as soon as it arrives into the system
![]()
3. You should leave this page open and submit data from the Source in which you have assigned the Webhook URL provided by LeadsBridge. In case you need to close the page and go back later to the Bridge configuration, make sure to set the Bridge on Listening Mode by clicking on the Recognize Other Fields button
![]()
4. Once you’re able to submit data from your Source it should get automatically recognized by LeadsBridge
![]()
5. In case you forgot to add some data, you should set the Bridge on Listening Mode by clicking on the Recognize Other Fields button and submit new data from your Source
![]()
6. In case data is not being correctly recognized you may reach our support with the Missing or wrong fields? Ask for help! button
![]()
7. Once all the data you want to map from your Source has been correctly recognized you should continue with your Bridge configuration by clicking on Next
![]()
In case you need to map new fields from your Source you should open your Bridge and follow the guidelines from step 5.
1. Go into the Source step of your Incoming Webhook Bridge
2. If the Bridge says Waiting for New Lead… means that is on Listening Mode and that any data you submit to the Webhook URL will be read by the LeadsBridge as soon as it arrives into the system
3. You should leave this page open and submit data from the Source in which you have assigned the Webhook URL provided by LeadsBridge. In case you need to close the page and go back later to the Bridge configuration, make sure to set the Bridge on Listening Mode by clicking on the Recognize Other Fields button
4. Once you’re able to submit data from your Source it should get automatically recognized by LeadsBridge
5. In case you forgot to add some data, you should set the Bridge on Listening Mode by clicking on the Recognize Other Fields button and submit new data from your Source
6. In case data is not being correctly recognized you may reach our support with the Missing or wrong fields? Ask for help! button
7. Once all the data you want to map from your Source has been correctly recognized you should continue with your Bridge configuration by clicking on Next
In case you need to map new fields from your Source you should open your Bridge and follow the guidelines from step 5.
Which entity concepts we support for Webhook - Classic
With LeadsBridge you may use these entity concepts for Webhook - Classic.
Lead
A person that actively shows interest in your offering.
Common questions for Webhook - Classic
Which kind of content type is accepted by Webhooks?
Currently, the content types accepted by Webhooks in LeadsBridge are JSON and FormData.
How is Webhook data sent when used as Destination?
Webhook data is sent using an HTTP request to the configured end point URL, the data sent will use the GET or POST method depending on the integration's configuration, as shown in the screenshot below.
The data will be sent exactly as received from the source of the Bridge, so if for example we receive the data from the source with the following format:
{"first_name": "John", "last_name": "Doe", "email": "john.doe@leadsbridge.com"}
We will send it to the Destination, using the GET or POST method, with the exact same format.
Is it possible to use the same Incoming Webhook URL for multiple Bridges?
At the moment our Incoming Webhooks are 1-1 with the Bridges and it is not possible to use the same Webhook URL for more than one Bridge.
Why the leads do not arrive at the Destination?
Notice that the Outbound Webhook integration is very technical and versatile, LeadsBridge system simply takes the data that comes from the Source and sends it to the specified URL.
If the lead doesn’t arrive at the Destination, make sure to double-check the Success and Failure patterns, they must be set according to the destination requirements.
Some Success and Failure Pattern examples could be:
- Ok
- Error
How can I use the Access Secret field?
When the Webhook Integration is used as Destination it's possible to specify an Access Secret.
It will be used as a password to maintain secure access with the Destination and avoid other pages calling the same page with data that doesn’t originate from your specific Source.
Do you need help?
Here some additional resources:
- LeadsBridge KNOWLEDGE BASE
- Contact support from your account clicking on the top right Support button