Connect the form your website already has to Make: webhook settings for Elementor, WPForms, Gravity Forms, Webflow and Contact Form 7
Short answer
Most website form builders can post each submission to a Make webhook: Elementor Pro has a Webhook action after submit, WPForms and Gravity Forms have webhooks add-ons on their Elite licences, Webflow has a form-submission webhook, and Contact Form 7 needs a third-party plugin. Send a test submission, check the field names Make received, then map them. The lead alert itself (sheet row and Telegram message) is the same whichever form you use.
Where the webhook setting is in Elementor Pro, WPForms, Gravity Forms, Webflow and Contact Form 7, what each sends, and how to test before the first lead.
Disclosure: links marked "paid link" pay us a commission from the vendor if you sign up. Your price is unchanged, and every file here works without them. How we choose tools →
Your site already has a contact form, and the client does not want a new one. The question is only whether that form can send each submission to a URL the moment it is submitted. If it can, it can feed the same lead alert as any other form: a row in Google Sheets and a Telegram message to whoever sells, within seconds.
This guide covers the part that differs between sites: where the webhook setting is in the common form builders, what each one sends, and how to test the connection before a real lead depends on it. The alert itself, and why answering in minutes matters, are covered in the free lead capture guide; we do not repeat the setup here.
The lead alert, from the startFree lead capture: form → Google Sheet → Telegram alert, with free blueprints and the exact fields
The blueprint this guide connects to
Lead comes in → logged → alert. No hands.
A form on the client site sends a lead; it is logged and an alert reaches Telegram in seconds. The first automation every consultant sets up.
Blueprint, steps and caveats → · Watch the tutorial on YouTube
Get all 27 blueprints in one ZIP, by email
Which website forms can send a webhook
Checked on each vendor's documentation on 29 September 2026. Licence names change; check the vendor's page before buying anything for this.
| Form builder | Webhook built in? | Where the setting is | What it sends |
|---|---|---|---|
| Elementor (Form widget) | Yes, in Elementor Pro | Form → Actions After Submit → Webhook | Field labels as names; all fields in one array with "Advanced Data" on |
| WPForms | Through the Webhooks addon, Elite licence | A Webhooks section in the form's settings, once the addon is active | JSON or form-encoded; you choose the fields and the method |
| Gravity Forms | Through the Webhooks Add-On, Elite licence | A Webhooks feed in the form's settings, once the add-on is active | JSON or form-encoded; all fields or selected ones |
| Webflow | Yes: a form_submission webhook | Site settings → webhooks, or the Webflow API | A POST with the submitted data, form details and metadata |
| Contact Form 7 | No | A third-party plugin, for example "CF7 to Webhook" | Depends on the plugin |
| No webhook at all | — | Replace or embed a form that has one | See the free form builders comparison |
Elementor Pro
Edit the form, open Actions After Submit, add Webhook, and paste the Make webhook address into the Webhook URL field. By default Elementor sends each field under its label, so "Phone number" arrives as a key with a space in it. Give each field a short custom ID and keep the labels stable; renaming a label renames the key Make receives.
WPForms and Gravity Forms
Both sell their webhooks add-on with the top licence, so check the site's licence before promising the client a date. Both let you choose JSON or form-encoded data and which fields to send. Choose JSON and send only the fields the sheet needs; Make then shows clean keys after the first test.
Webflow
Webflow can send every form submission to a webhook of type form_submission, and the API version can be limited to one form by name. Webflow's developer documentation notes that webhooks created in the dashboard do not include the headers needed to validate the request signature. If spam or forged requests matter, create the webhook through the API with a site token, or filter in Make.
Contact Form 7
Contact Form 7 has no webhook setting of its own. A plugin such as CF7 to Webhook adds one. That is one more plugin to keep updated; on a site that is rarely maintained, embedding a form that has webhooks built in is often the smaller risk.
Test before the first real lead
- Import the blueprint into Make and copy the address the webhook module shows.
- Paste it into the form's webhook setting and save.
- In Make, click "Run once", then submit the form on the live site with test data.
- Open the webhook module's output in Make and note the exact field names the form sent.
- Map those names in the Google Sheets and Telegram modules, run once more, and check the row and the message.
- Switch the scenario on, and delete the test row from the sheet.
If the form cannot send anything yet, you can check the Make side on its own: send one test request to the webhook address with a tool such as curl, then map the fields from that request and connect the form later.
The full build, step by step (6 minutes)
The video goes from an empty Make scenario to a working test: the sheet, importing the blueprint, the webhook, the Google Sheets module, creating a Telegram bot with BotFather, finding the chat ID, testing, and switching it on, plus the two things that do not work.
What goes wrong with website forms
A webhook does not check who is calling it. An open form attracts spam, and every spam submission becomes a row and an alert. Add a hidden field the form always fills and filter on it in Make before the sheet module.
The same person often fills the form twice. Without a check, sales calls them twice. The duplicate check below looks the phone number up in the sheet first and labels the second submission as a returning lead.
Returning lead → recognised → "second contact", not "new lead"
A returning lead is greeted as new. Before logging, the phone is checked against the log; if it is there, the alert says "came back", not "new lead".
Caching and security plugins can also get in the way. If the test submission never reaches Make, submit the form while logged out, check the plugin's log for a failed request, and look for a firewall rule that blocks outgoing requests from the site.
When the form arrives incomplete
Optional fields mean some leads arrive without a phone number. Instead of someone noticing and writing an email, the automation can list exactly what is missing and ask for it.
Form arrives incomplete → an email asking for exactly what is missing
A lead without a phone, an order without an address. Instead of someone chasing, one email lists the missing fields; the lead is logged as "incomplete".
If the site's form cannot send a webhook, the free form we build with has one built in, with hidden fields: Create a free form → paid link · we earn a commissionPaid link. If you ever upgrade to a paid plan through it we earn a commission from Tally; your price is the same, and the free plan covers every automation here.
Does the free version of Elementor send webhooks?
The Webhook action belongs to the Form widget, which Elementor documents as part of Elementor Pro (checked 2026-09-29). Without Pro, embed a form that has a webhook built in, or use a form plugin that does.
Why does Make show my fields with strange names?
The form sends each field under whatever name it uses internally: a label, a custom ID or a numbered key. Make only knows what the first test sent. Give fields short IDs in the form builder, send one test, and map from that.
Will changing the form break the automation?
It can, without an error. Renaming, removing or reordering a field can change what Make receives. Send a test submission after every form change and look at the sheet.
What does this cost to run in Make?
Three operations per lead, one for each module. The webhook uses nothing while no one submits the form. See the Make credits guide to compare that with your plan.
- Elementor Developers — Form actions (Webhook is a default action of the Pro form widget)
- WPForms — How to install and use the Webhooks addon (Elite licence; JSON or FORM)
- Gravity Forms — Webhooks (Elite licence add-on; JSON or FORM)
- Webflow Developers — Working with webhooks (form_submission; dashboard webhooks and signatures)
- WordPress.org — CF7 to Webhook plugin
Related guides
Next step
All automations →
FREE LEAD ALERTTally form → lead log → Telegram alert. The free version of the lead alert
No website form, no CRM, no paid tool. A free Tally form posts to Make; the lead lands in Google Sheets and Telegram pings sales in seconds.
AUTO WELCOMENew client → welcome email → onboarding checklist → alert
A client signs and hears nothing until someone is free. On signing, they get an email saying what comes next, a checklist opens and the team is alerted.
SOURCE REPORTEvery Sunday: leads by source → one message with the change from last week
Which source brings the leads? Every Sunday one Telegram message lists this week's leads per source (website, Facebook, referral) beside last week's.
Get one new Make automation each week
Get the full 27-blueprint pack (ZIP) by email, then one new automation a week. Every build on the site stays open and free without it.