WAITLIST · VUE

Waitlist for Vue

Pre-launch capture form with optional referral source. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for Vue

form.htmlhtml23 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Vue + Waitlistplatform-specific integration guide

Why Vue developers choose splitforms for waitlist

Vue's reactivity system is great for UI state but doesn't help with form delivery — you still need somewhere to POST the data. The waitlist on this page uses Vue's <code>@submit.prevent</code> to intercept the form event, builds a <code>FormData</code> object, and fires a <code>fetch</code> POST to splitforms. Works identically in Vue 2 (Options API) and Vue 3 (Composition API with <code>ref</code>). Because it's just a standard POST, it works with Nuxt, Vite, and any Vue bundler without a custom plugin or module.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Vue.

Use the HTML snippet on this page, keep the waitlist fields visible in your Vue UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains email, name, how did you hear about us?. Required fields are email.

native vue reality

Vue ships nothing form-related beyond v-model for two-way binding.

use case fit

Pre-launch waitlists let you capture demand before the product ships. The multi-step form qualifies the use case so launch-day conversions skew toward the highest-intent signups.

§ 01Waitlist × Vuewhy this combination, in 80 words

Built for Vue developers who hate operating a backend.

Splitforms is the form backend for Vue sites. One POST endpoint, no SDK, no plugin — drop the waitlist into a page and ship.

Splitforms is the form backend for Vue sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan

✓500 form submissions per month
✓2 forms on Free; unlimited forms on Pro
✓Spam protection (honeypot + classifier)
✓Webhooks: Slack, Discord, WhatsApp, custom
✓CSV export of all submissions
✓Email notifications (CC and BCC on Pro)

§ 02Copy-paste codeHTML · 23 lines

Drop into any Vue project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Vue page, and ship. No build-time integration required.

form.htmlhtml23 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first waitlist submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the waitlist into your Vue project

Drop the form snippet into a Vue page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippethtml

<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New waitlist signup

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bWaitlist Signup Form (Pre-Launch Lead Capture)template-specific playbook

The reason this waitlist exists.

Multi-step (Typeform-style) · webhooks into Loops / ConvertKit / Beehiiv.

why it matters

Waitlists are the cheapest growth tool a pre-launch product has — Superhuman, Notion, and Linear all built sizable waitlists before paid launch. The form captures email plus a question or two on use case ('what would you use this for?', 'what tools do you use today?') so the launch sequence segments by intent. Multi-step flow boosts completion vs a single form — the prospect commits in step 1 and answers the qualifying questions in step 2-3 with momentum. Push waitlist signups to a dedicated ESP audience (Loops, ConvertKit, Beehiiv) so launch-day emails segment by use case and target the highest-intent signups first.

route the submission

Step 1: capture email

Single email field — keep step 1 frictionless. Loss-rate from email-only is near-zero; once the email is in, momentum carries through later qualifying questions.

Step 2-3: qualify use case

One or two questions on use case ('what problem brings you here?', 'what tools do you use today?'). Optional but most users complete because they're invested by step 2.

Push to ESP segment

Webhook to Loops / ConvertKit / Beehiiv / Mailchimp into a 'waitlist' audience. Launch-day emails segment by use case so the highest-intent signups get the first invite waves.

§ 03cVue production notesnative path · deploy · gotchas

What changes when this waitlist lives in Vue.

These notes come from the Vue platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Vue ships nothing form-related beyond v-model for two-way binding. To deliver a submission anywhere, you write the same backend stack as React: an Express/Nitro/Hono route, an email provider, a database, spam filtering. Nuxt narrows the gap with /server/api routes, but you're still operating the route. Pinia/Vuex don't help — they're for client state, not network. The Vue ecosystem has FormKit and VeeValidate for validation UX, but neither delivers submissions. Splitforms slots in as the missing endpoint: any Vue 2 / Vue 3 / Nuxt setup posts a FormData to one URL, gets { success: true } back, done.

deploy notes

Vue + Vite produces a static bundle that deploys anywhere. For Nuxt, every Nitro preset (Vercel, Netlify, Node, Cloudflare, static, AWS Lambda) works identically because the form posts client-side. On Cloudflare Pages with the Nuxt Cloudflare preset, avoid proxying through /server/api — the fetch round-trip eats the 10ms CPU budget on the free tier; post directly to splitforms. Vite-only (non-Nuxt) projects must use VITE_SPLITFORMS_KEY or env vars are silently undefined client-side. Nuxt uses runtimeConfig.public.splitformsKey. Both inline the value into the bundle, so domain-lock the key in the splitforms dashboard.

Vue gotcha

ref() doesn't auto-unwrap inside a template handler

If you write status === 'loading' inside <script setup> it works because Vue auto-unwraps refs in templates — but inside a function you need status.value. Mixing the two is the #1 cause of "why isn't my button disabling?" bugs in Vue contact forms.

Vue gotcha

v-model and FormData read different sources

If you bind inputs with v-model="name" to a ref and then build new FormData(e.target), FormData reads the DOM — which Vue keeps in sync — so it works. But if you bind a computed value and the input doesn't have a name attribute, FormData drops it silently. Always set name="…" on every input.

Vue gotcha

@submit fires before .prevent unless you spell it right

Vue's event modifier syntax is @submit.prevent="onSubmit". People often write @submit="onSubmit" and then forget to call e.preventDefault() inside the handler — the page reloads and the fetch is cancelled mid-flight.

Vue gotcha

Vite env vars need the VITE_ prefix or they're undefined at build

Reading import.meta.env.SPLITFORMS_KEY returns undefined unless you rename it to VITE_SPLITFORMS_KEY (Vite) or expose it via runtimeConfig (Nuxt). Vite intentionally hides anything without the prefix to prevent leaking server secrets.

PATTERN A

Pattern A — `<script setup>` with status ref

Modern Vue 3 SFC, half the boilerplate of Options API, full reactivity. status is a single ref<'idle' | 'loading' | 'ok' | 'err'>. Use the same wiring for the waitlist fields on this page.

pattern-a.txtvue17 lines

01<script setup>
02import { ref } from "vue";
03const status = ref("idle");
04async function onSubmit(e) {
05  status.value = "loading";
06  const fd = new FormData(e.target);
07  fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
08  const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
09  status.value = (await r.json()).success ? "ok" : "err";
10}
11</script>
12<template>
13  <form @submit.prevent="onSubmit">
14    <input name="email" type="email" required />
15    <button :disabled="status === 'loading'">Send</button>
16  </form>
17</template>

PATTERN B

Pattern B — composable for reuse across forms

Wrap the splitforms POST in a useSplitforms() composable. Multiple forms (contact, newsletter, demo) share one implementation. Test once, ship everywhere. Use the same wiring for the waitlist fields on this page.

pattern-b.txtvue14 lines

01// composables/useSplitforms.js
02import { ref } from "vue";
03export function useSplitforms() {
04  const status = ref("idle");
05  async function submit(formEl, formName) {
06    status.value = "loading";
07    const fd = new FormData(formEl);
08    fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
09    fd.append("form-name", formName);
10    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
11    status.value = (await r.json()).success ? "ok" : "err";
12  }
13  return { status, submit };
14}

§ 04Field-by-field rundown3 fields · names you POST

What every field actually does.

Each field below ships in the waitlist template — rename, remove, or add your own. Splitforms accepts any name you POST.

emailREQUIRED

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com

name

TEXT

Name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Optional

referral

SELECT

How did you hear about us?

Dropdown — keeps responses normalised so you can filter the dashboard.

TwitterFriendSearchNewsletterOther

§ 05Waitlist on other frameworks21 frameworks · same backend

One backend. Every framework.

The same waitlist template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Waitlist on Vue — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this waitlist work on Vue?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Vue site without server-side code, plugins, or SDKs. Drop the snippet into a Vue page or component and submissions land in your splitforms dashboard.

02How much does the waitlist cost on Vue?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (email, name, how did you hear about us?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the waitlist?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Vue as on any other framework.

05Can I send the waitlist submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static Vue site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I show waitlist position / numbers?

Showing 'you're #347 in line' on the confirmation creates social proof but invites comparison. Showing total waitlist size ('join 2,500 people on the waitlist') without per-person position is the safer middle. Refer-a-friend mechanics that move people up the list (Robinhood-style) drive viral growth but require more eng work.

08How do I trigger launch invites in waves?

Tag waitlist signups by use case in the ESP audience (Loops, ConvertKit). Launch-day, segment by tag and send invite waves over 48-72 hours. Highest-intent / closest-fit goes first; broadest casts go last. Spreads server load and lets you triage onboarding support.

09Can I integrate with Loops / ConvertKit / Beehiiv?

Yes — webhook the JSON. Loops has direct webhook support and is purpose-built for product transactional + waitlist email. ConvertKit and Beehiiv accept via API or Zapier. All three handle the launch-sequence segmentation cleanly.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Vue5 adjacent patterns

Ship a waitlist on Vue in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Vue project.

Get free access key →Read the docs

founders pricing locked in · early access open

Waitlist for Vue

Why Vue developers choose splitforms for waitlist

Yes — this is the shortest safe path for Vue.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Vue developers who hate operating a backend.

Drop into any Vue project.

Generate, embed, receive.

Generate a free splitforms key

Paste the waitlist into your Vue project

Receive submissions

The reason this waitlist exists.

Step 1: capture email

Step 2-3: qualify use case

Push to ESP segment

What changes when this waitlist lives in Vue.

ref() doesn't auto-unwrap inside a template handler

v-model and FormData read different sources

@submit fires before .prevent unless you spell it right

Vite env vars need the VITE_ prefix or they're undefined at build

Pattern A — `<script setup>` with status ref

Pattern B — composable for reuse across forms

What every field actually does.

Email

Name

How did you hear about us?

One backend. Every framework.

Waitlist on Vue — FAQ.

splitforms vs everything else.

Other ready-to-ship Vue forms.

Ship a waitlist on Vue in 60 seconds.