Skip to content
Sign inJoin waitlist

Forms reference — Cerette Next.js

Cerette for Next.js has two forms, both Framer’s inquiry form: one with the project type as a list of choices, one on each service’s page where the project type is a text field that starts with the service’s name.

Form Where Server action form in the payload Fields (name → label) Required
Inquiry Contact page, Services page src/lib/actions-contact.ts contact name Name, email Email, phone Phone, location Location, type Project type (a select), budget Project budget, details Project details type, budget
Service inquiry every service’s page src/lib/actions-service.ts service the same, with type Project type a text field that starts with the service’s name (“Architecture”) budget

Every field shows its label above it, as in Framer. Only the selects are required (Framer’s choice): Project type and Project budget start on an empty placeholder option (“Select project category”, “Select estimated budget”) that must be replaced. The name and the e-mail may be left empty — make them required in the copy if you need them (see 5).

<Form> (design system) → server action (src/lib/actions-<form>.ts) → deliver() → provider(s) chosen in FORM_PROVIDER

The forms, their states (sending, “Thank you”, “Something went wrong”) and the spam honeypot work out of the box. Where the submissions go is a setting, not code.

Copy .env.example to .env.local (or add the variables in your host, e.g. Vercel → Settings → Environment Variables) and set FORM_PROVIDER. Restart npm run dev after changing it.

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 submission 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

Mailchimp needs an e-mail address: Cerette’s forms require only the two selects (as the Framer template does), so mark the Email field required in src/content/pages/forms.ts before you turn Mailchimp on — a submission without one fails there.

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. Each submission carries the form’s name (form: contact or service) and its title (title: “New inquiry from the Cerette website”, “New service inquiry from the Cerette website”).

Variable For Needed What it is
FORM_PROVIDER all no (console when missing) console, webhook, mailchimp, resend, or several, separated by commas
FORM_WEBHOOK_URL webhook yes The address that receives the POST
FORM_WEBHOOK_SECRET webhook no Sent as Authorization: Bearer <secret>; leave it empty to send no header
MAILCHIMP_API_KEY mailchimp yes Ends in your data center, e.g. …-us21
MAILCHIMP_AUDIENCE_ID mailchimp yes The audience that receives the contacts
MAILCHIMP_STATUS mailchimp no (transactional) The status of a new contact: transactional, pending or subscribed
RESEND_API_KEY resend yes Your Resend API key
FORM_EMAIL_TO resend yes The recipient, or several separated by commas
FORM_EMAIL_FROM resend yes A sender on a domain verified in Resend, e.g. Cerette <forms@yourdomain.com>

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.

  • console: [forms] <title> followed by the submitted values (data) as an object, for example [forms] New inquiry from the Cerette website { name: 'Jane Smith', email: 'jane@example.com', details: '…' }. In development it shows in the terminal that runs npm run dev; on a host, in its logs.
  • webhook: one POST of 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, and FNAME from name; MAILCHIMP_STATUS is 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 from FORM_EMAIL_FROM to FORM_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.
  • 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. Cerette’s forms don’t.
  • Merge fields: the name (name) → FNAME (a new audience’s default). Change mergeFields at the top of providers/mailchimp.ts if your audience uses other tags.
{
"form": "contact",
"title": "New inquiry from the Cerette website",
"submittedAt": "2026-10-21T10:48:23.256Z",
"data": {
"name": "Jane Smith", "email": "jane@example.com", "phone": "+1 555 010 2030", "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 ("" when left empty — every field but the required ones can be), and labels the label of each, in the order of the form. The service form sends the same keys with "form": "service" and the title “New service inquiry from the Cerette website”.

Each 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. deliver() looks at it first: when it holds anything, the visitor is shown “Thank you” and nothing is sent, so the bot moves on. Keep it as it is, and don’t give a real field the name fax.

submitContact and submitService list the fields of their form (the copy: contactForm and serviceForm) and call deliver(data, { form, title, fields, required }) from src/lib/forms/deliver.ts, which:

  1. drops the submission if the honeypot is filled;
  2. reads each listed field from the submitted data (trimmed);
  3. returns the error state when a required field (the project type of the contact form, the budget) is empty;
  4. builds the submission (form, title, submittedAt, data, labels) and gives it to every provider named in FORM_PROVIDER;
  5. returns the success state, or the error state with the reason logged ([forms] <title> could not be delivered).

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

Section titled “4. Add your own provider (HubSpot, Brevo, Airtable, a database…)”
  1. Create src/lib/forms/providers/<name>.ts:

    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, toLines(submission) returns "Label: value" lines for every filled field, and env(name) reads a required variable with a clear error. Both forms have the fields name and email (optional, as in Framer: a provider that needs a person should check them).

  • Fields and labels live in the copy: contactForm and serviceForm in src/content/pages/forms.ts. name is the key providers receive, label is the label shown above the field (and what the notification shows), placeholder is what people read in the empty field, required adds the browser’s check, options are the choices of a select. The button’s three texts and the title of the notification are there too.
  • Required fields come from the same required flags: the server action checks them again before it sends anything. Only the project type (a select) and the budget are required, as in Framer. Add required: true to name and email if you want them — and do, if you send to Mailchimp: it needs an e-mail and fails the submission without one.
  • A new field: add it to the form’s fields, then place it in src/components/sections/InquiryForm.tsx, which lays out both forms in a two-column grid from tablets up (<FormField {...fields.<name>} />; md:col-span-2 for a full-width one). A control without a visible label is a <FieldControl>.
  • A new form: lay it out with <Form> and <FieldControl> or <FormField>, add a server action next to the others (src/lib/actions-<form>.ts, “use server”) that calls deliver(data, { form, title, fields, required }), and add the form name to FormKind in types.ts.