Atlas Forms + Gatsby
Forms for static sites
Gatsby sites are static by default, but forms need a backend. Atlas provides webhooks, file uploads, and spam protection without requiring Gatsby Functions or server-side code.
Why Atlas for Gatsby?
The missing backend for static sites
Webhook Notifications
Send each submission as a JSON webhook to Zapier, Make, n8n, or your own endpoint, with automatic retries. Slack and Discord alerts on Pro and Business.
File Uploads
Accept file uploads on a static Gatsby site.
Spam Protection
Honeypot field, per-IP rate limiting, attack-pattern detection with a spam quarantine, and an IP blocklist. Cloudflare Turnstile is optional.
No Gatsby Functions
Works with static builds. No serverless functions required.
Quick Setup
Add forms to Gatsby in minutes
Create an Atlas Form
Sign up for Atlas and create a new form. Copy your unique form endpoint URL.
https://atlasforms.app/f/abc123xyz
Add Form Component
Create a React component with a standard HTML form pointing to Atlas.
// src/components/ContactForm.jsx
import React from "react"
export default function ContactForm() {
return (
<form
action="https://atlasforms.app/f/abc123xyz"
method="POST"
>
<input type="text" name="name" placeholder="Name" required />
<input type="email" name="email" placeholder="Email" required />
<textarea name="message" placeholder="Message" />
<button type="submit">Send</button>
</form>
)
}Build and Deploy
Build your Gatsby site and deploy. Make sure your site's domain is in the form's Allowed Origins (Form Settings), or submissions from it are rejected.
gatsby build gatsby serve # Deploy to Netlify, Vercel, or any static host
What You Get
Full form backend for Gatsby sites
| Feature | Static | + Atlas |
|---|---|---|
| Form submissions | - | |
| Webhook notifications | - | |
| File uploads | - | |
| Spam protection | - | |
| Submission dashboard | - | |
| API access | - | |
| Static build |
Ready to add forms to Gatsby?
Start free and upgrade when you need more. No credit card required.