← NetlifyCONTENT HISTORY

Update to Netlify

Snapshot Nov 19, 2026 · 00:11 UTC · version 1.9.0

Collection source: downloaded plugin package.

WHAT CHANGED

Payment or plan references changed

Full description — Now says: setting up submission notifications or ChatGPT automations on form submission events;

Observed in published text. Live prices and checkout terms have not been verified by this change.

Save Netlify and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 7, 2026 · 00:02 UTC

After

Nov 19, 2026 · 00:11 UTC

setting up submission notifications or ChatGPT automations on form submission events;

Skill instructions

Before

Oct 7, 2026 · 00:02 UTC

or debugging missing submissions and forms that silently fail to register. <!-- Forms usage now at Forms > Usage; form detection at Forms > Form detection — UI paths updated per manifest commit a28cd46.

After

Nov 19, 2026 · 00:11 UTC

setting up submission notifications or ChatGPT automations on form submission events; or debugging missing submissions and forms that silently fail to register. **⚠️ Email recipient must be an active member of your Netlify team** (unless...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 name: netlify-forms
-description: Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; or debugging missing submissions and forms that silently fail to register.
+description: Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; setting up submission notifications or ChatGPT automations on form submission events; or debugging missing submissions and forms that silently fail to register.
 ---
 
 # Netlify Forms
@@ -130,6 +130,10 @@
 
 Set up notifications (email/webhook/Slack) in the UI: Forms > Submission notifications > **Add notification**.
 
+**⚠️ Email recipient must be an active member of your Netlify team** (unless the team is on an Enterprise or Legacy Business plan). Enforced when **creating AND editing** a notification — any other address produces a validation error and the notification is not saved. Existing notifications using a non-member address (e.g. `orders@company.com`) keep sending, but an edit that keeps that address can't be saved. Before editing, invite the address owner to the team (https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-team-members#add-new-team-members) or switch to an existing member's address. To change the recipient: Forms > Submission notifications > **Options > Edit notifications**, enter an active team member's email, save. Netlify is building email verification for recipient addresses; details will be posted at https://www.netlify.com/changelog/tag/forms/
+
+ChatGPT automations: subscribe to form submission events from ChatGPT and run automations on them (e.g. review new submissions and flag ones needing follow-up). Setup: https://docs.netlify.com/build/build-with-ai/agent-setup-guides/use-netlify-with-chatgpt/#subscribe-to-netlify-events
+
 ## Reading submissions via the API
 
 Use only documented surfaces. Do NOT invent `api.netlify.com` endpoints or read tokens from local CLI config files. Reference: https://open-api.netlify.com/#tag/submission/operation/listFormSubmissions
@@ -153,6 +157,8 @@
 - No submissions at all: confirm form detection is enabled (Forms > Form detection) and redeploy.
 - SSR/JS forms silently failing: verify the static skeleton file exists with exactly-matching field names and that AJAX targets the skeleton file, not `/`.
 - Missing old-field data: the UI shows only fields from the last deployed form version. Mark old fields `hidden` instead of removing them to keep them visible; old data remains available via `listFormSubmissions`.
+- Email notification won't save on create or edit (validation error): outside Enterprise/Legacy Business plans, the recipient isn't an active team member — use a team member's email or invite the person first. Existing notifications with such an address keep sending until edited.
+- Still stuck: Netlify Support Guide on how to debug your form — https://answers.netlify.com/t/common-issue-how-to-debug-your-form/92
 
 ## Constraints
 
@@ -161,7 +167,8 @@
 - For PII, export and delete data regularly.
 - Data is stored in Netlify's database, not accessible except via UI/API/CSV.
 
-<!-- Forms usage now at Forms > Usage; form detection at Forms > Form detection — UI paths updated per manifest commit a28cd46. -->
+<!-- Gap: ChatGPT automation event names, plan gating, and setup steps are not in this grouping; see the linked ChatGPT setup guide.
+     Gap: docs don't say whether the active-team-member recipient rule applies to webhooks, or how upcoming recipient email verification will work. -->
 
 <!-- system: agent-context/forms/system.md — human-owned, merged by ctx-gen; edit system.md, not this section -->
 # Netlify house rules (forms)
Full technical diff · 2 changed fields

changed /description

BEFORE
"Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; or debugging missing submissions and forms that silently fail to register."
AFTER
"Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; setting up submission notifications or ChatGPT automations on form submission events; or debugging missing submissions and forms that silently fail to register."

changed /skill_md_contents

BEFORE
"---\nname: netlify-forms\ndescription: Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; or debugging missing submissions and forms that silently fail to register.\n---\n\n# Netlify Forms\n\nMark a form for detection with `data-netlify=\"true\"` (or the bare `netlify` attribute — equivalent) on the `<form>` tag. Forms are detected by **parsing the final built HTML at deploy time** — there is no runtime API call or backend code. Client-side/JS-rendered/SSR forms are NOT in the built HTML and are never detected on their own; they require a static skeleton file (see below).\n\nPrerequisite: form detection must be enabled once in the Netlify UI (Forms > **Enable form detection**). Takes effect on the next deploy.\n\n## Static HTML form\n\n```html\n<form name=\"contact\" method=\"POST\" data-netlify=\"true\">\n  <p><label>Your Name: <input type=\"text\" name=\"name\" /></label></p>\n  <p><label>Your Email: <input type=\"email\" name=\"email\" /></label></p>\n  <p><label>Message: <textarea name=\"message\"></textarea></label></p>\n  <p><button type=\"submit\">Send</button></p>\n</form>\n```\n\n- `name` sets the form name in the UI and **must be unique per site**.\n- At deploy, Netlify strips the `data-netlify`/`netlify` attribute and injects `<input type=\"hidden\" name=\"form-name\" value=\"contact\" />`.\n- Add an `<input name=\"email\">` so the notification email's `Reply-to` is set to the submitter.\n\n## JS-rendered / SSR / framework forms (Next.js, Nuxt, SvelteKit, Astro, Gatsby)\n\nTwo required pieces:\n\n**1. Static skeleton file `public/__forms.html`** — a hidden copy of each form with `data-netlify=\"true\"`, a hidden `form-name` input, and every field the component submits, with names matching **exactly** (Netlify validates field names against the registered form). Without this file, submissions silently fail.\n\n```html\n<!-- public/__forms.html -->\n<form name=\"pizzaOrder\" data-netlify=\"true\" hidden>\n  <input type=\"hidden\" name=\"form-name\" value=\"pizzaOrder\" />\n  <input name=\"order\" type=\"text\" />\n</form>\n```\n\n**2. The rendered form** carries a matching hidden `form-name` input:\n\n```jsx\n<form name=\"pizzaOrder\" method=\"post\" data-netlify=\"true\" onSubmit={handleSubmit}>\n  <input type=\"hidden\" name=\"form-name\" value=\"pizzaOrder\" />\n  <input name=\"order\" type=\"text\" onChange={handleChange} />\n  <input type=\"submit\" />\n</form>\n```\n\n**⚠️ SSR POST target:** In SSR apps, `fetch(\"/\")` is intercepted by the SSR catch-all function and never reaches form processing. POST to the static skeleton file itself — `/__forms.html` — not `/` or an arbitrary path.\n\n**⚠️ Astro on-demand routes:** Routes with `export const prerender = false` or `output: \"server\"` are never scanned at build time, so their forms are never registered. Put the form on a prerendered page, or rely on the static skeleton file.\n\n**Next.js Runtime v5 (Next.js 13.5+):** extract form definitions to the static skeleton file and submit via AJAX rather than full-page navigation. See https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview#v5-breaking-changes\n\n## AJAX submission\n\n```js\nconst handleSubmit = event => {\n  event.preventDefault();\n  const formData = new FormData(event.target);\n  fetch(\"/__forms.html\", {   // static sites may POST to \"/\"; SSR must target the skeleton file\n    method: \"POST\",\n    headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n    body: new URLSearchParams(formData).toString()\n  })\n    .then(() => alert(\"Thank you for your submission\"))  // or navigate(\"/thank-you\")\n    .catch(error => alert(error));\n};\ndocument.querySelector(\"form\").addEventListener(\"submit\", handleSubmit);\n```\n\n- **Body MUST be URL-encoded. JSON is NOT supported.**\n- If the rendered form has no hidden `form-name` input, you MUST include a `form-name` field in the POST body.\n- The honeypot field name and `g-recaptcha-response` (if used) must be in the body — automatic with `FormData()`.\n\n## File uploads\n\nAdd `type=\"file\"`; optionally `enctype=\"multipart/form-data\"` on the `<form>`. For AJAX file uploads, **do NOT set a `Content-Type` header** — let the browser set it (with the multipart boundary).\n\n```js\ndocument.forms.fileForm.addEventListener(\"submit\", event => {\n  event.preventDefault();\n  fetch(\"/\", { body: new FormData(event.target), method: \"POST\" })  // no headers\n    .then(() => { /* success */ });\n});\n```\n\nLimits: one file per field (use multiple fields for multiple files) · 8 MB max request size · 30 s upload timeout · after form deletion, uploaded files stay at their direct URL for 24 h. PII uploads need extra security (Very Good Security integration).\n\n## Custom success page\n\nAdd an `action` path relative to site root, starting with `/`. **Use extensionless paths** — Netlify serves `thank-you.html` at `/thank-you`; the `.html` path returns 404.\n\n```html\n<form name=\"contact\" action=\"/thank-you\" method=\"POST\" data-netlify=\"true\"></form>\n```\n\nCustom success *alert* is only possible via AJAX (substitute the redirect with your own logic).\n\n## Spam prevention\n\nAll submissions are filtered by Akismet. Passed → **Verified submissions**; flagged → **Spam submissions**. Honeypot/reCAPTCHA failures are rejected and appear in neither list.\n\n**Honeypot:** add `netlify-honeypot=\"bot-field\"` to the `<form>` and include a CSS-hidden field of that name. Any value entered → submission quietly rejected.\n\n```html\n<form name=\"contact\" method=\"POST\" netlify-honeypot=\"bot-field\" data-netlify=\"true\">\n  <p class=\"hidden\"><label>Don’t fill this out: <input name=\"bot-field\" /></label></p>\n  <!-- real fields -->\n</form>\n```\n\n**Netlify reCAPTCHA 2:** add `data-netlify-recaptcha=\"true\"` to the `<form>` AND an empty `<div data-netlify-recaptcha=\"true\"></div>` where it renders. Only ONE Netlify-provided challenge per page — for multiple, use custom reCAPTCHA. For JS-rendered forms, also add the `div` to the static skeleton file.\n\n**Custom reCAPTCHA 2:** your own reCAPTCHA snippet + `data-netlify-recaptcha=\"true\"` on the `<form>`, plus env vars:\n- `SITE_RECAPTCHA_KEY` — site key (scopes: Builds + Runtime)\n- `SITE_RECAPTCHA_SECRET` — secret (scope: Runtime)\n\n## Email notifications & subject line\n\nDefault sender: `formresponses@netlify.com`. Set subject via a hidden `subject` input **or** the Netlify UI (Forms > Submission notifications) — **not both; the HTML value always overrides the UI.**\n\n```html\n<input type=\"hidden\" name=\"subject\" value=\"New lead from %{formName} (%{submissionId})\" />\n```\n\nVariables: `%{formName}`, `%{siteName}`, `%{submissionId}`. Forms created before **May 5, 2023** carry a `[Netlify]` subject prefix — remove it by adding the `data-remove-prefix` attribute to the `subject` input.\n\nSet up notifications (email/webhook/Slack) in the UI: Forms > Submission notifications > **Add notification**.\n\n## Reading submissions via the API\n\nUse only documented surfaces. Do NOT invent `api.netlify.com` endpoints or read tokens from local CLI config files. Reference: https://open-api.netlify.com/#tag/submission/operation/listFormSubmissions\n\n- **Page through results using the `Link` header** — code that reads only the first response silently drops the rest.\n- `listFormSubmissions` returns data from old/removed fields no longer shown in the UI.\n- Query spam with `?state=spam`.\n\n## Submission summary (field order matters)\n\nThe UI summary is derived from field **type**, not name:\n- **Title**: first non-hidden text `<input>` that isn't email-like (`type=\"email\"`, or name matching `email`/`mail`/`from`/`twitter`/`sender`); falls back to a field named `title` or `subject`.\n- **Body**: first `<textarea>`.\n\nField order in the HTML affects what appears in the summary.\n\n## Debugging missing submissions\n\n- **First suspect: Akismet false positive.** A missing legitimate submission is usually spam-flagged — check the **Spam** list (or API `?state=spam`) and mark it verified. Do NOT build a custom recovery function or disable spam filtering as a first resort.\n- Test submissions get flagged as spam: use a real email (not `test@test.com`), write full sentences, don't hammer from one IP.\n- No submissions at all: confirm form detection is enabled (Forms > Form detection) and redeploy.\n- SSR/JS forms silently failing: verify the static skeleton file exists with exactly-matching field names and that AJAX targets the skeleton file, not `/`.\n- Missing old-field data: the UI shows only fields from the last deployed form version. Mark old fields `hidden` instead of removing them to keep them visible; old data remains available via `listFormSubmissions`.\n\n## Constraints\n\n- Deleting a form is permanent: future submissions return `404`, past submissions become unavailable. Export CSV first.\n- Submitted code is sanitized (`<script>` → escaped entities).\n- For PII, export and delete data regularly.\n- Data is stored in Netlify's database, not accessible except via UI/API/CSV.\n\n<!-- Forms usage now at Forms > Usage; form detection at Forms > Form detection — UI paths updated per manifest commit a28cd46. -->\n\n<!-- system: agent-context/forms/system.md — human-owned, merged by ctx-gen; edit system.md, not this section -->\n# Netlify house rules (forms)\n\nThese are org conventions and field-learned guardrails, not docs facts — they\nare merged into the rendered skill by ctx-gen and are never generated.\nExtracted from the previous hand-written netlify-forms skill; owned by the\nskills maintainer.\n\n1. In SSR apps (Next.js, Nuxt, SvelteKit, etc.), `fetch(\"/\")` is intercepted\n   by the SSR catch-all function and never reaches Netlify's form processing.\n   POST the AJAX submission to the static skeleton file itself (e.g.\n   `/__forms.html`), not to an arbitrary path.\n2. Use only documented surfaces: do not curl `https://api.netlify.com/...`\n   with an invented endpoint shape, and do not read tokens out of local CLI\n   config files (`~/Library/Preferences/netlify/config.json`).\n3. When reading submissions via the API, page through results (`Link`\n   header); code that reads only the first response silently drops the rest.\n4. For JS-rendered and SSR forms, always create the static skeleton file\n   `public/__forms.html`: a hidden copy of each form with\n   `data-netlify=\"true\"`, a hidden `form-name` input, and every field the\n   component submits — names matching exactly (Netlify validates field names\n   against the registered form). Without this file, submissions silently fail.\n5. Astro routes rendered on demand (`export const prerender = false`, or\n   `output: \"server\"` routes) are never scanned at build time, so their forms\n   are never registered. Put the form on a prerendered page or rely on the\n   static skeleton file.\n6. A \"missing\" legitimate submission is usually an Akismet false positive:\n   check the Spam list (or the API with `?state=spam`) and mark it verified.\n   Do not build a custom recovery function or disable spam filtering as a\n   first resort.\n7. For custom success pages, use extensionless `action` paths (`/thank-you`,\n   not `/thank-you.html`) — Netlify serves `thank-you.html` at `/thank-you`\n   and the `.html` path returns 404.\n"
AFTER
"---\nname: netlify-forms\ndescription: Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; setting up submission notifications or ChatGPT automations on form submission events; or debugging missing submissions and forms that silently fail to register.\n---\n\n# Netlify Forms\n\nMark a form for detection with `data-netlify=\"true\"` (or the bare `netlify` attribute — equivalent) on the `<form>` tag. Forms are detected by **parsing the final built HTML at deploy time** — there is no runtime API call or backend code. Client-side/JS-rendered/SSR forms are NOT in the built HTML and are never detected on their own; they require a static skeleton file (see below).\n\nPrerequisite: form detection must be enabled once in the Netlify UI (Forms > **Enable form detection**). Takes effect on the next deploy.\n\n## Static HTML form\n\n```html\n<form name=\"contact\" method=\"POST\" data-netlify=\"true\">\n  <p><label>Your Name: <input type=\"text\" name=\"name\" /></label></p>\n  <p><label>Your Email: <input type=\"email\" name=\"email\" /></label></p>\n  <p><label>Message: <textarea name=\"message\"></textarea></label></p>\n  <p><button type=\"submit\">Send</button></p>\n</form>\n```\n\n- `name` sets the form name in the UI and **must be unique per site**.\n- At deploy, Netlify strips the `data-netlify`/`netlify` attribute and injects `<input type=\"hidden\" name=\"form-name\" value=\"contact\" />`.\n- Add an `<input name=\"email\">` so the notification email's `Reply-to` is set to the submitter.\n\n## JS-rendered / SSR / framework forms (Next.js, Nuxt, SvelteKit, Astro, Gatsby)\n\nTwo required pieces:\n\n**1. Static skeleton file `public/__forms.html`** — a hidden copy of each form with `data-netlify=\"true\"`, a hidden `form-name` input, and every field the component submits, with names matching **exactly** (Netlify validates field names against the registered form). Without this file, submissions silently fail.\n\n```html\n<!-- public/__forms.html -->\n<form name=\"pizzaOrder\" data-netlify=\"true\" hidden>\n  <input type=\"hidden\" name=\"form-name\" value=\"pizzaOrder\" />\n  <input name=\"order\" type=\"text\" />\n</form>\n```\n\n**2. The rendered form** carries a matching hidden `form-name` input:\n\n```jsx\n<form name=\"pizzaOrder\" method=\"post\" data-netlify=\"true\" onSubmit={handleSubmit}>\n  <input type=\"hidden\" name=\"form-name\" value=\"pizzaOrder\" />\n  <input name=\"order\" type=\"text\" onChange={handleChange} />\n  <input type=\"submit\" />\n</form>\n```\n\n**⚠️ SSR POST target:** In SSR apps, `fetch(\"/\")` is intercepted by the SSR catch-all function and never reaches form processing. POST to the static skeleton file itself — `/__forms.html` — not `/` or an arbitrary path.\n\n**⚠️ Astro on-demand routes:** Routes with `export const prerender = false` or `output: \"server\"` are never scanned at build time, so their forms are never registered. Put the form on a prerendered page, or rely on the static skeleton file.\n\n**Next.js Runtime v5 (Next.js 13.5+):** extract form definitions to the static skeleton file and submit via AJAX rather than full-page navigation. See https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview#v5-breaking-changes\n\n## AJAX submission\n\n```js\nconst handleSubmit = event => {\n  event.preventDefault();\n  const formData = new FormData(event.target);\n  fetch(\"/__forms.html\", {   // static sites may POST to \"/\"; SSR must target the skeleton file\n    method: \"POST\",\n    headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n    body: new URLSearchParams(formData).toString()\n  })\n    .then(() => alert(\"Thank you for your submission\"))  // or navigate(\"/thank-you\")\n    .catch(error => alert(error));\n};\ndocument.querySelector(\"form\").addEventListener(\"submit\", handleSubmit);\n```\n\n- **Body MUST be URL-encoded. JSON is NOT supported.**\n- If the rendered form has no hidden `form-name` input, you MUST include a `form-name` field in the POST body.\n- The honeypot field name and `g-recaptcha-response` (if used) must be in the body — automatic with `FormData()`.\n\n## File uploads\n\nAdd `type=\"file\"`; optionally `enctype=\"multipart/form-data\"` on the `<form>`. For AJAX file uploads, **do NOT set a `Content-Type` header** — let the browser set it (with the multipart boundary).\n\n```js\ndocument.forms.fileForm.addEventListener(\"submit\", event => {\n  event.preventDefault();\n  fetch(\"/\", { body: new FormData(event.target), method: \"POST\" })  // no headers\n    .then(() => { /* success */ });\n});\n```\n\nLimits: one file per field (use multiple fields for multiple files) · 8 MB max request size · 30 s upload timeout · after form deletion, uploaded files stay at their direct URL for 24 h. PII uploads need extra security (Very Good Security integration).\n\n## Custom success page\n\nAdd an `action` path relative to site root, starting with `/`. **Use extensionless paths** — Netlify serves `thank-you.html` at `/thank-you`; the `.html` path returns 404.\n\n```html\n<form name=\"contact\" action=\"/thank-you\" method=\"POST\" data-netlify=\"true\"></form>\n```\n\nCustom success *alert* is only possible via AJAX (substitute the redirect with your own logic).\n\n## Spam prevention\n\nAll submissions are filtered by Akismet. Passed → **Verified submissions**; flagged → **Spam submissions**. Honeypot/reCAPTCHA failures are rejected and appear in neither list.\n\n**Honeypot:** add `netlify-honeypot=\"bot-field\"` to the `<form>` and include a CSS-hidden field of that name. Any value entered → submission quietly rejected.\n\n```html\n<form name=\"contact\" method=\"POST\" netlify-honeypot=\"bot-field\" data-netlify=\"true\">\n  <p class=\"hidden\"><label>Don’t fill this out: <input name=\"bot-field\" /></label></p>\n  <!-- real fields -->\n</form>\n```\n\n**Netlify reCAPTCHA 2:** add `data-netlify-recaptcha=\"true\"` to the `<form>` AND an empty `<div data-netlify-recaptcha=\"true\"></div>` where it renders. Only ONE Netlify-provided challenge per page — for multiple, use custom reCAPTCHA. For JS-rendered forms, also add the `div` to the static skeleton file.\n\n**Custom reCAPTCHA 2:** your own reCAPTCHA snippet + `data-netlify-recaptcha=\"true\"` on the `<form>`, plus env vars:\n- `SITE_RECAPTCHA_KEY` — site key (scopes: Builds + Runtime)\n- `SITE_RECAPTCHA_SECRET` — secret (scope: Runtime)\n\n## Email notifications & subject line\n\nDefault sender: `formresponses@netlify.com`. Set subject via a hidden `subject` input **or** the Netlify UI (Forms > Submission notifications) — **not both; the HTML value always overrides the UI.**\n\n```html\n<input type=\"hidden\" name=\"subject\" value=\"New lead from %{formName} (%{submissionId})\" />\n```\n\nVariables: `%{formName}`, `%{siteName}`, `%{submissionId}`. Forms created before **May 5, 2023** carry a `[Netlify]` subject prefix — remove it by adding the `data-remove-prefix` attribute to the `subject` input.\n\nSet up notifications (email/webhook/Slack) in the UI: Forms > Submission notifications > **Add notification**.\n\n**⚠️ Email recipient must be an active member of your Netlify team** (unless the team is on an Enterprise or Legacy Business plan). Enforced when **creating AND editing** a notification — any other address produces a validation error and the notification is not saved. Existing notifications using a non-member address (e.g. `orders@company.com`) keep sending, but an edit that keeps that address can't be saved. Before editing, invite the address owner to the team (https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-team-members#add-new-team-members) or switch to an existing member's address. To change the recipient: Forms > Submission notifications > **Options > Edit notifications**, enter an active team member's email, save. Netlify is building email verification for recipient addresses; details will be posted at https://www.netlify.com/changelog/tag/forms/\n\nChatGPT automations: subscribe to form submission events from ChatGPT and run automations on them (e.g. review new submissions and flag ones needing follow-up). Setup: https://docs.netlify.com/build/build-with-ai/agent-setup-guides/use-netlify-with-chatgpt/#subscribe-to-netlify-events\n\n## Reading submissions via the API\n\nUse only documented surfaces. Do NOT invent `api.netlify.com` endpoints or read tokens from local CLI config files. Reference: https://open-api.netlify.com/#tag/submission/operation/listFormSubmissions\n\n- **Page through results using the `Link` header** — code that reads only the first response silently drops the rest.\n- `listFormSubmissions` returns data from old/removed fields no longer shown in the UI.\n- Query spam with `?state=spam`.\n\n## Submission summary (field order matters)\n\nThe UI summary is derived from field **type**, not name:\n- **Title**: first non-hidden text `<input>` that isn't email-like (`type=\"email\"`, or name matching `email`/`mail`/`from`/`twitter`/`sender`); falls back to a field named `title` or `subject`.\n- **Body**: first `<textarea>`.\n\nField order in the HTML affects what appears in the summary.\n\n## Debugging missing submissions\n\n- **First suspect: Akismet false positive.** A missing legitimate submission is usually spam-flagged — check the **Spam** list (or API `?state=spam`) and mark it verified. Do NOT build a custom recovery function or disable spam filtering as a first resort.\n- Test submissions get flagged as spam: use a real email (not `test@test.com`), write full sentences, don't hammer from one IP.\n- No submissions at all: confirm form detection is enabled (Forms > Form detection) and redeploy.\n- SSR/JS forms silently failing: verify the static skeleton file exists with exactly-matching field names and that AJAX targets the skeleton file, not `/`.\n- Missing old-field data: the UI shows only fields from the last deployed form version. Mark old fields `hidden` instead of removing them to keep them visible; old data remains available via `listFormSubmissions`.\n- Email notification won't save on create or edit (validation error): outside Enterprise/Legacy Business plans, the recipient isn't an active team member — use a team member's email or invite the person first. Existing notifications with such an address keep sending until edited.\n- Still stuck: Netlify Support Guide on how to debug your form — https://answers.netlify.com/t/common-issue-how-to-debug-your-form/92\n\n## Constraints\n\n- Deleting a form is permanent: future submissions return `404`, past submissions become unavailable. Export CSV first.\n- Submitted code is sanitized (`<script>` → escaped entities).\n- For PII, export and delete data regularly.\n- Data is stored in Netlify's database, not accessible except via UI/API/CSV.\n\n<!-- Gap: ChatGPT automation event names, plan gating, and setup steps are not in this grouping; see the linked ChatGPT setup guide.\n     Gap: docs don't say whether the active-team-member recipient rule applies to webhooks, or how upcoming recipient email verification will work. -->\n\n<!-- system: agent-context/forms/system.md — human-owned, merged by ctx-gen; edit system.md, not this section -->\n# Netlify house rules (forms)\n\nThese are org conventions and field-learned guardrails, not docs facts — they\nare merged into the rendered skill by ctx-gen and are never generated.\nExtracted from the previous hand-written netlify-forms skill; owned by the\nskills maintainer.\n\n1. In SSR apps (Next.js, Nuxt, SvelteKit, etc.), `fetch(\"/\")` is intercepted\n   by the SSR catch-all function and never reaches Netlify's form processing.\n   POST the AJAX submission to the static skeleton file itself (e.g.\n   `/__forms.html`), not to an arbitrary path.\n2. Use only documented surfaces: do not curl `https://api.netlify.com/...`\n   with an invented endpoint shape, and do not read tokens out of local CLI\n   config files (`~/Library/Preferences/netlify/config.json`).\n3. When reading submissions via the API, page through results (`Link`\n   header); code that reads only the first response silently drops the rest.\n4. For JS-rendered and SSR forms, always create the static skeleton file\n   `public/__forms.html`: a hidden copy of each form with\n   `data-netlify=\"true\"`, a hidden `form-name` input, and every field the\n   component submits — names matching exactly (Netlify validates field names\n   against the registered form). Without this file, submissions silently fail.\n5. Astro routes rendered on demand (`export const prerender = false`, or\n   `output: \"server\"` routes) are never scanned at build time, so their forms\n   are never registered. Put the form on a prerendered page or rely on the\n   static skeleton file.\n6. A \"missing\" legitimate submission is usually an Akismet false positive:\n   check the Spam list (or the API with `?state=spam`) and mark it verified.\n   Do not build a custom recovery function or disable spam filtering as a\n   first resort.\n7. For custom success pages, use extensionless `action` paths (`/thank-you`,\n   not `/thank-you.html`) — Netlify serves `thank-you.html` at `/thank-you`\n   and the `.html` path returns 404.\n"
Full snapshot data
{
  "description": "Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; setting up submission notifications or ChatGPT automations on form submission events; or debugging missing submissions and forms that silently fail to register.",
  "included_files": [],
  "name": "netlify-forms",
  "skill_md_contents": "---\nname: netlify-forms\ndescription: Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; setting up submission notifications or ChatGPT automations on form submission events; or debugging missing submissions and forms that silently fail to register.\n---\n\n# Netlify Forms\n\nMark a form for detection with `data-netlify=\"true\"` (or the bare `netlify` attribute — equivalent) on the `<form>` tag. Forms are detected by **parsing the final built HTML at deploy time** — there is no runtime API call or backend code. Client-side/JS-rendered/SSR forms are NOT in the built HTML and are never detected on their own; they require a static skeleton file (see below).\n\nPrerequisite: form detection must be enabled once in the Netlify UI (Forms > **Enable form detection**). Takes effect on the next deploy.\n\n## Static HTML form\n\n```html\n<form name=\"contact\" method=\"POST\" data-netlify=\"true\">\n  <p><label>Your Name: <input type=\"text\" name=\"name\" /></label></p>\n  <p><label>Your Email: <input type=\"email\" name=\"email\" /></label></p>\n  <p><label>Message: <textarea name=\"message\"></textarea></label></p>\n  <p><button type=\"submit\">Send</button></p>\n</form>\n```\n\n- `name` sets the form name in the UI and **must be unique per site**.\n- At deploy, Netlify strips the `data-netlify`/`netlify` attribute and injects `<input type=\"hidden\" name=\"form-name\" value=\"contact\" />`.\n- Add an `<input name=\"email\">` so the notification email's `Reply-to` is set to the submitter.\n\n## JS-rendered / SSR / framework forms (Next.js, Nuxt, SvelteKit, Astro, Gatsby)\n\nTwo required pieces:\n\n**1. Static skeleton file `public/__forms.html`** — a hidden copy of each form with `data-netlify=\"true\"`, a hidden `form-name` input, and every field the component submits, with names matching **exactly** (Netlify validates field names against the registered form). Without this file, submissions silently fail.\n\n```html\n<!-- public/__forms.html -->\n<form name=\"pizzaOrder\" data-netlify=\"true\" hidden>\n  <input type=\"hidden\" name=\"form-name\" value=\"pizzaOrder\" />\n  <input name=\"order\" type=\"text\" />\n</form>\n```\n\n**2. The rendered form** carries a matching hidden `form-name` input:\n\n```jsx\n<form name=\"pizzaOrder\" method=\"post\" data-netlify=\"true\" onSubmit={handleSubmit}>\n  <input type=\"hidden\" name=\"form-name\" value=\"pizzaOrder\" />\n  <input name=\"order\" type=\"text\" onChange={handleChange} />\n  <input type=\"submit\" />\n</form>\n```\n\n**⚠️ SSR POST target:** In SSR apps, `fetch(\"/\")` is intercepted by the SSR catch-all function and never reaches form processing. POST to the static skeleton file itself — `/__forms.html` — not `/` or an arbitrary path.\n\n**⚠️ Astro on-demand routes:** Routes with `export const prerender = false` or `output: \"server\"` are never scanned at build time, so their forms are never registered. Put the form on a prerendered page, or rely on the static skeleton file.\n\n**Next.js Runtime v5 (Next.js 13.5+):** extract form definitions to the static skeleton file and submit via AJAX rather than full-page navigation. See https://docs.netlify.com/build/frameworks/framework-setup-guides/nextjs/overview#v5-breaking-changes\n\n## AJAX submission\n\n```js\nconst handleSubmit = event => {\n  event.preventDefault();\n  const formData = new FormData(event.target);\n  fetch(\"/__forms.html\", {   // static sites may POST to \"/\"; SSR must target the skeleton file\n    method: \"POST\",\n    headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n    body: new URLSearchParams(formData).toString()\n  })\n    .then(() => alert(\"Thank you for your submission\"))  // or navigate(\"/thank-you\")\n    .catch(error => alert(error));\n};\ndocument.querySelector(\"form\").addEventListener(\"submit\", handleSubmit);\n```\n\n- **Body MUST be URL-encoded. JSON is NOT supported.**\n- If the rendered form has no hidden `form-name` input, you MUST include a `form-name` field in the POST body.\n- The honeypot field name and `g-recaptcha-response` (if used) must be in the body — automatic with `FormData()`.\n\n## File uploads\n\nAdd `type=\"file\"`; optionally `enctype=\"multipart/form-data\"` on the `<form>`. For AJAX file uploads, **do NOT set a `Content-Type` header** — let the browser set it (with the multipart boundary).\n\n```js\ndocument.forms.fileForm.addEventListener(\"submit\", event => {\n  event.preventDefault();\n  fetch(\"/\", { body: new FormData(event.target), method: \"POST\" })  // no headers\n    .then(() => { /* success */ });\n});\n```\n\nLimits: one file per field (use multiple fields for multiple files) · 8 MB max request size · 30 s upload timeout · after form deletion, uploaded files stay at their direct URL for 24 h. PII uploads need extra security (Very Good Security integration).\n\n## Custom success page\n\nAdd an `action` path relative to site root, starting with `/`. **Use extensionless paths** — Netlify serves `thank-you.html` at `/thank-you`; the `.html` path returns 404.\n\n```html\n<form name=\"contact\" action=\"/thank-you\" method=\"POST\" data-netlify=\"true\"></form>\n```\n\nCustom success *alert* is only possible via AJAX (substitute the redirect with your own logic).\n\n## Spam prevention\n\nAll submissions are filtered by Akismet. Passed → **Verified submissions**; flagged → **Spam submissions**. Honeypot/reCAPTCHA failures are rejected and appear in neither list.\n\n**Honeypot:** add `netlify-honeypot=\"bot-field\"` to the `<form>` and include a CSS-hidden field of that name. Any value entered → submission quietly rejected.\n\n```html\n<form name=\"contact\" method=\"POST\" netlify-honeypot=\"bot-field\" data-netlify=\"true\">\n  <p class=\"hidden\"><label>Don’t fill this out: <input name=\"bot-field\" /></label></p>\n  <!-- real fields -->\n</form>\n```\n\n**Netlify reCAPTCHA 2:** add `data-netlify-recaptcha=\"true\"` to the `<form>` AND an empty `<div data-netlify-recaptcha=\"true\"></div>` where it renders. Only ONE Netlify-provided challenge per page — for multiple, use custom reCAPTCHA. For JS-rendered forms, also add the `div` to the static skeleton file.\n\n**Custom reCAPTCHA 2:** your own reCAPTCHA snippet + `data-netlify-recaptcha=\"true\"` on the `<form>`, plus env vars:\n- `SITE_RECAPTCHA_KEY` — site key (scopes: Builds + Runtime)\n- `SITE_RECAPTCHA_SECRET` — secret (scope: Runtime)\n\n## Email notifications & subject line\n\nDefault sender: `formresponses@netlify.com`. Set subject via a hidden `subject` input **or** the Netlify UI (Forms > Submission notifications) — **not both; the HTML value always overrides the UI.**\n\n```html\n<input type=\"hidden\" name=\"subject\" value=\"New lead from %{formName} (%{submissionId})\" />\n```\n\nVariables: `%{formName}`, `%{siteName}`, `%{submissionId}`. Forms created before **May 5, 2023** carry a `[Netlify]` subject prefix — remove it by adding the `data-remove-prefix` attribute to the `subject` input.\n\nSet up notifications (email/webhook/Slack) in the UI: Forms > Submission notifications > **Add notification**.\n\n**⚠️ Email recipient must be an active member of your Netlify team** (unless the team is on an Enterprise or Legacy Business plan). Enforced when **creating AND editing** a notification — any other address produces a validation error and the notification is not saved. Existing notifications using a non-member address (e.g. `orders@company.com`) keep sending, but an edit that keeps that address can't be saved. Before editing, invite the address owner to the team (https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-team-members#add-new-team-members) or switch to an existing member's address. To change the recipient: Forms > Submission notifications > **Options > Edit notifications**, enter an active team member's email, save. Netlify is building email verification for recipient addresses; details will be posted at https://www.netlify.com/changelog/tag/forms/\n\nChatGPT automations: subscribe to form submission events from ChatGPT and run automations on them (e.g. review new submissions and flag ones needing follow-up). Setup: https://docs.netlify.com/build/build-with-ai/agent-setup-guides/use-netlify-with-chatgpt/#subscribe-to-netlify-events\n\n## Reading submissions via the API\n\nUse only documented surfaces. Do NOT invent `api.netlify.com` endpoints or read tokens from local CLI config files. Reference: https://open-api.netlify.com/#tag/submission/operation/listFormSubmissions\n\n- **Page through results using the `Link` header** — code that reads only the first response silently drops the rest.\n- `listFormSubmissions` returns data from old/removed fields no longer shown in the UI.\n- Query spam with `?state=spam`.\n\n## Submission summary (field order matters)\n\nThe UI summary is derived from field **type**, not name:\n- **Title**: first non-hidden text `<input>` that isn't email-like (`type=\"email\"`, or name matching `email`/`mail`/`from`/`twitter`/`sender`); falls back to a field named `title` or `subject`.\n- **Body**: first `<textarea>`.\n\nField order in the HTML affects what appears in the summary.\n\n## Debugging missing submissions\n\n- **First suspect: Akismet false positive.** A missing legitimate submission is usually spam-flagged — check the **Spam** list (or API `?state=spam`) and mark it verified. Do NOT build a custom recovery function or disable spam filtering as a first resort.\n- Test submissions get flagged as spam: use a real email (not `test@test.com`), write full sentences, don't hammer from one IP.\n- No submissions at all: confirm form detection is enabled (Forms > Form detection) and redeploy.\n- SSR/JS forms silently failing: verify the static skeleton file exists with exactly-matching field names and that AJAX targets the skeleton file, not `/`.\n- Missing old-field data: the UI shows only fields from the last deployed form version. Mark old fields `hidden` instead of removing them to keep them visible; old data remains available via `listFormSubmissions`.\n- Email notification won't save on create or edit (validation error): outside Enterprise/Legacy Business plans, the recipient isn't an active team member — use a team member's email or invite the person first. Existing notifications with such an address keep sending until edited.\n- Still stuck: Netlify Support Guide on how to debug your form — https://answers.netlify.com/t/common-issue-how-to-debug-your-form/92\n\n## Constraints\n\n- Deleting a form is permanent: future submissions return `404`, past submissions become unavailable. Export CSV first.\n- Submitted code is sanitized (`<script>` → escaped entities).\n- For PII, export and delete data regularly.\n- Data is stored in Netlify's database, not accessible except via UI/API/CSV.\n\n<!-- Gap: ChatGPT automation event names, plan gating, and setup steps are not in this grouping; see the linked ChatGPT setup guide.\n     Gap: docs don't say whether the active-team-member recipient rule applies to webhooks, or how upcoming recipient email verification will work. -->\n\n<!-- system: agent-context/forms/system.md — human-owned, merged by ctx-gen; edit system.md, not this section -->\n# Netlify house rules (forms)\n\nThese are org conventions and field-learned guardrails, not docs facts — they\nare merged into the rendered skill by ctx-gen and are never generated.\nExtracted from the previous hand-written netlify-forms skill; owned by the\nskills maintainer.\n\n1. In SSR apps (Next.js, Nuxt, SvelteKit, etc.), `fetch(\"/\")` is intercepted\n   by the SSR catch-all function and never reaches Netlify's form processing.\n   POST the AJAX submission to the static skeleton file itself (e.g.\n   `/__forms.html`), not to an arbitrary path.\n2. Use only documented surfaces: do not curl `https://api.netlify.com/...`\n   with an invented endpoint shape, and do not read tokens out of local CLI\n   config files (`~/Library/Preferences/netlify/config.json`).\n3. When reading submissions via the API, page through results (`Link`\n   header); code that reads only the first response silently drops the rest.\n4. For JS-rendered and SSR forms, always create the static skeleton file\n   `public/__forms.html`: a hidden copy of each form with\n   `data-netlify=\"true\"`, a hidden `form-name` input, and every field the\n   component submits — names matching exactly (Netlify validates field names\n   against the registered form). Without this file, submissions silently fail.\n5. Astro routes rendered on demand (`export const prerender = false`, or\n   `output: \"server\"` routes) are never scanned at build time, so their forms\n   are never registered. Put the form on a prerendered page or rely on the\n   static skeleton file.\n6. A \"missing\" legitimate submission is usually an Akismet false positive:\n   check the Spam list (or the API with `?state=spam`) and mark it verified.\n   Do not build a custom recovery function or disable spam filtering as a\n   first resort.\n7. For custom success pages, use extensionless `action` paths (`/thank-you`,\n   not `/thank-you.html`) — Netlify serves `thank-you.html` at `/thank-you`\n   and the `.html` path returns 404.\n"
}

SHA-256 of public snapshot: 2459771237b4c48b783a7ccb8192e8c5d07d479de0e47cf083dfbcbe8f5a900c