At a glance
- Setting
- Form Settings › Action
- Method
- POST
- Code export
- Not needed
- Honeypot
- An Embed element
- Messages
- Webflow’s own
The integration
In the Designer, select the form, open the Settings panel, set Action to your endpoint URL and Method to POST. Add the honeypot as an Embed element inside the form. Webflow keeps rendering its own success and error messages on top.
<!--
Webflow: select your form → Settings panel → Action.
Set Action to the URL below and Method to POST.
Framer: use a Code Override or an embedded HTML form with the same action.
-->
https://mtform.co/f/your-form-key
<!--
Then add one hidden field so the spam trap works.
Add an Embed element inside the form containing exactly this:
-->
<input
type="text"
name="_mtf_honeypot"
tabindex="-1"
autocomplete="off"
aria-hidden="true"
style="position:absolute;left:-9999px"
>Step by step
- 1
Create the endpoint
Create a MakeTheForm form to get your public endpoint URL and inbox.
- 2
Set a custom form action
Select the form in the Webflow Designer, open the form Settings panel, and set Action to your endpoint URL with Method = POST.
- 3
Add the honeypot
Drop an Embed element inside the form containing the hidden _mtf_honeypot input, so the spam trap travels with the submission.
- 4
Publish and test
Verify your recipient email, publish the site, and submit the form to confirm it reaches your inbox and email.
Common pitfalls
The field names Webflow generates for you
Webflow uses each field’s Name (not its label) as the posted key, and auto-generates names like ‘field’ or ‘Email-2’. Set a clean Name on every field in settings so your submissions arrive with predictable keys.
Trusting Webflow’s success message as proof of delivery
Webflow shows its success state based on the HTTP response, not on whether email actually went out. Always send a real test and confirm it lands in your inbox: don’t rely on the green checkmark alone.
Troubleshooting
| Symptom | What’s happening | Fix |
|---|---|---|
| redirected to webflow.io | The Action was left blank, so Webflow posted to its own default handler. | Set Action explicitly to your endpoint URL and Method to POST in the form settings. |
| weird field keys | Fields kept their auto-generated Name values. | Rename each field’s Name in the settings panel; those become the JSON keys in your submission. |
| 403 | Allowed-domains is on and your published Webflow domain isn’t listed. | Add your webflow.io and custom domains in the form’s spam settings, or keep it public. |
Frequently asked questions
Can you change a Webflow form’s action to a custom URL?
Yes. Select the form, open the Settings panel, and set the Action field to any external endpoint with Method POST. Webflow then submits directly to that URL instead of its own handler, so you can route submissions anywhere.
Does Webflow email form submissions for free?
No. Email notifications require a paid Site plan and only send to Webflow’s configured address. Pointing the form action at a form endpoint gives you email delivery and a stored inbox independent of your Webflow plan.
Where does the honeypot go in a Webflow form?
Add it as an Embed element inside the form, containing a hidden input named exactly _mtf_honeypot. Embed elements let you insert raw HTML that Webflow’s visual fields can’t, which is where the spam-trap field lives.
Other platforms
Keep going
Last reviewed by the MakeTheForm team.