Submit buttons that go nowhere
Generated projects ship forms wired to nothing (or to console.log). A Furrow endpoint makes them real: stored, filtered, delivered.
AI site builders · works with Furrow Forms
Contact forms for Bolt sites
Prompt the frontend in Bolt, prompt the backend into Furrow.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for the site I’m building in Bolt.agent-readable recipe: /forms-for/bolt.md
prefer clicking? start in the dashboard
Make the contact form functional:
- POST the FormData to https://api.furrowforms.com/s/fp_k7m2
- add a hidden text input named "_gotcha" (honeypot, keep empty)
- add a hidden input named "_ft" set to Date.now() on page load (timing check)
- treat response JSON { ok: true } as success
- no backend code needed — the endpoint handles spam, storage, and emailThe gap
Why Bolt sites need a form backend
Bolt.new builds real projects — an in-browser environment where a prompt becomes a running app you can deploy. Its contact forms have the same gap as every generated frontend: no backend on the other side of submit. Furrow Forms closes the gap without changing the workflow. One instruction makes the form POST to your endpoint; better yet, the agent working in Bolt can read furrowforms.com/ai and provision the backend itself — account, forms, snippet, webhook verification — while it builds the site around it.
Keep the generated project dependency-light
No mail SDK, no ORM, no serverless function for the contact page. The form talks to Furrow directly from the browser; your Bolt project stays frontend.
An agent is already in the loop — use it
The same session that scaffolds your app can cold-start a Furrow account over API, bootstrap the site’s forms via MCP, and test the webhook — no tab-switching to a dashboard.
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 the site I’m building in Bolt.- 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 Furrow account and form — or let the agent in Bolt cold-start one from the prompt above.
- 02Apply the integration prompt so the form POSTs to your endpoint.
- 03Add the deployed domain to the allowlist and set notify emails on the project.
- 04Deploy from Bolt; the form is live, spam-filtered, and verifiable.
free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Bolt + Furrow Forms, answered
How do I hook up the contact form on a Bolt-built site?
Prompt Bolt to POST the form’s FormData to a Furrow Forms endpoint with a hidden _gotcha honeypot field. Furrow handles spam, storage, and notifications — the generated project needs no backend code.
Can the agent inside Bolt set up Furrow for me?
Yes. Furrow is built to be operated by agents: registration over API (you read one 6-digit email code), one-call site provisioning via bootstrap_site, snippet generation, and webhook testing. Point the agent at furrowforms.com/ai and it has the full instructions.
What happens to spam on a brand-new site?
It is filtered before it costs you anything: honeypot-caught and rejected posts are never stored and never count toward your quota. Add Turnstile keys and a domain allowlist at the project level for the full stack.
The form backend your agent can run.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.