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

How to add a backend to an Astro contact form

Use a plain HTML form in Astro or enhance it with client-side JavaScript.

No backend API route Honeypot spam trap Works with any host
FS Formserve Team Product guides
Astro 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.

Use a plain HTML form in Astro or enhance it with client-side JavaScript.

§ 01 · Context Why it still needs a backend.

Astro is ideal for static sites, and static sites still need working forms. Formserve lets your Astro page use plain HTML while the backend, inbox, spam protection, and notifications live outside the project.

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:

Static form markup

A normal form in an .astro page is enough.

Endpoint action

Set action to the Formserve endpoint URL.

POST method

Use method='POST' for browser submissions.

Production domain

Add your deployed Astro domain to allowed domains.

1
Create the endpoint — Name it after the page or campaign the Astro form belongs to.
2
Paste the endpoint URL — Use it directly in the form action attribute.
3
Add fields and honeypot — Use named inputs and the hidden _honeypot field.
4
Deploy and submit — Test from the live Astro site, not only the local dev server.

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

astro.html — minimal 
---
// src/pages/contact.astro
---

<form action="https://formserve.io/f/YOUR_ENDPOINT_KEY" method="POST">
  <input name="_honeypot" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" />
  <input name="email" type="email" required />
  <textarea name="message" required></textarea>
  <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

  • ✓ Use plain HTML first before adding client JavaScript.
  • ✓ Confirm the form submits from the built site.
  • ✓ Add allowed domains for the production URL.
  • ✓ Check Formserve inbox and delivery status.

Common mistakes

  • ! Adding a server adapter only for contact forms.
  • ! Forgetting method='POST'.
  • ! Testing only with astro dev.
  • ! Using fields without names.

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 Astro contact 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 Astro?
Yes. An Astro 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.
Astro Guide No-code

Keep reading

All guides →
HTML

HTML form

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

4 steps · Setup guide
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