Exported sites lose their forms
Webflow’s code export famously ships forms that no longer submit — handling lives on Webflow’s servers. A Furrow action URL survives export unchanged, because the backend was never Webflow’s.
Hosts & site builders · works with Furrow Forms
A form backend for Webflow sites
Native forms end at Webflow’s walls; Furrow works inside and outside them.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Webflow site.agent-readable recipe: /forms-for/webflow.md
prefer clicking? start in the dashboard
<form action="https://api.furrowforms.com/s/fp_k7m2" method="POST">
<input type="text" name="_gotcha" style="display:none" tabindex="-1" />
<input type="hidden" name="_ft" value="" />
<script>document.currentScript.previousElementSibling.value = Date.now();</script>
<input name="name" type="text" required />
<input name="email" type="email" required />
<textarea name="message" required></textarea>
<button>Send</button>
</form>The gap
Why Webflow sites need a form backend
Webflow forms work well inside Webflow’s world: designer-built, submissions in the dashboard, notifications on. The friction appears at the boundaries — form submissions are metered by your site plan, routing beyond email means third-party glue, and the moment you export code, form handling stays behind: exported forms simply don’t submit. Furrow Forms works on both sides of that boundary. Point a Webflow form’s action at a Furrow endpoint (a form setting, no custom code) or drop a form in an Embed element, and the same backend serves the hosted site, the exported site, and every other property you run.
Submission limits ride your site plan
Native form volume is coupled to what you pay Webflow for hosting. Furrow decouples it: form volume is Furrow’s flat pricing, hosting is Webflow’s business.
Routing beyond the inbox
CRM, Slack pipeline, data warehouse — Furrow delivers every submission as an HMAC-signed webhook with retries and a log, to any endpoint you choose.
Two ways in
Set it up yourself, or don’t
Hand it to your agent
[ recommended ]Furrow’s whole control plane is an API and MCP server. Paste this prompt into Claude Code, Cursor, or any agent — it does the rest:
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Webflow site.- 1.Registers the account over POST /api/register — you read one 6-digit email code
- 2.Provisions the site: client, project, and forms in one idempotent bootstrap_site call
- 3.Pastes the generated snippet into your codebase
- 4.Fires test_webhook and verifies the signed delivery
Or do it by hand
- 01Create a free account and a project for the site.
- 02In the Designer, set the form’s Action to your endpoint and Method to POST (or use an Embed element).
- 03Add your webflow.io and custom domains to the allowlist; set recipients and webhooks once.
- 04Publish — and if you ever export the code, the form keeps working.
free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Webflow + Furrow Forms, answered
Can I use my own form backend with Webflow?
Yes — Webflow lets you set a custom Action URL on any form in the Designer’s form settings. Point it at a Furrow Forms endpoint with Method POST, and submissions flow to Furrow: spam filtered, stored, emailed, and webhooked.
Why don’t forms work after exporting code from Webflow?
Because Webflow’s form handling runs on Webflow’s hosting — exported sites keep the markup but lose the backend. Forms pointed at Furrow are backend-independent, so the exported site submits exactly like the hosted one.
Do Webflow’s form notifications and dashboard still apply?
No — with a custom action, submissions bypass Webflow entirely and land in Furrow, which takes over storage, notification email, and webhooks. That is the trade: you leave Webflow’s form dashboard and gain an API-manageable backend with signed delivery.
The form backend your agent can run.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.