Vue guide

How to add a backend to a Vue contact form

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

No backend API route Honeypot spam trap Works with any host
FS Formserve Team Product guides
Vue Stack
4 steps setup Walkthrough
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.

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

§ 01 · Context Why it still needs a backend.

Vue makes it easy to keep the user experience inside the component while Formserve handles the backend. Use @submit.prevent, send FormData to your endpoint, and update local status after the request.

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:

Vue submit handler

Use @submit.prevent to avoid browser navigation.

Template refs

Read the form element through a ref or event target.

Named fields

Each input in the template needs a name attribute.

Status state

Track loading, success, and error messages.

1
Keep the Vue template — Preserve the component styling and only wire up submission behavior.
2
Add hidden spam field — Add _honeypot as a hidden input in the form template.
3
Submit FormData — Use fetch with method POST and the FormData object.
4
Reset and show feedback — Reset the form after success and show a message in the component.

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

vue.html — minimal
<script setup>
import { ref } from "vue";

const status = ref("");

async function submit(event) {
  const response = await fetch("https://formserve.io/f/YOUR_ENDPOINT_KEY", {
    method: "POST",
    body: new FormData(event.target)
  });

  status.value = response.ok ? "Thanks, we received your message." : "Please try again.";
  if (response.ok) event.target.reset();
}
</script>

<template>
  <form @submit.prevent="submit">
    <input name="_honeypot" tabindex="-1" autocomplete="off" class="hidden" />
    <input name="email" type="email" required />
    <textarea name="message" required />
    <button type="submit">Send</button>
    <p v-if="status">{{ status }}</p>
  </form>
</template>
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

  • Confirm @submit.prevent is on the form.
  • Check v-model fields still have name attributes.
  • Render status near the submit button.
  • Test after deployment.

Common mistakes

  • ! Relying on v-model names instead of input name attributes.
  • ! Submitting JSON when FormData would preserve form behavior.
  • ! Forgetting to reset the form after success.
  • ! Hiding errors from the user.

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 Vue 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 Vue?
Yes. A Vue 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.
Vue Guide No-code