Slices ship pages; forms need a backend
A form slice without a backend is a promise the frontend can’t keep. Backed by Furrow, the slice is self-sufficient: marketers reuse it freely, and every instance inherits the project’s spam stack and routing.
Visual CMS · works with Furrow Forms
Contact forms for Prismic sites
A form slice marketers can reuse — the backend is already wired.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Prismic site.agent-readable recipe: /forms-for/prismic.md
prefer clicking? start in the dashboard
export default function ContactForm({ slice }) {
const loadedAt = Date.now();
return (
<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={loadedAt} />
<input name="name" type="text" required />
<input name="email" type="email" required />
<textarea name="message" required />
<button>{slice.primary.button_label}</button>
</form>
);
}The gap
Why Prismic sites need a form backend
Prismic’s slice model lets marketing ship pages without waiting on developers — until the page needs a form. Then someone has to answer where the submission goes, who gets notified, and what stops the bots, and the answer usually becomes a custom API route in the Next.js app. Furrow Forms removes that step: build a ContactForm slice that POSTs to a Furrow endpoint, and every page built in the Page Builder gets a working form with spam, storage, notifications, and signed webhooks handled.
The custom API route tax
Each Prismic build that handles forms in-app carries a route that validates, filters, and emails — unowned code that pages depend on. Furrow replaces it with managed infrastructure and a delivery log.
Landing pages mean campaign-speed changes
New campaign, new recipients, new CRM webhook. In Furrow those are project-level settings changed via dashboard, API, or agent — live immediately, no rebuild.
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 Prismic 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.
- 02Build the form slice once, pointed at your form’s endpoint.
- 03Set domains, recipients, and webhooks on the project — inherited by every form.
- 04Marketers reuse the slice across pages; you change routing in one place when campaigns change.
free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Prismic + Furrow Forms, answered
How do I add a contact form to a Prismic site?
Create a form slice in your frontend that POSTs to a Furrow Forms endpoint, then let editors place it through the Page Builder. Furrow stores submissions, filters spam, emails your team, and fires signed webhooks — no custom API route in your Next.js app.
Where do submissions from a Prismic site go?
To Furrow: stored with configurable retention, emailed to the recipients configured on the project, and optionally delivered to your systems by HMAC-signed webhooks with automatic retries. Prismic remains purely the content layer.
Can we run multiple forms across landing pages?
Yes — forms are unlimited on every Furrow tier, and all of them inherit the project’s security and routing settings. A campaign-specific form is one create call (or one agent prompt) away, and spam never counts toward your submission quota.
The form backend your agent can run.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.