--- title: "Netlify Integration" description: "Manage Netlify sites, deploys, environment variables, forms, and DNS from your flows over the Netlify API. Trigger builds, roll back to a known-good deploy, and sync configuration." url: https://flowrunner.ai/integrations/netlify date_modified: 2026-08-01T02:40:32-07:00 --- # Netlify [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Manage Netlify sites, deploys, environment variables, forms, and DNS from your flows over the Netlify API. Trigger builds, roll back to a known-good deploy, and sync configuration. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 25 actions · API key · available [Netlify website](https://netlify.com/) · [Platform Documentation](https://open-api.netlify.com/) · Capability data verified 2026-08-12 1. A release flow signals a new build is ready 2. Agent resolves the site to deploy 3. Agent calls Trigger Build to deploy from the connected repository 4. Agent polls Get Deploy until the deploy reaches the ready state 5. Agent posts the deploy state and URL to the team channel 6. An engineer confirms before the agent restores a previous deploy during a rollback ## What This Integration Enables FlowRunner agents use Netlify to run deploys and site operations from inside a larger flow. An agent can trigger a build from a connected Git repository and monitor its state, roll back to a known-good deploy when a bad release is detected, and sync environment variables across sites and deploy contexts. It can collect and process Netlify Forms submissions, then archive or clean them up, and manage DNS zones and records programmatically. Netlify deploys are digest-based, so the agent deploys from the repository or restores a previous deploy rather than uploading files. What it does not do on its own is restore a previous deploy, because a rollback changes the live site. That confirmation stays with a person. ### Without FlowRunner **Manual deploys**: An engineer opens Netlify and triggers each deploy by hand **Guesswork rollbacks**: Finding the last good deploy means scrolling the deploy list under pressure **Submissions piling up**: Form submissions sit unprocessed until someone checks the dashboard ### With FlowRunner **Triggered deploys**: The agent deploys from the repository and confirms it reaches ready **Confirmed rollbacks**: The agent surfaces the last good deploy and restores it on approval **Submissions routed**: The agent pulls new form submissions and hands them to the next step ## Use Case Scenarios ### Deploy on release A release flow signals a new build. The agent calls Trigger Build to deploy the site from the connected repository, then polls Get Deploy until it reaches the ready state, and posts the deploy URL to the team channel. The site ships as part of the flow, and the team sees the confirmed deploy instead of watching the dashboard. ### Form submissions into the operation The agent calls List Form Submissions and finds new entries. It notifies the team of each one and hands the payload to the next step, then calls Delete Form Submission to clear the entries it has processed. Submissions move into the operation instead of collecting in the Netlify UI. ### Rollback with a confirmation gate A monitoring flow detects a bad release. The agent calls List Deploys to find the last deploy that reached ready cleanly, and posts it to the incident channel with the current broken deploy for comparison. It does not roll back on its own. Only after an engineer confirms does the agent call Restore Deploy to republish the good build. ## Human-in-Loop Highlight The human-in-loop moment in Netlify is the rollback gate. Triggering a build, watching a deploy reach ready, and clearing processed form submissions are all safe to automate, so the agent runs them by rule. Restoring a previous deploy is different, because it changes what every visitor sees right now. When a monitoring flow detects a bad release, the agent finds the last good deploy with List Deploys and posts it to the incident channel: "Current deploy is erroring. The last deploy that reached ready cleanly is #341 from 40 minutes ago. Restore it?" An engineer confirms. Only then does the agent call Restore Deploy. The agent ships deploys and gathers evidence on its own. A person owns the rollback that changes the live site. Agent processes routinely Detects bad release Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 25 actions ### Sites 5 - **Create Site** Create a new site. - **Delete Site** Delete a site. - **Get Site** Retrieve a site's details. - **List Sites** List the sites in the account. - **Update Site** Update a site's settings. ### Deploys 7 - **Cancel Deploy** Cancel an in-progress deploy. - **Get Deploy** Retrieve a deploy's details and state. Used to confirm a build reaches ready. - **List Deploys** List a site's deploys. Used to find the last good deploy for a rollback. - **Lock Deploy** Lock the published deploy so new builds do not auto-publish. - **Restore Deploy** Republish a previous deploy. Used to roll back a bad release, behind a human confirmation. - **Trigger Build** Start a new build and deploy from the connected repository. - **Unlock Deploy** Unlock a locked published deploy. ### Environment Variables 5 - **Create Environment Variable** Create an account-scoped environment variable. Requires an Account ID. - **Delete Environment Variable** Delete an environment variable. - **Get Environment Variable** Retrieve an environment variable. - **List Environment Variables** List the account's environment variables. - **Set Environment Variable Value** Set an environment variable's value for a deploy context. ### Forms 3 - **Delete Form Submission** Delete a form submission. Used to clear processed entries. - **List Form Submissions** List the submissions to a Netlify form. - **List Forms** List the forms on a site. ### DNS 4 - **Create DNS Record** Create a DNS record in a Netlify DNS zone. - **Delete DNS Record** Delete a DNS record. - **List DNS Records** List the records in a DNS zone. - **List DNS Zones** List the DNS zones in the account. ### Account 1 - **List Accounts** List the accounts the token can access. Used to discover an Account ID. ## Frequently Asked Questions ### What can FlowRunner do with Netlify? FlowRunner agents can run List Sites, Get Site, and Create Site in Netlify, plus 22 more actions. ### Does connecting Netlify to FlowRunner require OAuth? No. Netlify connects to FlowRunner with an API key, no OAuth flow required. ### Can Netlify trigger a FlowRunner workflow automatically? Netlify doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Netlify?** This integration exposes Netlify to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/netlify. Site index: https://flowrunner.ai/llms.txt