FEEDBACK FORM · NUXT

Feedback Form for Nuxt

Rating + free-text feedback with optional follow-up email. 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 Nuxt

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 feedback submission">
04 
05  <label for="rating">How would you rate your experience? *</label>
06  <select id="rating" name="rating" required>
07    <option value="">Choose…</option>
08    <option>★★★★★</option>
09    <option>★★★★☆</option>
10    <option>★★★☆☆</option>
11    <option>★★☆☆☆</option>
12    <option>★☆☆☆☆</option>
13  </select>
14  <label for="feedback">What can we do better? *</label>
15  <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required></textarea>
16  <label for="email">Email (optional, for follow-up)</label>
17  <input id="email" type="email" name="email" placeholder="you@example.com">
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

§ 00Nuxt + Feedback Formplatform-specific integration guide

Why Nuxt developers choose splitforms for feedback form

Nuxt 3's auto-imports and server routes make it easy to add form handling, but setting up a server-side submission pipeline (SMTP, spam checks, database, dashboard) is still a significant project. The feedback form on this page uses <code>useState</code> for submit state and a <code>fetch</code> POST to splitforms — no server route, no Nitro engine dependency, no SMTP configuration. Because the form posts directly from the browser, it works identically on static hosting (Netlify, Cloudflare Pages) and on Nuxt's server-rendered pages.

§ 00Quick answerHTML · feedback

Yes — this is the shortest safe path for Nuxt.

Use the HTML snippet on this page, keep the feedback form fields visible in your Nuxt 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 how would you rate your experience?, what can we do better?, email (optional, for follow-up). Required fields are how would you rate your experience? and what can we do better?.

native nuxt reality

Nuxt 3's Nitro server gives you /server/api/contact.post.ts for free — write a handler, parse FormData, send email, store the submission, fan out a webhook.

use case fit

Customer feedback is the cheapest product research you have. The form captures NPS / CSAT plus an open comment — and routes negative responses to a Slack channel for same-day triage.

§ 01Feedback Form × Nuxtwhy this combination, in 80 words

Built for Nuxt developers who hate operating a backend.

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

Splitforms is the form backend for Nuxt 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 Nuxt project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Nuxt 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 feedback submission">
04 
05  <label for="rating">How would you rate your experience? *</label>
06  <select id="rating" name="rating" required>
07    <option value="">Choose…</option>
08    <option>★★★★★</option>
09    <option>★★★★☆</option>
10    <option>★★★☆☆</option>
11    <option>★★☆☆☆</option>
12    <option>★☆☆☆☆</option>
13  </select>
14  <label for="feedback">What can we do better? *</label>
15  <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required></textarea>
16  <label for="email">Email (optional, for follow-up)</label>
17  <input id="email" type="email" name="email" placeholder="you@example.com">
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 feedback form 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 feedback form into your Nuxt project

Drop the form snippet into a Nuxt 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 feedback submission

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?

§ 03bCustomer Feedback Form (NPS / CSAT / Open-Ended)template-specific playbook

The reason this feedback form exists.

Webhooks into Slack / Linear / Productboard · NPS detractor triage in minutes.

why it matters

Feedback forms cost almost nothing to ship and pay back disproportionately — every NPS detractor (score 0-6) is a conversation that prevents churn, every promoter (9-10) is a referral or testimonial source. The form is simple: 0-10 rating, an optional comment, and an email. The leverage is in the routing: detractors auto-DM your support lead in Slack within minutes, promoters get a 'mind leaving us a G2 / Trustpilot review?' follow-up, passives go into a digest. Survey tools (SurveyMonkey, Typeform, Hotjar) charge $30-100/mo for the same pattern. The form pattern is 30 lines of HTML.

route the submission

Capture rating + comment

Required: 0-10 NPS rating (or 1-5 CSAT for transactional surveys). Optional: comment textarea, email for follow-up. Keep it minimal — long surveys tank completion.

Route by score

Webhook branches on score: 0-6 (detractors) DM Slack support channel; 7-8 (passives) go to weekly digest; 9-10 (promoters) trigger a G2 / Trustpilot review-request email.

Push to your tools

Detractor comments to Linear / Productboard for product triage. Promoter quotes to a 'testimonials' Notion database for marketing. Raw data to a CSV / BigQuery / dbt warehouse for trend analysis.

§ 03cNuxt production notesnative path · deploy · gotchas

What changes when this feedback form lives in Nuxt.

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

without splitforms

Nuxt 3's Nitro server gives you /server/api/contact.post.ts for free — write a handler, parse FormData, send email, store the submission, fan out a webhook. The DX is good; the operational cost is the same as any framework: an SMTP integration (Nodemailer + a transactional provider), a Postgres or KV store for submissions, anti-spam logic (honeypot + classifier or hCaptcha), and webhook signing if you want secure delivery to Slack/Discord/Make.com. Each feature is another deploy artifact, another env var, another thing to monitor. Splitforms is the inverse: skip the /server/api route entirely (post directly from the page), or proxy through a one-line Nitro route to keep the key server-side.

deploy notes

Nuxt's Nitro server abstracts away deployment — pick a preset (vercel, netlify, cloudflare-pages, cloudflare-workers, node-server, static, aws-lambda, digital-ocean) and ship. The form's POST is cross-origin to splitforms, so the preset doesn't affect delivery. On Cloudflare Workers (10ms CPU on free tier), strongly prefer Pattern A — Pattern B's $fetch round-trip can blow the budget under load. Use runtimeConfig.public.splitformsKey (client-exposed) for Pattern A and runtimeConfig.splitformsKey (server-only) for Pattern B. Both populate from NUXT_PUBLIC_SPLITFORMS_KEY / NUXT_SPLITFORMS_KEY env vars.

Nuxt gotcha

runtimeConfig.public is required for client exposure — `runtimeConfig.x` is server-only

Nuxt's runtimeConfig has two scopes. Anything under runtimeConfig.public is exposed to the browser bundle; anything else is server-only. If you put splitformsKey directly in runtimeConfig (not .public), useRuntimeConfig().splitformsKey returns undefined client-side.

Nuxt gotcha

useRuntimeConfig() called outside setup() returns empty object

Calling useRuntimeConfig() inside a regular function (not inside <script setup> or a composable) returns {}. Always call it at the top of <script setup> and capture the value, then use config.public.splitformsKey inside event handlers.

Nuxt gotcha

Nitro Cloudflare preset has 10ms CPU time on the free plan

If you proxy the splitforms call through a Nuxt server route (/server/api/contact.post.ts), the fetch round-trip eats your Cloudflare Worker CPU budget. On Cloudflare Pages Free tier, this can fail under load. Skip the proxy: have the form POST directly to splitforms.com.

Nuxt gotcha

Nuxt Content's <ContentDoc> rendering can break form HTML

If you embed the form in a Markdown file rendered by Nuxt Content, MDC syntax may interpret your inputs as MDC components. Wrap the form in <NuxtContent> (or use :component="ContactForm") instead of inline form HTML.

PATTERN A

Pattern A — direct browser POST from `<script setup>`

No server route. Page reads the access key from useRuntimeConfig().public.splitformsKey. Works identically on every Nitro preset. Use the same wiring for the feedback form fields on this page.

pattern-a.txtvue18 lines

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

PATTERN B

Pattern B — Nitro server route (key stays server-side)

Page posts to /api/contact (a Nitro route) which appends the access key from runtimeConfig.splitformsKey (private) and proxies to splitforms. Adds a hop but the key never reaches the browser bundle. Use the same wiring for the feedback form fields on this page.

pattern-b.txtvue11 lines

01// server/api/contact.post.ts
02export default defineEventHandler(async (event) => {
03  const config = useRuntimeConfig();
04  const parts = await readMultipartFormData(event);
05  const fd = new FormData();
06  for (const p of parts ?? []) p.name && fd.append(p.name, p.data.toString("utf8"));
07  fd.append("access_key", config.splitformsKey);
08  const res = await $fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
09  if (!res.success) throw createError({ statusCode: 400, message: res.message });
10  return { ok: true };
11});

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

What every field actually does.

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

ratingREQUIRED

SELECT

How would you rate your experience?

NPS / CSAT signal — quantitative complement to the comment field.

★★★★★★★★★☆★★★☆☆★★☆☆☆★☆☆☆☆

feedbackREQUIRED

TEXTAREA

What can we do better?

Free-text input — no character limit, expands as the visitor types.

placeholder · Be honest — we won't take it personally.

Email (optional, for follow-up)

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

placeholder · you@example.com

§ 05Feedback Form on other frameworks21 frameworks · same backend

One backend. Every framework.

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

§ 06Questions9 answered

Feedback Form on Nuxt — FAQ.

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

01Does this feedback form work on Nuxt?

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

02How much does the feedback form cost on Nuxt?

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 (how would you rate your experience?, what can we do better?, email (optional, for follow-up)…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the feedback form?

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 Nuxt as on any other framework.

05Can I send the feedback form 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 Nuxt 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 use NPS or CSAT?

NPS (0-10) for relationship surveys ('how likely are you to recommend us?') sent quarterly or after major moments. CSAT (1-5) for transactional surveys ('how was this support ticket?') sent right after the interaction. Different questions, different cadences, both common patterns.

08Will I get response bias from a public form?

Yes — open-link feedback skews toward people with strong feelings (positive or negative). For statistically representative measurement, send the survey via email to a random sample of users. The public form catches the heat-of-moment feedback you'd otherwise miss.

09Can I push to Slack / Linear / Productboard?

Yes — webhook the JSON. Slack has incoming webhooks (free); Linear and Productboard accept inbound issue creation via Zapier or native APIs. Detractor comments showing up as a Linear issue with the rating prefilled in the title is a powerful workflow.

§ 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 Nuxt5 adjacent patterns

Ship a feedback form on Nuxt in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Feedback Form for Nuxt

Why Nuxt developers choose splitforms for feedback form

Yes — this is the shortest safe path for Nuxt.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Nuxt developers who hate operating a backend.

Drop into any Nuxt project.

Generate, embed, receive.

Generate a free splitforms key

Paste the feedback form into your Nuxt project

Receive submissions

The reason this feedback form exists.

Capture rating + comment

Route by score

Push to your tools

What changes when this feedback form lives in Nuxt.

runtimeConfig.public is required for client exposure — `runtimeConfig.x` is server-only

useRuntimeConfig() called outside setup() returns empty object

Nitro Cloudflare preset has 10ms CPU time on the free plan

Nuxt Content's <ContentDoc> rendering can break form HTML

Pattern A — direct browser POST from `<script setup>`

Pattern B — Nitro server route (key stays server-side)

What every field actually does.

How would you rate your experience?

What can we do better?

Email (optional, for follow-up)

One backend. Every framework.

Feedback Form on Nuxt — FAQ.

splitforms vs everything else.

Other ready-to-ship Nuxt forms.

Ship a feedback form on Nuxt in 60 seconds.