Headless CMS · works with Furrow Forms
Keep submissions out of your Content Lake — one endpoint, spam handled.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Sanity site.agent-readable recipe: /forms-for/sanity.md
prefer clicking? start in the dashboard
'use client';
export function ContactForm() {
const loadedAt = Date.now();
async function submit(formData: FormData) {
await fetch('https://api.furrowforms.com/s/fp_k7m2', {
method: 'POST',
body: formData,
});
}
return (
<form action={submit}>
<input type="text" name="_gotcha" style={{ display: 'none' }} tabIndex={-1} />
<input type="hidden" name="_ft" value={loadedAt} />
<input name="name" type="text" required />
<input name="email" type="email" required />
<textarea name="message" required />
<button>Send</button>
</form>
);
}The gap
Sanity is deliberately a content platform, not an everything platform: structured documents, GROQ, real-time collaboration. Form submissions are explicitly not its job — and the workarounds people reach for (a write token mutating submissions into the dataset, or a hand-rolled serverless function) each create new problems. Furrow Forms is the boring, dedicated answer: your Next.js or Astro frontend POSTs to one endpoint; storage, spam, notifications, and signed webhooks are handled; your Content Lake stays content.
Mutating submissions into your dataset from the client means shipping a token that can write to your production content — and inviting every bot on the internet to use it. Furrow’s public keys are safe in client HTML by design; protection comes from the spam stack, not secrecy.
Submissions written into Sanity appear right where your editors work, count against your quotas, and need cleanup queries when the bots arrive. Rejected and honeypot-caught posts never even reach Furrow’s stored submissions — or your bill.
The other standard answer — an API route that validates, filters, emails, and stores — is a small product you now maintain per site. Furrow is that product, already built, with retried webhooks when you want the data in your own pipeline.
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 Sanity site.free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Don’t write them into your dataset. Point the form in your frontend at a dedicated form backend: POST to a Furrow Forms endpoint and let it store the submission, filter spam, notify your team, and deliver a signed webhook. Sanity stays the system of record for content, not inbound mail.
Technically yes, via a mutation with a write token — but that token cannot safely live in a browser, spam lands next to your editors’ documents, and submissions count toward dataset usage. A form backend avoids all three; if you still want submissions in Sanity, consume Furrow’s webhook server-side and write them in on your terms.
Yes — the form is plain markup in whatever renders your frontend. Furrow generates snippets for HTML, Astro, and Next.js from the form’s field contract, honeypot and Turnstile included.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.