Forwarding leads with a webhook
Send every new enquiry to your CRM, Zapier or Make automatically, with the visitor's source. The lead also stays in your dashboard.
On this page4
What you need
- A webhook address from your CRM, Zapier or Make. It starts with https://
- Owner rights in meetpiloot
With a webhook, meetpiloot forwards every new lead straight away to an address you choose. The message contains the customer's details, the quoted price and the visitor's source: the UTM parameters, the click IDs from Google, Microsoft, Meta and TikTok, the landing page and the referrer. Your web developer or agency connects it to Zapier, Make or their own system, and from there to any CRM.
Setting up the webhook
Open Integrations and choose Forward leads.
You will find it in your dashboard under SettingsIntegrationsForward leads.
Paste the webhook address.
Zapier, Make and most CRM packages give you an address that starts with https://. In Zapier, choose "Webhooks by Zapier" as the trigger and then "Catch Raw Hook". Paste the address into the Webhook address field.
Fill in your website addresses.
These are the domains the configurator is embedded on. They tell us the source data really comes from your site. You can leave this empty.
Generate the signing secret and give it to your web developer.
meetpiloot creates the secret for you. You only see it once, so copy it straight away. The receiving system uses it to check that a message really comes from meetpiloot.
Send a test message and switch the connection on.
Click Send test message. If that works, switch on Connection active. From then on, every new lead is sent automatically.
How the source is recorded
The source is recorded on the first visit and stays for the whole session. A later page without parameters does not overwrite a campaign that was measured earlier. If the configurator sits on your site as an iframe, the tracking script reads the parameters from your page's address. With a direct link, the configurator reads them from its own address.
Check that it works
Under Recent messages you can see the twenty most recent deliveries, with their status, error message and number of attempts. A test message is a complete sample lead with a real signature, sent along exactly the same path as a real lead. If the test message arrives, the connection works.
Then send a real test enquiry through your configurator. Within a few seconds it shows up in your CRM or in your Zap's history.
When a delivery fails
If the receiving system does not respond, or responds with an error on its side, meetpiloot tries again automatically. The details are in delivery and retries. The lead always stays in your dashboard, even if delivery fails.
For developersPayload, signature and sample code for Node.js
The message fields are described in payload and fields. How to check the signature is explained in verifying the signature.
Read next
Stuck?
Email us or open a ticket from your dashboard. We reply within 1 to 2 working days.