Contact Form (with phone) for Nuxt
Name, email, phone, company, reason — for B2B inquiries that need qualification. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why Nuxt developers choose splitforms for contact form (with phone)
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 contact form (with phone) 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.
Yes — this is the shortest safe path for Nuxt.
Use the HTML snippet on this page, keep the contact form (with phone) fields visible in your Nuxt UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the HTML version, then replace YOUR_ACCESS_KEY.
The posted payload contains full name, work email, phone, company, what's this about?, message. Required fields are full name, work email, phone, what's this about? and message.
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.
A contact form with a phone number field that auto-formats as the user types — (555) 123-4567 emerges from raw digits. Pure pattern validation, optional JS mask for the live formatting.
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 contact form (with phone) 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.
- ✓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)
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.
Generate, embed, receive.
Three actions stand between you and your first contact form (with phone) submission. None of them require a backend, a database, or a CAPTCHA library.
Generate a free splitforms key
Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.
Paste the contact form (with phone) 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.
Receive submissions
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
The reason this contact form (with phone) exists.
Mobile-friendly numeric keypad, live mask, format-tolerant.
Phone fields suffer from format chaos — users type +1 555 123 4567, (555) 123 4567, 555.123.4567, 5551234567. Three options: accept anything and normalize server-side (best for international), use a pattern attribute for client-side validation (good for US-only), or apply a JavaScript mask that formats as the user types (highest conversion, more code). splitforms accepts any format and your form's UX is whichever approach fits your audience.
Use type="tel" not type="text"
Mobile keyboards open the numeric keypad for tel inputs. Desktop accepts the same characters as text but signals intent.
Add a pattern attribute for validation
`pattern="[0-9() +-]+"` allows the common phone characters. Or use a strict US format: `pattern="\(?\d{3}\)?[ -]?\d{3}[ -]?\d{4}"`.
(Optional) Add the JS mask
On input, strip non-digits and reformat to `(XXX) XXX-XXXX`. The mask runs on every keystroke, giving live formatting feedback.
What changes when this contact form (with phone) 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.
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.
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.
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.
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.
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 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 — 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 contact form (with phone) fields on this page.
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 contact form (with phone) fields on this page.
What every field actually does.
Each field below ships in the contact form (with phone) template — rename, remove, or add your own. Splitforms accepts any name you POST.
Full name
Greeting + dashboard label so submissions don't all read 'anonymous'.
Work email
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
Phone
Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.
Company
Lets you sort enterprise vs SMB inquiries before you reply.
What's this about?
Routes the lead to the right inbox folder or teammate.
Message
Free-text context — what the visitor actually wants you to know.
One backend. Every framework.
The same contact form (with phone) template works on every framework splitforms supports. Pick yours.
Contact Form (with phone) on Nuxt — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship Nuxt forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a contact form (with phone) 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.