Headless CMS · works with Furrow Forms
Skip the public create-permission recipe — your CMS stays read-only.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Strapi site.agent-readable recipe: /forms-for/strapi.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
The standard Strapi contact-form tutorial goes: create a "submission" content-type, grant the public role create permission, configure the email plugin, and hope the spam stays manageable. That recipe turns your CMS — the thing running your content — into an unauthenticated write target. Furrow Forms replaces the whole chain with one POST endpoint: submissions stored elsewhere, spam filtered before it counts, notifications delivered, and a signed webhook if you do want the data back in your own pipeline.
An open create endpoint on your Strapi instance will be found and hammered. Now your admin panel fills with junk entries, and your database and your content share fate with a bot wave. Furrow absorbs that traffic on its own infrastructure.
Provider credentials, templates, failure handling — per environment, per site. Furrow sends notification emails with template tokens on every tier, no plugin configuration.
Self-hosting Strapi means every form POST is compute you pay for and traffic you defend. Rate limiting, honeypot, Turnstile, and domain allowlisting are Furrow defaults — configured once per project, inherited by every form.
Two ways in
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 Strapi site.free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Point the form in your frontend at a Furrow Forms endpoint instead of opening a public create permission on Strapi. Furrow stores the submission, filters spam, and emails your team; your Strapi API stays read-only to anonymous visitors.
It exposes your production CMS to unauthenticated writes: spam entries in the admin panel, database growth you didn’t plan, and your content infrastructure absorbing bot traffic. It works — the tutorials exist for a reason — but a dedicated form backend keeps that risk off the system your site depends on.
Yes, the safe way around: subscribe your server to Furrow’s signed webhook and create entries with an authenticated API token. You get HMAC signatures to verify, automatic retries with backoff if your endpoint is down, and a delivery log — instead of a public write hole.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.