splitforms.com
BUG REPORT · GATSBY

Bug Report for Gatsby

Bug reports with severity, environment, and reproduction steps. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Gatsby
Form.tsxtsx57 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function BugForm() {
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 bug report');
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="title">Short summary *</label>
32 <input id="title" type="text" name="title" placeholder="What went wrong?" required />
33 <label htmlFor="severity">Severity *</label>
34 <select id="severity" name="severity" required>
35 <option value="">Choose…</option>
36 <option>Critical</option>
37 <option>High</option>
38 <option>Medium</option>
39 <option>Low</option>
40 </select>
41 <label htmlFor="browser">Browser &amp; OS</label>
42 <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS" />
43 <label htmlFor="steps">Steps to reproduce *</label>
44 <textarea id="steps" name="steps" placeholder="1. Go to…
452. Click…
463. See error" required />
47 <label htmlFor="email">Your email (so we can follow up) *</label>
48 <input id="email" type="email" name="email" placeholder="you@example.com" required />
49
50 <button type="submit" disabled={status === 'sending'}>
51 {status === 'sending' ? 'Sending…' : 'Send'}
52 </button>
53
54 {status === 'error' && <p>Something went wrong. Try again.</p>}
55 </form>
56 );
57}
500
submissions / mo, free
5
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Gatsby + Bug Reportplatform-specific integration guide

Why Gatsby developers choose splitforms for bug report

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 bug report 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 · support

Yes — this is the shortest safe path for Gatsby.

Use the React / Next.js snippet on this page, keep the bug report 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 short summary, severity, browser & os, steps to reproduce, your email (so we can follow up). Required fields are short summary, severity, steps to reproduce and your email (so we can follow up).

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

User-reported bugs are signal — but only if the report has steps-to-reproduce and a screenshot. The form forces the structure, then files the issue automatically.

§ 01Bug Report × 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 bug report 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 · 57 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.tsxtsx57 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function BugForm() {
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 bug report');
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="title">Short summary *</label>
32 <input id="title" type="text" name="title" placeholder="What went wrong?" required />
33 <label htmlFor="severity">Severity *</label>
34 <select id="severity" name="severity" required>
35 <option value="">Choose…</option>
36 <option>Critical</option>
37 <option>High</option>
38 <option>Medium</option>
39 <option>Low</option>
40 </select>
41 <label htmlFor="browser">Browser &amp; OS</label>
42 <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS" />
43 <label htmlFor="steps">Steps to reproduce *</label>
44 <textarea id="steps" name="steps" placeholder="1. Go to…
452. Click…
463. See error" required />
47 <label htmlFor="email">Your email (so we can follow up) *</label>
48 <input id="email" type="email" name="email" placeholder="you@example.com" required />
49
50 <button type="submit" disabled={status === 'sending'}>
51 {status === 'sending' ? 'Sending…' : 'Send'}
52 </button>
53
54 {status === 'error' && <p>Something went wrong. Try again.</p>}
55 </form>
56 );
57}
ALTPrefer plain HTML? View the universal bug report HTML snippet28 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 bug report">

  <label for="title">Short summary *</label>
  <input id="title" type="text" name="title" placeholder="What went wrong?" required>
  <label for="severity">Severity *</label>
  <select id="severity" name="severity" required>
    <option value="">Choose…</option>
    <option>Critical</option>
    <option>High</option>
    <option>Medium</option>
    <option>Low</option>
  </select>
  <label for="browser">Browser &amp; OS</label>
  <input id="browser" type="text" name="browser" placeholder="Chrome 120 / macOS">
  <label for="steps">Steps to reproduce *</label>
  <textarea id="steps" name="steps" placeholder="1. Go to…
2. Click…
3. See error" required></textarea>
  <label for="email">Your email (so we can follow up) *</label>
  <input id="email" type="email" name="email" placeholder="you@example.com" required>

  <!-- 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 bug report 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 bug report 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 bug report
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?
§ 03bBug Report Form (Issue Submission)template-specific playbook

The reason this bug report exists.

Screenshot upload (Pro) · webhooks into Linear / GitHub Issues / Slack.

why it matters

Bug reports without reproduction steps waste hours of triage. The form structures the report — what happened, what was expected, steps to reproduce, browser / OS / device, screenshot. Screenshot upload is critical: 'the page broke' tells you nothing; a screenshot of the broken state tells you everything. Webhook the structured report into Linear or GitHub Issues so it lands as a triageable ticket, not a Slack message that scrolls away. For SaaS teams the time saved is huge — instead of a 4-message back-and-forth gathering basic context, the engineer opens the issue and starts debugging.

route the submission
01

Structure the report

Required: what happened, what you expected, steps to reproduce. Optional: browser, OS, device, URL where it occurred. Most templates auto-detect browser/OS via JS so the user doesn't have to fill them.

02

Screenshot upload

Pro file upload — drag-and-drop a screenshot or screen recording. Multi-file accepted. Image attachments arrive on the email and via webhook with signed URLs.

03

Webhook into Linear / GitHub

Lands as a Linear issue or GitHub issue with the structured report as the body and the screenshot embedded. Engineer opens, reproduces, fixes — no triage thread needed.

§ 03cGatsby production notesnative path · deploy · gotchas

What changes when this bug report 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 bug report 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 bug report 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 rundown5 fields · names you POST

What every field actually does.

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

titleREQUIRED
TEXT

Short summary

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

placeholder · What went wrong?
severityREQUIRED
SELECT

Severity

Triage signal — drives whether this pages on-call or waits till Monday.

CriticalHighMediumLow
browser
TEXT

Browser & OS

Repro context for engineering — saves a back-and-forth.

placeholder · Chrome 120 / macOS
stepsREQUIRED
TEXTAREA

Steps to reproduce

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

placeholder · 1. Go to… 2. Click… 3. See error
emailREQUIRED
EMAIL

Your email (so we can follow up)

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

placeholder · you@example.com
§ 06Questions9 answered

Bug Report on GatsbyFAQ.

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

01Does this bug report 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 bug report 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 (short summary, severity, browser & os, steps to reproduce…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the bug report?
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 bug report 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.
07Should I auto-detect browser / OS?
Yes — JavaScript can read navigator.userAgent and pre-fill hidden fields with browser name, version, OS, and screen size. The user doesn't see them; the engineer gets them. Saves 90% of 'what browser are you on?' replies.
08Can I integrate with Linear / GitHub / Sentry?
Yes — webhook the JSON. Linear and GitHub both accept inbound issue creation via API or Zapier. Sentry doesn't accept user-reported bugs as events but you can webhook to a Slack channel where the on-call engineer triages and creates the Sentry issue manually.
09How do I prevent abuse / spam in bug reports?
Public bug-report forms attract spam — hidden honeypot plus splitforms' classifier catches most. Require an email field; bots filling random emails get filtered by the classifier. For severe abuse, gate the form behind a logged-in user session.
§ 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 bug report 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