Formserve
Features Templates Pricing Docs Blog FAQ
Sign in Create endpoint
Bolt guide

How to add a backend to a Bolt form backend

Connect a Bolt-generated website form without building a backend API.

No backend API route Honeypot spam trap Works with any host
FS Formserve Team Product guides
Bolt Stack
4 steps setup Walkthrough
Try without signup Read the docs
Form <form action="…" method="POST"> in the browser
Formserve Validates & filters spam, then stores the submission
Deliver Notifications sent to email, Slack, Sheets, or webhooks
Why a backend at all

The browser can't handle the submission on its own.

An HTML form has to POST somewhere. Formserve is that destination — it receives the submission, screens it for spam, stores it, and sends the notifications. No server to run, no serverless function, no fragile scripts.

Connect a Bolt-generated website form without building a backend API.

§ 01 · Context Why it still needs a backend.

Bolt.new is strong for shipping a site quickly, but the generated form still needs a reliable submissions backend. Formserve gives the form a real POST destination while keeping the generated layout, styles, and frontend structure intact.

The form POSTs to an endpoint URL, the submission is stored, and notifications are sent according to the endpoint settings. It's a safer, more maintainable replacement for fragile mailto: patterns or one-off scripts that break the first time your host changes.

§ 02 · Why More than just an email alert.

When the backend stores every submission first and notifies second, you get three things a raw SMTP relay can't give you:

Inbox plus notifications

Every submission stays searchable in the Formserve inbox — not just buried in one person's mailbox.

Spam stopped first

Allowed domains, honeypot fields, rate limits, and blocklists run before any notification is sent.

Route later if needed

Start email-only, then add Slack, webhooks, Sheets, or a CRM later without touching the form.

And because the submission is stored, delivery failures stay visible instead of disappearing into email logs. If a notification bounces, you can see it, retry it, and still have the lead.

§ 03 · Setup How to connect it.

None of these steps involve writing server code. First, make sure you have the essentials in place:

Existing Bolt form UI

Use the generated form that already exists in the Bolt project.

Endpoint URL

Create a Formserve endpoint first and use the real public URL in the prompt or code edit.

Field names

Make sure visible form fields still render meaningful name attributes.

Live test

Test the generated site after deployment, not only in preview.

1
Start from the generated page — Do not replace the form or redesign the section. Keep the generated Bolt output and only fix form submission behavior.
2
Point the form to Formserve — Use a direct POST flow with the endpoint URL and include _honeypot as a hidden field.
3
Keep friendly feedback — Add or preserve loading, success, and failure states so the site still feels polished.
4
Test from Bolt preview and live deploy — Send a test submission from the live URL and verify it appears in Formserve.

§ 04 · Example Keep the form simple.

There's nothing special about the markup. The only required change is the action attribute. The hidden _honeypot input is the one spam-prevention field worth adding by hand:

bolt.html — minimal 
<form action="https://formserve.io/f/YOUR_ENDPOINT_KEY" method="POST">
  <input type="text" name="_honeypot" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" />
  <input type="text" name="name" required />
  <input type="email" name="email" required />
  <textarea name="message" required></textarea>
  <button type="submit">Send message</button>
</form>
No fetch required for the basic case.

A plain action + method="POST" works with zero JavaScript. Reach for fetch only when you want to stay on the page and show a custom success state.

Before you launch

  • ✓ Preserve the generated Bolt layout and spacing.
  • ✓ Check every field has a name attribute.
  • ✓ Configure allowed domains before the final test.
  • ✓ Confirm the inbox receives the submission with the correct field values.

Common mistakes

  • ! Replacing the whole generated component instead of patching submission behavior.
  • ! Omitting _honeypot.
  • ! Using placeholder success text that never waits for the real request.
  • ! Not validating the final live deploy.

Get a working endpoint in under a minute.

Paste the URL into your form's action and send a test. Free up to 100 submissions / month — no credit card.

Try without signup

§ 05 · FAQ Common questions.

Do I need to build a backend for a Bolt form backend?
No. Formserve is the backend. You point the form at a Formserve endpoint URL and it stores submissions, filters spam, and sends notifications, so you never build or host a server yourself.
Does this work with Bolt?
Yes. A Bolt form submits standard named fields, and Formserve accepts them the same way any HTML form posts data — no SDK or plugin required.
Will connecting Formserve change my form design?
No. You keep your existing markup and styling. Only the submission behaviour changes so the form posts to your endpoint instead of a server you maintain.
How do I stop spam without a CAPTCHA?
Add the hidden _honeypot field shown in the code sample and set a spam protection level on the endpoint. Formserve blocks bots invisibly instead of showing a CAPTCHA.
FS
Formserve Team
We build the form backend behind thousands of HTML forms — from one-page contact forms to high-traffic launch pages.
Bolt Guide No-code

Keep reading

All guides →
Cursor

Cursor form backend

Give Cursor a generated prompt that wires your existing form to Formserve.

4 steps · Setup guide
v0

v0 form backend

Use Formserve as the backend for forms generated by v0.

4 steps · Setup guide
Claude Code

Claude Code form backend

Ask Claude Code to scan your project and update the most relevant form component.

4 steps · Setup guide