Forms reference — Catchup Next.js
Catchup for Next.js has one form: the inquiry on the Contact page.
| Form | Where | Server action | form in the payload |
Fields (name → label) |
Required |
|---|---|---|---|---|---|
| Inquiry | Contact page | src/lib/actions-contact.ts |
contact |
name Name, email Email, service Services, budget Budget, timeline Project Timeline, message Message |
name, email, budget, timeline |
Every field shows its label above it, as in Framer; required ones carry a “” in their placeholder (“Your name”). Services is one radio group (the chips: one choice or none). Budget and Project Timeline start on an empty placeholder option that must be replaced (Framer preselects “Estimated Budget” and “ASAP”, so its check passed without a choice).
<Form> (design system) → server action (src/lib/actions-contact.ts) → deliver() → provider(s) chosen in FORM_PROVIDERThe form, its 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. What the form asks, and how to edit it, is in Forms.
1. Pick a provider
Section titled “1. Pick a provider”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 message 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. Each submission carries the form’s name (form: contact) and its title (title: “New inquiry
from the Catchup website”).
The variables of .env.example
Section titled “The variables of .env.example”| 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. Catchup <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.
What each provider receives
Section titled “What each provider receives”console:[forms] <title>followed by the submitted values (data) as an object, for example[forms] New inquiry from the Catchup website { name: 'Jane Smith', email: 'jane@example.com', message: '…' }. In development it shows in the terminal that runsnpm run dev; on a host, in its logs.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 Catchup 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. Catchup’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.
Webhook payload
Section titled “Webhook payload”{ "form": "contact", "title": "New inquiry from the Catchup website", "submittedAt": "2026-10-13T10:48:23.256Z", "data": { "name": "Jane Smith", "email": "jane@example.com", "service": "Branding", "budget": "$5,000 – $10,000", "timeline": "1–2 Months", "message": "We are launching a skincare line and need a brand identity." }, "labels": { "name": "Name", "email": "Email", "service": "Services", "budget": "Budget", "timeline": "Project Timeline", "message": "Message" }}data has a key for every field ("" when left empty — only the service and the message can be), and labels the label of each, in the
order of the form.
2. Spam: the honeypot
Section titled “2. Spam: the honeypot”The 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.
3. The server action
Section titled “3. The server action”submitContact lists the fields of the form (the copy: contactForm) and calls
deliver(data, { form, title, fields, required }) from src/lib/forms/deliver.ts, which:
- drops the submission if the honeypot is filled;
- reads each listed field from the submitted data (trimmed);
- returns the error state when a required field (the name, the e-mail, the budget or the timeline) is empty;
- builds the submission (
form,title,submittedAt,data,labels) and gives it to every provider named inFORM_PROVIDER; - 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…)”-
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()}`);},}; -
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. The form
has the fields name and email, so a provider that needs a person can rely on them.
5. Change the form
Section titled “5. Change the form”- Fields and labels live in the copy:
contactForminsrc/content/pages/contact.ts.nameis the key providers receive,labelnames the field for assistive technology (and is what the notification shows),placeholderis what people read in the empty field,requiredadds the browser’s check,optionsare 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
requiredflags: the server action checks them again before it sends anything. The name, the e-mail, the budget and the timeline are required; the service and the message are not. - A new field: add it to
contactForm.fields, then place it in the form insrc/components/sections/ContactMain.tsx(<FormField {...<name>} />; the form lays out its fields by hand in a two-column grid,md:col-span-2for a full-width one). A group of choices is a<ChoiceChips>; 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 other (src/lib/actions-<form>.ts, “use server”) that callsdeliver(data, { form, title, fields, required }), and add the form name toFormKindintypes.ts.