Skip to content
Wrenform

Contact forms / Webflow

Webflow form submissions by email

Set two fields on your Webflow Form Block. Submissions then come to Wrenform instead of Webflow.

Why Webflow needs a form backend

Webflow handles forms itself, with submission limits that depend on the site plan. Agencies often want submissions in one place across many client sites, sent to several recipients, or forwarded to their own systems.

A Form Block can post to any URL. Set its action to your Wrenform endpoint and its method to POST. Webflow then stops storing those submissions; we store them, filter spam and email the recipients you choose.

This suits agencies most. Each client site gets its own Wrenform form, with its own recipients, allowed origins and retention, all in one account. Submissions keep arriving if the client changes Webflow plans, and you can export them to CSV at any time.

The snippet

Replace YOUR_FORM_ID with the ID of your form.

Webflow: point the Form Block at your endpoint

1. Select the Form Block and open its settings.
2. Action:  https://wrenform.com/f/YOUR_FORM_ID
3. Method:  POST
4. Name each field (name, email, message).
   A field called "email" becomes the reply-to address.

With a custom action, Webflow hands the submission to us
instead of storing it itself. Publish, then send a test.

Steps

  1. Create a form (free) and copy its endpoint.
  2. Select the Form Block and open Settings. Set Action to the endpoint and Method to POST.
  3. Name each field, and add the _honey field in an Embed element inside the form.
  4. Publish, then add your webflow.io address and custom domain to Allowed origins.

Spam handling

Spam filtering is on for every form, with no CAPTCHA: a hidden honeypot field, a timing check, rate limits per visitor, and a content score for links, keywords and gibberish. Spam goes to a separate tab and is never emailed. See how spam filtering works.

Webflow's own success and error messages don't show with a custom action. Visitors land on our thank-you page, or on your own page if you set Redirect to.

Deployment notes

  • Webflow staging. Test on your webflow.io address. The Designer preview doesn't submit forms. Add the staging address to Allowed origins while you test.
  • Custom domain. Add your custom domain to Allowed origins before you publish to it. Keep the staging address only if you still test there.

FAQ

Does Webflow still store submissions with a custom action?
No. With a custom action the browser posts to Wrenform, so Webflow doesn't receive the submission or send its own notification.
Can I keep Webflow's success message?
Not with a standard post. Use Redirect to for your own thank-you page, or embed a form that submits with JavaScript.
How do I add the honeypot field?
Drop an Embed element inside the Form Block and paste the hidden _honey input.
Can one account handle many client sites?
Yes. Each site gets its own form, with its own recipients, allowed origins and retention.
Do I need Webflow's reCAPTCHA?
No. Spam filtering runs on our side. If reCAPTCHA stays on, its token arrives as an extra field, g-recaptcha-response, in your submissions.

Next steps