Skip to content
Sign inJoin waitlist

Forms reference — Fitbricks Astro

The three forms of Fitbricks for Astro — Contact (“Get in Touch”), Free trial (“Claim Free Trial”) and the booking form on every club page (“Book Your Class Now”) — share one pipeline and work in one of three ways. You choose with environment variables (copy .env.example to .env, or set them in your host’s dashboard); no code changes.

Form Where name of the <Form> / form in the payload Fields (name → label)
Contact Contact page contact Name Name, Email Email (required), Phone Phone, Contact Time Contact Time Preferences (required), Message Message
Free trial Free trial page free-trial Name, Email (required), Phone, Contact Time (required), City Preferred Location, Class Preferred Class, Message
Booking Every club page booking Name, Phone, Email (required), Club Club Location (prefilled with the club), Date Preferred Date, Time Preferred Time, Message Additional Notes
Mode Set Hosting Where submissions go
Demo (default) nothing any static host Nowhere: the form shows “Thank you” and logs the fields in the browser console.
Static PUBLIC_FORM_ENDPOINT any static host Posted from the browser to a form service or webhook.
Server PUBLIC_FORM_MODE=server + FORM_PROVIDER a host with an Astro adapter Delivered by the site’s own route to console, webhook, Mailchimp or Resend.

Every mode shows the same states on the Submit button (spinner, “Thank you”, “Something went wrong”), keeps the typed values after an error, resets the form after success (the booking form back to its club) and drops spam caught by the hidden honeypot field.

<Form> (design system) → browser: PUBLIC_FORM_ENDPOINT, or the demo
→ server mode: POST /api/forms/<form> → deliver() → provider(s) chosen in FORM_PROVIDER

1. Static mode: form services and webhooks

Section titled “1. Static mode: form services and webhooks”

Set PUBLIC_FORM_ENDPOINT to the URL the service gives you. The form posts multipart/form-data with Accept: application/json, and the service must answer with a 2xx status.

Service PUBLIC_FORM_ENDPOINT Notes
Formspree https://formspree.io/f/<form id> Emails you each submission.
Web3Forms https://api.web3forms.com/submit Also set PUBLIC_FORM_ACCESS_KEY.
Getform, Basin the form’s endpoint URL
Zapier, Make, n8n, Pipedream the webhook (“catch hook”) URL Route submissions anywhere: Mailchimp, Google Sheets, Slack, a CRM.

Fields sent: every input by its name (see the table above) plus form (contact, free-trial or booking) and subject (the form’s title: “Get in Touch”, “Claim Free Trial”, “Book Your Class Now”). One endpoint receives all three: tell them apart by form.

The endpoint is public (it is in the page), which is how these services are designed to work; they filter spam themselves. A build with PUBLIC_FORM_ENDPOINT set sends the style guide’s sample form nowhere: it is marked demo.

For Mailchimp or Resend without a third-party service, run the forms on your server:

  1. Add the adapter for your host: npx astro add vercel (or netlify, node, …).
  2. Set PUBLIC_FORM_MODE=server and choose providers with FORM_PROVIDER.

The forms then post to POST /api/forms/<form> (src/lib/forms/route.ts, added by src/integrations/forms.ts). Without an adapter the build stops with NoAdapterInstalled. Astro rejects cross-site posts to the route, so only your own pages can submit. Environment variables are read when the server runs (process.env, then the values of the build).

FORM_PROVIDER What happens Variables
console (default) Printed to the server log. For development. —
webhook Posted as JSON to a URL — Zapier, Make, n8n, Pipedream, Formspree, Slack workflow, your own API. FORM_WEBHOOK_URL, optional FORM_WEBHOOK_SECRET (sent as Authorization: Bearer …)
mailchimp Sender added or updated in an audience, tagged with the form, the rest saved as a note. MAILCHIMP_API_KEY, MAILCHIMP_AUDIENCE_ID, optional MAILCHIMP_STATUS
resend Emailed to you; replying answers the sender. RESEND_API_KEY, FORM_EMAIL_TO, FORM_EMAIL_FROM

Use several at once with a comma: FORM_PROVIDER=resend,mailchimp emails you and adds the contact to Mailchimp. If any of them fails, the visitor sees “Something went wrong” (their input stays in the form) and the reason is logged on the server. A provider that needs a variable and doesn’t find it stops that submission with Missing environment variable <NAME> (see .env.example) in the server log.

  • API key: Profile → Extras → API keys. It ends in your data center (…-us21); nothing else to configure.
  • Audience ID: Audience → Settings → Audience name and defaults.
  • Consent: new contacts are added as transactional — they can receive replies, not campaigns. Use pending to send a double opt-in email, or subscribed only if the form asks for marketing consent.
  • Merge fields: name → FNAME (the whole name), phone → PHONE (a new audience’s defaults). Change the map at the top of providers/mailchimp.ts if your audience uses other tags.
{
"form": "contact",
"title": "Get in Touch",
"submittedAt": "2026-11-09T10:48:23.256Z",
"data": { "Name": "Ana Lee", "Email": "ana@example.com", "Phone": "+1 555 0100", "Contact Time": "Morning", "Message": "Hi!" },
"labels": { "Name": "Name", "Email": "Email", "Phone": "Phone", "Contact Time": "Contact Time Preferences", "Message": "Message" }
}

data has a key for every field of that form, as "" when left empty, and labels the label of each, in the order of the form.

Every form carries a hidden text field named fax (honeypotField in src/design-system/components/forms/form-state.ts): it is out of sight and out of the tab order, a person never fills it, and bots usually do. The form shows “Thank you” without sending anything when it holds anything (and deliver() does the same on the server), so the bot moves on. Don’t give a real field the name fax.

4. Your own provider (HubSpot, Brevo, Airtable, a database…)

Section titled “4. Your own provider (HubSpot, Brevo, Airtable, a database…)”
  1. Create src/lib/forms/providers/<name>.ts exporting a FormProvider — throw to show the error state:

    import { env, valueOf, type FormProvider } from "../types";
    export const brevoProvider: FormProvider = {
    name: "brevo",
    async send(submission) {
    const response = await fetch("https://api.brevo.com/v3/contacts", {
    method: "POST",
    headers: { "api-key": env("BREVO_API_KEY"), "Content-Type": "application/json" },
    body: JSON.stringify({ email: valueOf(submission, "email"), attributes: { FIRSTNAME: valueOf(submission, "name") }, updateEnabled: true }),
    });
    if (!response.ok) throw new Error(`Brevo responded ${response.status}: ${await response.text()}`);
    },
    };
  2. Register it in providers/index.ts (brevo: brevoProvider).

  3. Set FORM_PROVIDER=brevo and its variables in .env.example / your host.

Helpers from types.ts: valueOf(submission, name) returns one field as text (names match ignoring case), toLines(submission) returns "Label: value" lines for every filled field, and env(name) reads a required variable with a clear error.

  • Texts and fields live in the copy: form in src/content/pages/contact.json and free-trial.json, booking in club.json (name is the key services and providers receive, label is what people read; the free trial’s location and class options come from the cities and the first 10 programs).
  • Required fields follow the required flags in the copy: the browser checks them first and, in server mode, src/lib/forms/definitions.ts checks them again before it sends anything.
  • A new form: lay it out with <Form name="…">, <FormField> and <RadioGroup>, give the endpoint with formEndpoint("…") (src/lib/forms/endpoint.ts), add its definition to definitions.ts for server mode and its name to FormKind in types.ts.