adapter-static can’t run form actions
Prerendered SvelteKit output is plain files. A Furrow-backed form keeps the site static and the form functional — no adapter change, no server bill.
Frameworks & SSGs · works with Furrow Forms
Forms that work under adapter-static — no +page.server.ts action required.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my SvelteKit site.agent-readable recipe: /forms-for/sveltekit.md
prefer clicking? start in the dashboard
<script>
const loadedAt = Date.now();
let sent = false;
async function submit(e) {
e.preventDefault();
const res = await fetch('https://api.furrowforms.com/s/fp_k7m2', {
method: 'POST',
body: new FormData(e.target),
});
sent = (await res.json()).ok;
}
</script>
{#if sent}
<p>Thanks — we’ll be in touch.</p>
{:else}
<form method="POST" action="https://api.furrowforms.com/s/fp_k7m2" on:submit={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></textarea>
<button>Send</button>
</form>
{/if}The gap
SvelteKit’s form actions are elegant — and server-only. The moment you build with adapter-static (a marketing site, docs, a portfolio), there is no server to run them, and the usual answer becomes a third-party endpoint anyway. Furrow Forms is that endpoint done properly: POST from a plain form or a tiny submit handler, get JSON back, and let managed infrastructure handle spam, storage, notifications, and signed webhooks. On server-rendered deployments it still earns its keep — it is the mail delivery, spam stack, and retry logic you were about to write.
Prerendered SvelteKit output is plain files. A Furrow-backed form keeps the site static and the form functional — no adapter change, no server bill.
Start with a classic POST that redirects to your thank-you page; layer a fetch handler for inline success when JS is available. Both hit the same endpoint.
Honeypot, Turnstile, domain allowlist, rate limits, email templates, webhook signing and retries — project-level settings, not code in your repo.
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 SvelteKit site.free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Point a plain form (or a fetch call) at a Furrow Forms endpoint. adapter-static output stays fully prerendered, and Furrow handles spam filtering, storage, notifications, and the thank-you redirect.
You don’t need to — the browser can POST directly to Furrow. If you prefer routing through your own action on a server-rendered deployment, your action can forward the submission server-side; but for most sites the direct POST is simpler and works everywhere.
It lives on Furrow’s side: honeypot field, optional Cloudflare Turnstile with project-level keys, a per-project domain allowlist, and per-IP rate limiting. Rejected submissions never reach your inbox or count toward quota.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.