HTML guide

How to add a backend to an HTML form

Point a normal HTML form at Formserve and receive submissions instantly.

No backend API route Honeypot spam trap Works with any host

FS Formserve Team Product guides

HTML 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.

Point a normal HTML form at Formserve and receive submissions instantly.

§ 01 · Context Why it still needs a backend.

A plain HTML form is the fastest way to use Formserve. You keep the markup in your site, set the form action to your endpoint URL, and Formserve handles the backend work: storage, spam checks, email notifications, exports, and integrations.

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:

Endpoint URL

Create a Formserve endpoint and copy the public form URL.

POST method

Set the form method to POST so browser submissions are sent correctly.

Named fields

Every input, select, and textarea must have a name attribute.

Honeypot field

Add a hidden _honeypot input to catch basic bots without CAPTCHA.

Create a Formserve endpoint — Use a name that matches the form purpose, such as Contact, Waitlist, or Quote request.

Update the form tag — Paste the endpoint URL into the action attribute and keep method set to POST.

Add field names and honeypot — Make sure visible fields use useful names like email, name, company, and message.

Test from the real page — Submit once locally, then again from the deployed domain after allowed domains are configured.

§ 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:

html.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" />
  <label>Email <input type="email" name="email" required></label>
  <label>Message <textarea name="message" required></textarea></label>
  <button type="submit">Send</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

✓ Submit with a valid email address.
✓ Confirm the entry appears in the inbox.
✓ Add your production domain to allowed domains.
✓ Enable email or Slack notifications if needed.

Common mistakes

! Using GET instead of POST.
! Forgetting name attributes.
! Putting the endpoint URL in JavaScript only when plain HTML would work.
! Testing only from localhost and not from production.

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 an HTML form?

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 HTML?

Yes. An HTML 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.

Formserve Team

We build the form backend behind thousands of HTML forms — from one-page contact forms to high-traffic launch pages.

HTML Guide No-code

Keep reading

All guides →

React

React contact form

Use FormData from your existing React component and POST it to Formserve.

4 steps · Setup guide

Next.js

Next.js contact form

Connect a Next.js form without creating an unnecessary API route.

4 steps · Setup guide

Vue

Vue contact form

Submit a Vue form to Formserve while keeping your current UI intact.

4 steps · Setup guide