Headless CMS · works with Furrow Forms
Skip the custom-Lambda chore that ships with every Contentful build.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Contentful site.agent-readable recipe: /forms-for/contentful.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="email" type="email" required />
<textarea name="message" required />
<button>Send</button>
</form>
);
}The gap
Contentful is deliberate about its boundary: it is a content platform, and form submissions sit outside it. So every Contentful build ends with the same chore — someone writes a serverless function to catch the contact form, bolts on a captcha, wires up an email service, and promises to monitor it. Multiply by every site your team runs. Furrow Forms is that function as a product: one endpoint per form, spam stack on by default, notifications and signed webhooks included, settings inherited across each site.
The build is scoped around content modeling and the frontend — then the contact form needs storage, spam, and email, and a custom function appears in the repo. It works until it quietly doesn’t. Furrow makes it a managed dependency instead.
Teams pick Contentful to standardize content ops across many properties — then hand-roll a different form handler per site. Furrow’s project-level settings cascade gives forms the same operational story: configure once, inherit everywhere.
A dedicated backend gives a clean answer: submissions live in Furrow with configurable retention, reach your team by email, and reach your systems by HMAC-signed webhooks you can verify — not in an ad-hoc function’s logs.
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 Contentful site.free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
No — Contentful is a content platform and deliberately leaves form handling to your stack. The common answers are a custom serverless function or a dedicated form backend. Furrow Forms is the latter: endpoint, spam filtering, storage, notifications, and signed webhooks as a service.
Most write a serverless function per site: validate, filter spam, send email, store somewhere. It is a recurring per-project cost and an unowned service in production. A form backend replaces it with one POST endpoint and project-level settings your whole roster of sites inherits.
Yes — every Furrow delivery is an HMAC-signed webhook with automatic retries (up to 8 attempts over ~24 hours) and a delivery log. Point it at your integration layer and treat submissions like any other verified event stream.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.