Netlify let ChatGPT subscribe to deploy, build-failure and form events on Oct. 7, so automations run when something happens instead of on a schedule.
ChatGPT can now react to Netlify site events as they happen. Netlify said in an Oct. 7, 2026 changelog entry that users can set up ChatGPT automations triggered by those events. ChatGPT can “act as soon as something happens” instead of waiting for someone to check the dashboard or an email.
What changed #
Netlify listed three events: a deploy succeeded, a build failed, and a form submission came in. The entry points to its deploy events documentation for more.
Setup is conversational. A user connects Netlify in ChatGPT, then asks ChatGPT to subscribe to the events wanted for a project. Netlify said the events work alongside its ChatGPT plugin and its MCP server.
Netlify’s two examples: reviewing new form submissions and flagging the ones that need follow-up, and summarizing what changed when a production deploy succeeds. The automations live in ChatGPT. Netlify said they can be described in plain language and changed as a workflow changes.
Key Takeaways #
- Deploy success, build failure and form submission events can now start ChatGPT automations.
- Subscriptions are set up from inside ChatGPT after connecting Netlify.
- It builds on Netlify’s existing ChatGPT plugin and MCP server.
The Take #
With the plugin and MCP server, a person asks and the agent looks. Events reverse that. The agent gets pushed a signal and does something with it. That is how most teams already use webhooks and Slack alerts, with ChatGPT standing in for the person reading them.
The build-failure event is the obvious one to try first. A summary of why a build broke, delivered when it breaks, is worth more than a red badge nobody opens. Form submissions are the riskier fit. They carry visitor data, so check privacy rules before wiring them up.