Forms reference — Cerette Astro
The inquiry forms of Cerette for Astro (contact on Contact and Services, service on a service’s page) 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 and Services pages | contact |
name Name, email Email, phone Phone, location Location, type Project type, budget Project budget, details Project details |
| Service | each service page | service |
the same fields; type is a text field holding the service’s name |
| 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 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_PROVIDER1. 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) and
subject (“New inquiry from the Cerette website”). One endpoint can receive every form you add: 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 forms nowhere: they are marked demo.
2. Server mode: your own route
Section titled “2. Server mode: your own route”For Mailchimp or Resend without a third-party service, run the forms on your server:
- Add the adapter for your host:
npx astro add vercel(ornetlify,node, …). - Set
PUBLIC_FORM_MODE=serverand choose providers withFORM_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. The providers run at the same time, so when one fails the others have usually delivered already: sending
again can duplicate. The provider applies to every form; each submission says which form it came from (form, and
the title).
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; a name in FORM_PROVIDER that doesn’t exist does the same with Unknown FORM_PROVIDER "<name>". The visitor sees “Something went wrong” in both cases.
What each provider receives
Section titled “What each provider receives”console:[forms] <title>followed by the submitted values (data) as an object.webhook: onePOSTof JSON (Content-Type: application/json) holding the whole submission, as in the payload below. An answer that isn’t a success is an error.mailchimp: three calls. The sender is added or updated in the audience (email, in lower case, andFNAMEfromname;MAILCHIMP_STATUSis the status of a new contact only), tagged with the form’s title, and a note is added to the profile: the title, then one “Label: value” line for each field that was filled in.resend: one e-mail fromFORM_EMAIL_FROMtoFORM_EMAIL_TO. The subject is the title followed by the sender’s name (“New inquiry from the Cerette website — Jane Smith”; the title alone if the name is empty), the reply address is the sender’s e-mail, and the text is one “Label: value” line for each field that was filled in, then the time it was sent.
Mailchimp notes
Section titled “Mailchimp notes”- 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. Usependingto send a double opt-in email, orsubscribedonly if the form asks for marketing consent. Cerette’s form doesn’t. - Merge fields: the name (
name) →FNAME(a new audience’s default). ChangemergeFieldsat the top ofproviders/mailchimp.tsif your audience uses other tags, for examplephone: "PHONE".
Webhook payload
Section titled “Webhook payload”{ "form": "contact", "title": "New inquiry from the Cerette website", "submittedAt": "2026-10-07T10:48:23.256Z", "data": { "name": "Jane Smith", "email": "jane@example.com", "phone": "+1 555 0100", "location": "Austin, TX", "type": "Architecture", "budget": "$100K – $250K", "details": "A two-storey family house on a sloping lot." }, "labels": { "name": "Name", "email": "Email", "phone": "Phone", "location": "Location", "type": "Project type", "budget": "Project budget", "details": "Project details" }}data has a key for every field of that form (the names in the table above), as "" when left empty, and labels the
label of each, in the order of the form.
3. Spam: the honeypot
Section titled “3. Spam: the honeypot”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. Keep it as it is, and 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…)”-
Create
src/lib/forms/providers/<name>.tsexporting aFormProvider— 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()}`);},}; -
Register it in
providers/index.ts(brevo: brevoProvider). -
Set
FORM_PROVIDER=brevoand its variables in.env.example/ your host.
Helpers from types.ts: valueOf(submission, name) returns one field as text, toLines(submission) returns
"Label: value" lines for every filled field, and env(name) reads a required variable with a clear error. Every form
has the fields name and email, so a provider that needs a person can rely on them.
5. Change a form
Section titled “5. Change a form”- Fields and labels live in the copy:
contactFormandserviceForminsrc/content/pages/forms.json.nameis the key services and providers receive,labelis what people read (shown above each field, and the name providers give it),placeholderthe text inside an empty field,requiredadds the browser’s check,optionsare the choices of a select,defaultValueis what a field starts with. The button’s three texts and the title of the notification are there too. - Required fields come from the same
requiredflags: in server modesrc/lib/forms/definitions.tschecks them again before it sends anything. As in Framer, only the two selects (project type and budget) are required. - A new field: add it to the list in the copy and lay it out in
src/components/sections/InquiryForm.astro. - A new form: lay it out with
<Form name="…">and<FormField>, give the endpoint withformEndpoint("…")(src/lib/forms/endpoint.ts), add its definition todefinitions.tsfor server mode and its name toFormKindintypes.ts.