Static export leaves the form handler behind
The SSG addon outputs flat files — and Statamic’s form processing is PHP that no longer runs. A Furrow-backed form is pure markup, so it survives the export untouched.
Platform CMS · works with Furrow Forms
Contact forms for Statamic sites
Native forms are great — until the site ships static or headless.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Statamic site.agent-readable recipe: /forms-for/statamic.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 Statamic sites need a form backend
Credit first: Statamic’s built-in Forms are genuinely good — tags in your Antlers templates, submissions in the control panel, email notifications built in. If Statamic serves every page, use them. The cases below are where that stops being true: sites exported to static hosting with the SSG addon, headless builds where a JS frontend consumes Statamic’s API, and agencies running Statamic next to Astro, Next, and Webflow who want one place submissions land. In all three, Furrow Forms keeps the form working when the PHP handler isn’t there.
Headless frontends can’t use Antlers form tags
When Next or Astro renders content from Statamic’s API, the {{ form }} tags never execute. Furrow gives the frontend a first-class endpoint instead of a workaround.
Mixed-stack rosters want one submissions plane
Statamic here, Astro there, a Webflow build for that one client — Furrow’s client → project → form hierarchy collects them all, with settings inherited per site and one API over everything.
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 Statamic 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.
- 02Replace the {{ form }} block with the plain-action form in your template.
- 03Configure domain, recipients, and thank-you URL once at the project level.
- 04Export or go headless freely — the form no longer depends on Statamic serving the request.
free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Statamic + Furrow Forms, answered
Do Statamic forms work with the SSG static export?
No — static export produces flat files, and Statamic’s form handling is server-side PHP that isn’t running anymore. Point the form at a Furrow Forms endpoint instead: the markup exports cleanly and the backend is always on.
Should I replace Statamic’s native forms with Furrow?
Not on a conventional Statamic deployment — the native Forms are excellent when PHP serves the page. Furrow is for static exports, headless frontends, and teams consolidating form handling across multiple sites and stacks.
Where do submissions go if not the control panel?
To Furrow: stored with configurable retention, emailed to your configured recipients, and optionally delivered anywhere by HMAC-signed webhooks with automatic retries — so you can even pipe them back into your own systems if you like.
The form backend your agent can run.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.