Forms reference — Brickfolio Next.js
Brickfolio for Next.js has two forms: the contact form (“Let’s Connect”) on Home and the newsletter box (“Subscribe to Our
Newsletter”) in the footer of every page. Both post to a server action in src/lib/actions.ts.
| Form | Where | Server action | form in the payload |
Fields (name → label) |
Required |
|---|---|---|---|---|---|
| Contact | Home (#contact) |
sendContact |
contact |
First Name, Last Name, Email, Phone Number, Message (the labels are the same as the names) |
First Name, Last Name, Email, Phone Number |
| Newsletter | every page (footer) | sendNewsletter |
newsletter |
Email Email |
Email |
<Form> (design system) → server action (src/lib/actions.ts) → deliver() → provider(s) chosen in FORM_PROVIDERThe forms, their states, the e-mail check and the spam honeypot work out of the box. The button shows the visitor’s progress: “Thank you” when it worked (the fields are cleared) and “Something went wrong” when it didn’t (what was typed stays, so the visitor can try again). Where the submissions go is a setting, not code.
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. It applies to both forms. 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 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. Each submission carries the form’s name (form) and its title (title: “New message from the
contact form”, “New newsletter subscriber”).
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. Javier Martinez <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 message from the contact form { 'First Name': 'Jane', 'Last Name': 'Smith', Email: 'jane@example.com', … }. 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;First Name→FNAME,Last Name→LNAME,Phone Number→PHONEwhen filled in;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 first and last name (“New message from the contact form — Jane Smith”; the title alone for the newsletter), 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. The contact form doesn’t; the newsletter box does ask people to subscribe, so usependingorsubscribedif Mailchimp should mail them. - Merge fields:
mergeFieldsat the top ofproviders/mailchimp.tsmaps the field names to a new audience’s default tags (FNAME,LNAME,PHONE). Change it if your audience uses other tags.
Webhook payload
Section titled “Webhook payload”{ "form": "contact", "title": "New message from the contact form", "submittedAt": "2026-10-28T10:48:23.256Z", "data": { "First Name": "Jane", "Last Name": "Smith", "Email": "jane@example.com", "Phone Number": "+1 555 000 0000", "Message": "I'd like a new website for my studio." }, "labels": { "First Name": "First Name", "Last Name": "Last Name", "Email": "Email", "Phone Number": "Phone Number", "Message": "Message" }}data has a key for every field, in the order of the form, and labels the label of each. A field left empty is "".
The newsletter sends { "form": "newsletter", "title": "New newsletter subscriber", "data": { "Email": "…" } }.
2. Spam: the honeypot
Section titled “2. Spam: the honeypot”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.
3. The checks and the server action
Section titled “3. The checks and the server action”In the browser, <Form> checks the fields before sending: when a required field is empty or the e-mail isn’t an e-mail
address, the first failing field gets the focus and every failing field is marked until it is changed. Without
JavaScript the form still posts and the browser’s own check runs.
The server actions check again, since a browser can be bypassed: sendContact returns the error state when the e-mail
doesn’t look like an address, then lists the fields of the form (home.contact.fields) 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 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, "first name"), LASTNAME: valueOf(submission, "last 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 (the name is matched ignoring case, so
"email" finds Email), toLines(submission) returns "Label: value" lines for every filled field, and env(name)
reads a required variable with a clear error. Both forms always deliver an Email.
5. Change the form
Section titled “5. Change the form”- Fields and labels live in the copy:
home.contact.fieldsinsrc/content/pages/home.ts(edited incontent/pages/home.jsonin the workspace).nameis the key providers receive,labelis what people read above the field (and what the notification shows),placeholderis what the empty field shows,typepicks the control (text,email,tel,textarea),requiredmakes the field checked before sending. The button’s three texts (submit,success,error) are there too. - Required fields come from the same
requiredflags: the server action checks them again before it sends anything. - A new field: add it to
home.contact.fields;src/components/sections/Contact.tsxplaces the first two fields side by side and every other field on its own row, so it appears without a code change. - A new form: lay it out with
<Form>and<FormField>, add a server action next to the others insrc/lib/actions.ts(“use server”) that callsdeliver(data, { form, title, fields, required }), and add the form name toFormKindintypes.ts.