How to send website leads to a CRM via webhook
A webhook is an address a website form sends request data to instantly. Make receives the webhook, checks the fields, adds UTM tags and creates the lead in your CRM within seconds. This works for Tilda, WordPress and most page builders, into one CRM or several at once.
At an online academy, requests from Tilda and WordPress sites ended up in different places, and some were entered into the CRM by hand. Some leads were lost before the first call.
Now the form sends each request to a Make webhook, and within seconds the lead appears in two CRMs at once, in the right course. That's how 4,726 website leads reached the CRM automatically.
A website request shouldn't wait in an inbox
Many sites still send requests by email or to a Telegram chat, and someone moves them to the CRM by hand. Some get lost, some arrive without a source. A webhook removes that manual step.
You need this if…
- Website requests arrive by email or in a chat
- Someone moves them to the CRM by hand
- Lead cards have no source or UTM tags
- You have several websites or landing pages
What webhook delivery affects
- Speed. The lead is in the CRM seconds after the form is sent.
- Source for every lead. UTM tags and the page are written to the card automatically.
- One source of truth. Leads from all sites land in one CRM, not in different inboxes.
- Flexibility. Make can route the lead to pipelines, alert the team and log it in a sheet.
Pitfalls
- Tags don't arrive. A form doesn't pass UTM unless you add them as hidden fields.
- Test requests. Form tests land in the CRM as real leads. Add a filter or a test flag.
- Site changes. Someone renames a form field, and the scenario starts creating empty cards. Check required fields and set up error alerts.
- Spam. Bots fill in forms. Without a captcha or filter the CRM gets cluttered.
- Duplicates. A person submits twice. Search for the contact by phone or email before creating a deal.
The path of one request
Solution options
Requests by emailsimple but unreliable
Someone moves requests to the CRM by hand. Slow, leaky and without a source.
Page builder's CRM integrationfast but limited
Tilda and others have ready integrations with some CRMs, but routing, duplicates and multiple CRMs are hard to set up.
Webhook + Makemost flexible
The form sends data to Make, the scenario normalises fields, checks duplicates, records UTM and creates the lead in one or several CRMs.
Website leads reach the CRM instantly
For an online academy I set up leads from Tilda and WordPress sites to flow via webhook and Make into two CRMs at once. Together with Facebook forms and TikTok that's 17,124 leads without a single manual export.
Read the full case study →FAQ
What is a webhook in simple terms?
An address one service automatically sends data to when something happens. For example, a website form sends a request to a Make webhook as soon as the button is pressed.
How do I connect a Tilda form to a CRM via Make?
Create a Make scenario with a Webhook module, add its address to the Tilda form settings as a webhook, and the scenario writes the data to the CRM.
How do I pass UTM tags from the site to the CRM?
Add hidden fields to the form that are filled with UTM from the page URL, and send them to the CRM with the request.
Can a request go to two CRMs at once?
Yes, a Make scenario can create the lead in several systems at the same time.
What if the webhook stops working?
Set up error alerts in Make and check the execution log. The usual cause is changed form fields.
Want website requests to never get lost?
Describe your funnel and the result you want. I'll tell you how to build it with the tools you already use.
Discuss your task