Skip to content
Wrenform

Docs / Contact form guides

Add a contact form to a Gatsby site

A Gatsby contact form from one prompt or one React component, no Functions.

Last updated 2026-11-20View as Markdown
Add a working contact form to this Gatsby site. Create the form by sending POST https://wrenform.com/api/v1/quick-forms with JSON {"email": "YOUR_EMAIL", "framework": "react"} (if you can't make HTTP requests, give me the curl command to run). Put the returned snippet on a /contact page or section, matching the site's style: a label for each field, type="email" on the email field, and keep the _honey field exactly as returned. Show a thank-you message after sending and an error message on failure. It's a Gatsby site, so put the form in src/components/ContactForm.jsx, render it on src/pages/contact.js, and read the form ID from process.env.GATSBY_WRENFORM_ID. No Gatsby Functions. Add no dependencies, API keys or server code. Then tell me to check my inbox for the Wrenform email and click Confirm, because messages are held until I do.

Replace YOUR_EMAIL with the address that should get the messages, and paste. This creates a form without an account: no sign-up, no mail provider, free for 250 submissions a month. Nothing is forwarded until you click Confirm in the email we send, and unconfirmed forms are deleted after 7 days. Prefer the dashboard? Create a form and use the snippet below.

Gatsby builds static pages, so a form usually needs a Gatsby Function and a mail provider. With Wrenform the visitor's browser posts straight to the endpoint, and the form ID is public, so it can sit in client code. Gatsby is React, so the prompt asks for the React snippet.

Steps

  1. Paste the prompt into your coding tool, or save the component below as src/components/ContactForm.jsx.
  2. Render it on src/pages/contact.js.
  3. Click Confirm in the email from Wrenform.
  4. Deploy.

Lock the form to your site. A form created this way accepts posts from any site. Once you've confirmed, sign in with the same address and add your published domain under Allowed origins in the form's settings, for example https://example.com.

Or paste the code

// src/ContactForm.jsx (React + Vite, also Lovable and Bolt projects)
import { useState } from "react";

export default function ContactForm() {
  const [status, setStatus] = useState("idle");

  async function onSubmit(e) {
    e.preventDefault();
    const form = e.currentTarget;
    setStatus("sending");
    try {
      const res = await fetch("https://wrenform.com/f/YOUR_FORM_ID", {
        method: "POST",
        headers: { Accept: "application/json" },
        body: new FormData(form),
      });
      setStatus(res.ok ? "sent" : "error");
      if (res.ok) form.reset();
    } catch {
      setStatus("error");
    }
  }

  return (
    <form onSubmit={onSubmit}>
      <label>Name <input type="text" name="name" autoComplete="name" required /></label>
      <label>Email <input type="email" name="email" autoComplete="email" required /></label>
      <label>Message <textarea name="message" required /></label>
      <input type="text" name="_honey" style={{ display: "none" }} tabIndex={-1} autoComplete="off" />
      <button type="submit" disabled={status === "sending"}>Send</button>
      <p role="status">
        {status === "sent" && "Thanks, your message was sent."}
        {status === "error" && "Something went wrong. Please try again."}
      </p>
    </form>
  );
}

To keep the ID out of the code, put GATSBY_WRENFORM_ID=YOUR_FORM_ID in .env.development and .env.production, and build the URL from process.env.GATSBY_WRENFORM_ID. Only GATSBY_ variables reach the browser. A plain <form method="POST" action="https://wrenform.com/f/YOUR_FORM_ID"> also works with no JavaScript.

Spam and email

  • The hidden _honey field catches most bots. Keep it in the form, hidden, with autocomplete="off".
  • A timing check marks submissions sent less than 3 seconds after the form loaded as spam, when the form sends the timing field. The optional script in the HTML snippet adds it; see the timing field. No captcha is needed.
  • Each real submission is emailed to you and shown in your dashboard. If a field is missing from the email, check that its input has a name and isn't disabled.
  • Submissions are stored in the EU. Free keeps them for 30 days, paid plans for 365 days.

Test it

Run gatsby develop, open /contact and send the form. After confirming, the message is in your inbox and your dashboard. Send one more from the deployed site.

Common problems

  • The form sends but no email arrives. The address hasn't confirmed yet. Look for the email from Wrenform, also in spam.
  • 403 origin_not_allowed. The page's origin isn't in the form's Allowed origins. Add it, including any preview domain you test from. See errors.
  • The URL ends in /f/ or /f/undefined. The form ID isn't set. Check the variable starts with GATSBY_, then restart gatsby develop.
  • The page reloads instead of showing the result. The submit handler isn't attached: check onSubmit on the form.
  • Anything else. See troubleshooting.

Next steps

Something wrong or unclear on this page? Report a problem: write to hello [at] wrenform.com with the page address (/docs/guides/contact-form-gatsby).