splitforms.com
CONTACT FORM (WITH PHONE) · GATSBY

Contact Form (with phone) for Gatsby

Name, email, phone, company, reason — for B2B inquiries that need qualification. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Gatsby
Form.tsxtsx59 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function ContactDetailedForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New detailed contact submission');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Full name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Work email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@company.com" required />
35 <label htmlFor="phone">Phone *</label>
36 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required />
37 <label htmlFor="company">Company</label>
38 <input id="company" type="text" name="company" placeholder="Acme Inc" />
39 <label htmlFor="reason">What's this about? *</label>
40 <select id="reason" name="reason" required>
41 <option value="">Choose…</option>
42 <option>Sales / pricing</option>
43 <option>Partnerships</option>
44 <option>Press / media</option>
45 <option>Support</option>
46 <option>Careers</option>
47 <option>Other</option>
48 </select>
49 <label htmlFor="message">Message *</label>
50 <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required />
51
52 <button type="submit" disabled={status === 'sending'}>
53 {status === 'sending' ? 'Sending…' : 'Send'}
54 </button>
55
56 {status === 'error' && <p>Something went wrong. Try again.</p>}
57 </form>
58 );
59}
500
submissions / mo, free
6
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Gatsby + Contact Form (with phone)platform-specific integration guide

Why Gatsby developers choose splitforms for contact form (with phone)

Gatsby's static output is excellent for SEO and performance, but static HTML forms have no way to deliver submissions without a backend. Gatsby Cloud offers serverless functions, but wiring SMTP and a dashboard is a substantial project for what should be a simple contact form. The contact form (with phone) on this page posts from the browser to splitforms — no Gatsby Function, no API route, no build-time configuration. The form works identically whether you deploy to Gatsby Cloud, Netlify, Cloudflare Pages, or any static host.

§ 00Quick answerReact / Next.js · lead capture

Yes — this is the shortest safe path for Gatsby.

Use the React / Next.js snippet on this page, keep the contact form (with phone) fields visible in your Gatsby UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the React / Next.js 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.

native gatsby reality

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend.

use case fit

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.

§ 01Contact Form (with phone) × Gatsbywhy this combination, in 80 words

Built for Gatsby developers who hate operating a backend.

Splitforms is the form backend for Gatsby 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 Gatsby 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 codeReact / Next.js · 59 lines

Drop into any Gatsby project.

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

Form.tsxtsx59 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function ContactDetailedForm() {
06 const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07
08 async function onSubmit(e: FormEvent<HTMLFormElement>) {
09 e.preventDefault();
10 setStatus('sending');
11
12 const data = new FormData(e.currentTarget);
13 data.set('access_key', 'YOUR_ACCESS_KEY');
14 data.set('subject', 'New detailed contact submission');
15
16 const res = await fetch('https://splitforms.com/api/submit', {
17 method: 'POST',
18 body: data,
19 headers: { Accept: 'application/json' },
20 });
21
22 const json = await res.json();
23 setStatus(json.success ? 'sent' : 'error');
24 if (json.success) e.currentTarget.reset();
25 }
26
27 if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28
29 return (
30 <form onSubmit={onSubmit}>
31 <label htmlFor="name">Full name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane Builder" required />
33 <label htmlFor="email">Work email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@company.com" required />
35 <label htmlFor="phone">Phone *</label>
36 <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required />
37 <label htmlFor="company">Company</label>
38 <input id="company" type="text" name="company" placeholder="Acme Inc" />
39 <label htmlFor="reason">What's this about? *</label>
40 <select id="reason" name="reason" required>
41 <option value="">Choose…</option>
42 <option>Sales / pricing</option>
43 <option>Partnerships</option>
44 <option>Press / media</option>
45 <option>Support</option>
46 <option>Careers</option>
47 <option>Other</option>
48 </select>
49 <label htmlFor="message">Message *</label>
50 <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required />
51
52 <button type="submit" disabled={status === 'sending'}>
53 {status === 'sending' ? 'Sending…' : 'Send'}
54 </button>
55
56 {status === 'error' && <p>Something went wrong. Try again.</p>}
57 </form>
58 );
59}
ALTPrefer plain HTML? View the universal contact form (with phone) HTML snippet30 lines
form.htmlHTML
<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New detailed contact submission">

  <label for="name">Full name *</label>
  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
  <label for="email">Work email *</label>
  <input id="email" type="email" name="email" placeholder="jane@company.com" required>
  <label for="phone">Phone *</label>
  <input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required>
  <label for="company">Company</label>
  <input id="company" type="text" name="company" placeholder="Acme Inc">
  <label for="reason">What's this about? *</label>
  <select id="reason" name="reason" required>
    <option value="">Choose…</option>
    <option>Sales / pricing</option>
    <option>Partnerships</option>
    <option>Press / media</option>
    <option>Support</option>
    <option>Careers</option>
    <option>Other</option>
  </select>
  <label for="message">Message *</label>
  <textarea id="message" name="message" placeholder="Give us context — links, dates, deal size, anything we should know." required></textarea>

  <!-- honeypot — bots fill every field -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">

  <button type="submit">Send</button>
</form>
§ 03Setup3 steps · 60 seconds · zero config

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.

STEP 01GENERATE

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.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the contact form (with phone) into your Gatsby project

Drop the form snippet into a Gatsby 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.

snippettsx
'use client';
  …
</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 detailed contact 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?
§ 03bPhone Number Input Form (with masked input)template-specific playbook

The reason this contact form (with phone) exists.

Mobile-friendly numeric keypad, live mask, format-tolerant.

why it matters

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.

route the submission
01

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.

02

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}"`.

03

(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.

§ 03cGatsby production notesnative path · deploy · gotchas

What changes when this contact form (with phone) lives in Gatsby.

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

without splitforms

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend. Gatsby v4 had Functions running as Lambda-equivalent serverless routes; v5 removed them entirely. Result: every Gatsby contact form today uses an external service. Splitforms is a drop-in replacement — same shape as Netlify Forms (POST to a URL), same shape as Formspree, but with 5× the free monthly submissions and built-in spam filtering.

deploy notes

Gatsby builds static HTML + JS that deploys to any host: Netlify, Vercel, Cloudflare Pages, AWS Amplify, S3 + CloudFront, Gatsby Cloud (sunset 2024 — migrate). The form posts cross-origin to splitforms regardless of host. Env vars exposed to the browser bundle must be prefixed GATSBY_ — anything else is undefined client-side. The key gets bundled into the JS at build time; lock it to your domain in the splitforms dashboard. For headless Gatsby + WordPress / Contentful setups, the form lives in the React tree, not the CMS — no special CMS wiring required.

Gatsby gotcha

GATSBY_ prefix required for env vars exposed at build time

Gatsby's webpack config only exposes process.env.* variables prefixed with GATSBY_. If you write process.env.SPLITFORMS_KEY, you'll get undefined in the browser bundle. Rename to GATSBY_SPLITFORMS_KEY — and accept that it's bundled into the static JS (lock the key to your domain in the splitforms dashboard).

Gatsby gotcha

Gatsby's <Link> can't wrap a form's submit handler

Gatsby's <Link> component prevents default navigation. If you wrap your form in <Link to="/thanks"> thinking the redirect will fire, it won't — the form's submit event runs, but the navigation is suppressed. Use a hidden redirect input on the form and let splitforms handle the 302.

Gatsby gotcha

SSR + client hydration mismatch on form initial state

If you use useState('idle') in your form and render any state-dependent UI on first paint, Gatsby's static HTML and React's client render can diverge — you'll see a hydration warning. Render the form unconditionally; only render status messages inside the handler-triggered branches.

Gatsby gotcha

Gatsby v5 partial hydration changed how forms hydrate

Gatsby 5 introduced partial hydration via React Server Components. If your form is in a Server Component, the onSubmit handler won't bind. Add 'use client' at the top of the file (or use a separate ContactForm.client.jsx).

PATTERN A

Pattern A — React component (Gatsby v4/v5)

Standard React function component, useState for status. Drop into src/components/ContactForm.jsx and import on any page. Set GATSBY_SPLITFORMS_KEY in .env.production and .env.development. Use the same wiring for the contact form (with phone) fields on this page.

pattern-a.jsxjsx16 lines
01import React, { useState } from "react";
02export default function ContactForm() {
03 const [status, setStatus] = useState("idle");
04 return (
05 <form onSubmit={async (e) => {
06 e.preventDefault(); setStatus("loading");
07 const fd = new FormData(e.target);
08 fd.append("access_key", process.env.GATSBY_SPLITFORMS_KEY);
09 const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10 setStatus((await r.json()).success ? "ok" : "err");
11 }}>
12 <input name="email" type="email" required />
13 <button disabled={status === "loading"}>Send</button>
14 </form>
15 );
16}
PATTERN B

Pattern B — partial hydration (Gatsby v5)

Gatsby 5's partial hydration mounts only the components marked client-bound. Add 'use client' at the top of the form file so the onSubmit handler binds at hydration time; the rest of the page stays static. Use the same wiring for the contact form (with phone) fields on this page.

pattern-b.jsxjsx7 lines
01// src/components/ContactForm.jsx
02"use client";
03import React, { useState } from "react";
04export default function ContactForm() {
05 const [status, setStatus] = useState("idle");
06 // ...same body as Pattern A
07}
§ 04Field-by-field rundown6 fields · names you POST

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.

nameREQUIRED
TEXT

Full name

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

placeholder · Jane Builder
emailREQUIRED
EMAIL

Work email

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

placeholder · jane@company.com
phoneREQUIRED
PHONE

Phone

Faster qualification — phone leads convert ~3× higher than email-only on B2B forms.

placeholder · +1 415 555 0142
company
TEXT

Company

Lets you sort enterprise vs SMB inquiries before you reply.

placeholder · Acme Inc
reasonREQUIRED
SELECT

What's this about?

Routes the lead to the right inbox folder or teammate.

Sales / pricingPartnershipsPress / mediaSupportCareersOther
messageREQUIRED
TEXTAREA

Message

Free-text context — what the visitor actually wants you to know.

placeholder · Give us context — links, dates, deal size, anything we should know.
§ 05Contact Form (with phone) on other frameworks21 frameworks · same backend

One backend. Every framework.

The same contact form (with phone) template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Contact Form (with phone) on GatsbyFAQ.

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

01Does this contact form (with phone) work on Gatsby?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Gatsby site without server-side code, plugins, or SDKs. Drop the snippet into a Gatsby page or component and submissions land in your splitforms dashboard.
02How much does the contact form (with phone) cost on Gatsby?
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 (full name, work email, phone, company…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the contact form (with phone)?
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 Gatsby as on any other framework.
05Can I send the contact form (with phone) 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 Gatsby 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.
07Why use type="tel" if it doesn't do anything special on desktop?
Two reasons. (1) Mobile keyboards: tel triggers the numeric keypad, dramatically reducing typos. (2) Accessibility: screen readers announce the field type, helping users with assistive tech understand what's expected. The 'no desktop benefit' is a feature, not a bug — the behavior matches user intent.
08Should I validate international or US-only?
Depends on your audience. International contact forms should accept any format (use a permissive pattern + server-side normalization). US-only forms can use a strict pattern that matches `(555) 123-4567`. Either way, splitforms accepts whatever format the user submits — the validation is for UX, not data integrity.
09Does the JS mask work with paste?
Yes — listen for both `input` and `paste` events, and reformat on every change. The pattern only validates on submit, so the mask gives live feedback as the user types or pastes.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

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

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a contact form (with phone) on Gatsby in 60 seconds.

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

Get free access key →Read the docs
founders pricing locked in · early access open