Furrow Forms

Hosts & site builders · works with Furrow Forms

Contact forms for sites on Netlify

Native forms exist here — Furrow is for control, portability, and agents.

paste this into your agent

Fetch furrowforms.com/ai and set up a contact form backend for my site on Netlify.

agent-readable recipe: /forms-for/netlify.md

prefer clicking? start in the dashboard

contact.html
<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 Netlify sites need a form backend

Netlify is the one host on this page with genuine native form handling: add an attribute to your markup and the build system wires it up, unmetered on current plans. If that covers your needs, use it — sincerely. Furrow Forms earns its place when you hit the feature’s edges: configuration changes require redeploys, there is no API or agent surface to create or manage forms, delivery to your systems lacks verifiable signing and retries, and the forms are welded to Netlify — leave the host, lose the forms. Furrow is dedicated form infrastructure that happens to work beautifully on Netlify too.

01

Config changes shouldn’t be deploys

Changing recipients or notifications with Netlify Forms means touching the site or dashboard settings per form. Furrow settings live at the project level and apply instantly — via dashboard, API, or agent.

02

No programmatic or agent surface

Netlify Forms cannot be created, configured, or verified over an API — an agent can only write markup and hope. Furrow’s entire control plane is REST + MCP, including webhook test calls.

03

Portability is insurance

Forms pointed at Furrow survive a move to Cloudflare, Vercel, or a VPS unchanged. Forms built on a host feature do not — migration means rebuilding form handling from scratch.

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 site on Netlify.
  1. 1.Registers the account over POST /api/register — you read one 6-digit email code
  2. 2.Provisions the site: client, project, and forms in one idempotent bootstrap_site call
  3. 3.Pastes the generated snippet into your codebase
  4. 4.Fires test_webhook and verifies the signed delivery

Or do it by hand

  1. 01Create a free account and a project for the site.
  2. 02Swap the netlify attribute for an action pointed at your Furrow endpoint.
  3. 03Configure domains, recipients, and webhooks once at the project level.
  4. 04Redeploy once — and never again for a form-settings change.

free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →

FAQ

Netlify + Furrow Forms, answered

Should I use Netlify Forms or a form backend?

If your site lives on a current Netlify plan and needs a basic contact form, Netlify Forms is a fine zero-config answer. Choose a dedicated backend like Furrow when you need API/agent management, signed webhooks with retries, instant config changes, or forms that survive a host migration.

What are the limits of Netlify Forms?

The main structural ones: forms exist only on Netlify-hosted sites, are created by build-time HTML parsing, cannot be managed via API or MCP, and settings changes ride the deploy cycle. Legacy (non-credit) plans also cap verified submissions per site. Our full comparison covers the details.

Can I migrate from Netlify Forms to Furrow later?

Yes, and it is mechanical: create the equivalent forms in Furrow (an agent can do this in one bootstrap_site call), change each form’s markup from the netlify attribute to an action URL, and redeploy. From then on, form changes never require another deploy.

The form backend your agent can run.

paste this into your agent

Fetch furrowforms.com/ai and set up forms for this site.

Setup for agents →