Headless CMS · works with Furrow Forms
Your database deserves better than an anonymous-write collection.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Directus site.agent-readable recipe: /forms-for/directus.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
Directus turns your SQL database into an API — so the tempting contact-form recipe is obvious: make a submissions collection, grant the public role create access, done. Except now anonymous internet traffic writes directly into the database that runs your project, and the spam cleanup happens in the same Data Studio your team works in. Furrow Forms keeps that write path external: the form POSTs to Furrow, spam dies there, and verified submissions can flow back into Directus through a signed webhook — authenticated, on your terms.
The public-create recipe points bots at the same SQL database your application depends on. Growth, junk rows, and cleanup are now database-administration problems. Furrow absorbs the raw traffic and stores submissions on its side.
Self-hosted Directus means you tune the throttles and eat the traffic. Furrow ships per-IP, per-form rate limits, honeypot, Turnstile, and domain allowlisting — on by default, configured once per project.
If you automate on submissions with Directus Flows, feed them from Furrow’s HMAC-signed webhook rather than an open collection — you can verify every payload’s signature and timestamp before acting on it.
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 Directus site.free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Point the form at a Furrow Forms endpoint instead of granting public create access on a collection. Furrow handles spam, storage, and notifications; if you want submissions inside Directus, consume the signed webhook and insert them with an authenticated call.
It routes unauthenticated internet traffic straight into your SQL database: spam rows beside real data, storage growth, and cleanup inside the Data Studio your team uses daily. It is fine for a prototype; for production, a dedicated form backend keeps that surface off your database.
Yes — point the project webhook at a Flow’s webhook trigger (or any endpoint you run). Payloads are HMAC-SHA256 signed with a timestamp header, retried with backoff up to 8 attempts, and logged, so your automation acts only on verified submissions.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.