Skip to content
Sign inJoin waitlist

Forms reference — Denzel Astro

Denzel for Astro has one form: the newsletter box in the footer of every page (NewsletterForm.astro, form newsletter). It works in one of three ways, chosen with environment variables (copy .env.example to .env, or set them in your host’s dashboard); no code changes.

Form Where form in the payload Fields (name → label) Required
Newsletter every page (footer) newsletter email Email email (must look like an e-mail address)
Mode Set Hosting Where submissions go
Demo (default) nothing any static host Nowhere: the button shows “Thank you!” and the fields are logged 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 button (“…” while sending, then “Thank you!” or “Something went wrong”), clears the field once the answer is in and drops spam caught by the hidden honeypot field (fax). The PUBLIC_ variables are read when the site is built: rebuild (or restart npm run dev) after changing them.

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

formEndpoint("newsletter") in src/lib/forms/endpoint.ts decides where the form posts: /api/forms/<form> in server mode, else PUBLIC_FORM_ENDPOINT, else nothing (demo mode). The browser part is src/design-system/scripts/newsletter.ts; the form’s definition (fields, required, e-mail check) is src/lib/forms/definitions.ts.

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; the service must answer with a 2xx status, anything else shows “Something went wrong”.

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

Fields sent: email, plus form (newsletter) and subject.

  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 form then posts to POST /api/forms/newsletter (src/lib/forms/route.ts, added by src/integrations/forms.ts; every other page stays prerendered). Without an adapter the build stops with NoAdapterInstalled. Astro rejects cross-site posts to the route. The route answers JSON: 200 { "status": "success" }, or 500 { "status": "error" } (404 unknown form, 400 not form data).

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, your own API. FORM_WEBHOOK_URL, optional FORM_WEBHOOK_SECRET (sent as Authorization: Bearer …)
mailchimp Subscriber added or updated in an audience and tagged with the form. MAILCHIMP_API_KEY, MAILCHIMP_AUDIENCE_ID, optional MAILCHIMP_STATUS
resend Emailed to you. RESEND_API_KEY, FORM_EMAIL_TO, FORM_EMAIL_FROM

Use several with a comma (FORM_PROVIDER=resend,mailchimp). If one fails the visitor sees the error state and the reason is logged on the server. A provider that needs a variable and doesn’t find it stops the submission with Missing environment variable <NAME> (see .env.example). Add your own provider in src/lib/forms/providers/index.ts.