Mattering Automations Netlify integration
Connect Netlify to Mattering Automations: sites, deploys and rollbacks, builds, build hooks, environment variables, DNS, and form submissions as workflow steps, authenticated with a Netlify Personal Access Token.
The Mattering Automations Netlify integration adds Netlify to your automation canvas: list and inspect sites and deploys, restore any past deploy as the live site or roll back to the previous one, start and cancel builds, lock production for a change freeze, create and trigger build hooks, manage environment variables with per-context values, manage DNS records in existing zones, and read or clean up Netlify Forms submissions.
Setup takes a few minutes: create a Personal Access Token in your Netlify user settings, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.
Two things this guide is deliberately blunt about. Netlify: Start Build and Netlify: Trigger Build Hook start real CI builds that consume the account's build minutes, and past the plan's included allowance Netlify charges for extra minutes. And reading environment variables copies their unencrypted values into automation execution records; Netlify's secret variables, which are write-only after creation, are the real fix for anything sensitive.
Before you start
- A Netlify account with at least one site. Nearly every node is site-scoped and takes a site id from Netlify: List Sites.
- Access to your Netlify user settings to create a Personal Access Token under Applications.
- A Mattering workspace with access to the Automations app.
- Only for the nodes that need them: a domain on Netlify DNS for the DNS nodes, and Netlify Forms receiving submissions for the form nodes.
Create a Netlify Personal Access Token
Mattering authenticates to Netlify with a Personal Access Token, sent as a bearer credential on every request. Personal Access Tokens are Netlify's documented path for automating your own team, with no OAuth flow involved; you choose the token's expiration date when creating it.
Connect Netlify to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Netlify section should list the query and action nodes. Drop Netlify: Get Current User onto the canvas and run a test step. It takes no parameters and returns the account the token belongs to; a successful response proves the credential works. Then run Netlify: List Sites and note the site ids, because nearly every other node wants one.
To confirm the deploy surface, run Netlify: List Site Deploys for a site and Netlify: Get Deploy on one of the returned ids: both are read-only. Leave the environment variable reads out of casual verification, since their responses contain unencrypted values that land in execution records, and nothing in this verify path touches the five destructive delete nodes or starts a build.
Node reference
39 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 21
Netlify: Get Account Build Status
netlify_get_account_build_status
Show the team's current build queue (active and enqueued builds) and build-minutes usage for the billing period. Check this before start-build automations to avoid burning through the plan's included minutes.
Netlify: Get Build
netlify_get_build
Fetch one build by id: done flag, error message, and the deploy_id it produced. Poll after Netlify: Start Build to follow progress.
Netlify: Get Build Hook
netlify_get_build_hook
Fetch one build hook by id: title, target branch, and the trigger URL.
Netlify: Get Current User
netlify_get_current_user
Return the account of the user the access token belongs to: name, email, site count, last login. Takes no parameters, so it doubles as the credential health check for the connector.
Netlify: Get DNS Record
netlify_get_dns_record
Fetch one DNS record by id.
Netlify: Get DNS Zone
netlify_get_dns_zone
Fetch one DNS zone: domain, name servers, supported record types, and the account and site it belongs to.
Netlify: Get Deploy
netlify_get_deploy
Fetch one deploy by id: state (new, building, ready, error), branch, commit, error_message and URLs. Poll this after starting a build to know when the deploy goes live or fails.
Netlify: Get Environment Variable
netlify_get_env_var
Fetch one environment variable by key, with its values per deploy context. WARNING: the response contains each variable's UNENCRYPTED value, and node outputs are stored in automation execution records, so running this copies the values into execution history. Variables created with is_secret true come back with values omitted; mark sensitive variables as secret in Netlify if they must stay unreadable.
Netlify: Get Form Submission
netlify_get_submission
Fetch one form submission by id, with every submitted field under data.
Netlify: Get Site
netlify_get_site
Fetch one site: state, URLs, custom domain, build settings, and the currently published deploy (its id is what rollback and restore work against).
Netlify: List Accounts
netlify_list_accounts
List the teams (accounts) the token can access, with plan and usage capabilities. The account id or slug returned here is what the environment variable and build status nodes need.
Netlify: List Build Hooks
netlify_list_build_hooks
List a site's build hooks: incoming URLs that trigger a build of a set branch when POSTed to. Each hook's url and id feed the trigger and delete nodes.
Netlify: List DNS Records
netlify_list_dns_records
List every DNS record in a zone: type, hostname, value, TTL. Records with managed true are Netlify-managed (created automatically for its own services).
Netlify: List DNS Zones
netlify_list_dns_zones
List the DNS zones (domains on Netlify DNS) the token can access, with name servers and linked sites. Zone ids feed the record nodes.
Netlify: List Environment Variables
netlify_list_env_vars
List environment variables for a team, or for one site via site_id, with per-context values. WARNING: the response contains each variable's UNENCRYPTED value, and node outputs are stored in automation execution records, so running this copies the values into execution history. Variables created with is_secret true come back with values omitted; mark sensitive variables as secret in Netlify if they must stay unreadable.
Netlify: List Form Submissions
netlify_list_form_submissions
List verified submissions of ONE form, newest first, with the submitted field data under data. The new-form-submission automation usually starts here.
Netlify: List Site Builds
netlify_list_site_builds
List a site's builds, newest first, each linking to the deploy it produced (deploy_id) with done and error status.
Netlify: List Site Deploys
netlify_list_site_deploys
List a site's deploys, newest first, with state, branch, commit and URLs. Filter to production deploys, deploy previews, a branch, or a state; latest-published narrows to the deploy currently live. The ids here feed the restore, cancel and lock nodes.
Netlify: List Site Form Submissions
netlify_list_site_submissions
List verified form submissions across ALL forms on a site, newest first, with the submitted field data. Submissions can contain visitors' personal data; handle downstream accordingly.
Netlify: List Site Forms
netlify_list_site_forms
List the Netlify Forms detected on a site, with field definitions and submission counts. Form ids feed the submissions nodes.
Netlify: List Sites
netlify_list_sites
List the sites the token can access, with URLs, custom domains, build settings and the currently published deploy. Filter by exact name or by ownership, and page with page/per_page.
Action nodes 18
Netlify: Cancel Deploy
netlify_cancel_deploy
Cancel a deploy that is still processing. The deploy ends in an error state and the currently published version stays live; recover by starting a new build. Only in-progress deploys can be cancelled.
Netlify: Create Build Hook
netlify_create_build_hook
Create a build hook for the site: the response's url is an unauthenticated endpoint that starts a build of the chosen branch whenever it receives a POST. Treat that URL as a secret; anyone holding it can trigger builds (which consume build minutes).
Netlify: Create DNS Record
netlify_create_dns_record
Create a DNS record in a zone. CAUTION: this changes LIVE DNS for a real domain as soon as it propagates; a wrong record can misroute mail (MX) or traffic. Reversible by deleting the record, but propagation and caching mean mistakes can linger up to the TTL.
Netlify: Create Environment Variables
netlify_create_env_vars
Create one or more environment variables on the team, or on one site via site_id. Each variable carries per-context values and optional scopes. For anything sensitive set is_secret true: secret values are write-only afterwards (unreadable via UI, API and CLI), which is Netlify's own mechanism for keeping credentials out of places like automation execution records.
Netlify: Delete Build Hook
netlify_delete_build_hook
DESTRUCTIVE: delete a build hook. Its URL stops working immediately and cannot be recreated with the same id, so every external service pointed at it silently stops triggering builds. Returns 204 with an empty body.
Netlify: Delete DNS Record
netlify_delete_dns_record
DESTRUCTIVE: delete a DNS record from LIVE DNS. Deleting the wrong record can take a site or its email offline until the record is recreated and propagates. Read the record first (Netlify: Get DNS Record) so it can be recreated if needed. Returns 204 with an empty body.
Netlify: Delete Environment Variable
netlify_delete_env_var
DESTRUCTIVE: delete an environment variable and every one of its context values (team-wide, or from one site via site_id). Secret values cannot be read back before deleting, so there is no way to restore them afterwards. The next build runs without the variable. Returns 204 with an empty body.
Netlify: Delete Form Submission
netlify_delete_submission
DESTRUCTIVE: permanently delete a form submission and its data; there is no undo. Useful for spam cleanup and data-removal requests. Returns 204 with an empty body.
Netlify: Delete Site
netlify_delete_site
DESTRUCTIVE: permanently delete a real site, its deploy history, forms and settings. The site stops serving immediately and there is no undo via the API. Returns 204 with an empty body on success.
Netlify: Lock Deploy (Stop Auto-Publishing)
netlify_lock_deploy
Lock the site to this published deploy: new builds still run but stop being auto-published, freezing production at the locked version (a change freeze in one call). Undo with Netlify: Unlock Deploy.
Netlify: Restore Deploy (Rollback to Deploy)
netlify_restore_site_deploy
Publish a specific past deploy again, making it the live production version of the site: the roll-back-to-known-good workflow. Takes effect immediately on the live site; reversible by restoring another deploy. Pick the deploy id from Netlify: List Site Deploys.
Netlify: Rollback Site to Previous Deploy
netlify_rollback_site_deploy
Roll the site back to the deploy that was published before the current one, in one call with no deploy id needed. Takes effect immediately on the live site. Returns 204 with an empty body; follow with Netlify: Get Site to see the newly published deploy. For rolling back to a SPECIFIC older deploy, use Netlify: Restore Deploy instead.
Netlify: Set Environment Variable Value
netlify_set_env_var_value
Set the value of an EXISTING environment variable for one deploy context, leaving its other context values alone: the day-to-day update node. New values apply from the next build or function reload, not retroactively to the running deploy.
Netlify: Start Build
netlify_start_build
Trigger a new build of the site from its linked repository, producing a fresh deploy. No branch means a production build; a non-main branch produces a branch deploy. This is also the retry-a-failed-deploy move (optionally with clear_cache). This starts a real CI build that consumes the account's build minutes; beyond the plan's included allowance Netlify charges for extra minutes. Netlify also rate-limits deploy-producing calls to 3 per minute and 100 per day.
Netlify: Trigger Build Hook
netlify_trigger_build_hook
Fire a build hook, starting a build exactly as an external service POSTing the hook URL would (note the hook endpoint itself needs no auth; the unguessable id is the credential). Optionally override the branch and deploy title or clear the cache. This starts a real CI build that consumes the account's build minutes; beyond the plan's included allowance Netlify charges for extra minutes. Netlify also rate-limits deploy-producing calls to 3 per minute and 100 per day.
Netlify: Unlock Deploy (Resume Auto-Publishing)
netlify_unlock_deploy
Release a deploy lock so new production builds auto-publish again. Pass the id of the locked deploy.
Netlify: Update Environment Variable (Replace)
netlify_update_env_var
Replace an environment variable wholesale: rename it, change its scopes, or REPLACE ITS ENTIRE VALUES LIST (context values missing from the new list are dropped). For changing one context's value, prefer Netlify: Set Environment Variable Value. Setting is_secret true makes the values write-only from then on.
Netlify: Update Site
netlify_update_site
Update a site's settings: rename it (changes its netlify.app URL), point its custom domain, set or clear password protection, toggle HTTPS forcing, or patch any other documented site attribute through the body field. Changes to name and custom_domain affect the LIVE site's URLs immediately.
Using the integration
On the automation canvas
Netlify nodes chain with every other node: a scheduled Netlify: List Site Deploys sweep can open a task in Mattering Productivity when a production deploy fails, log each deploy to a Mattering database, and hold a gated Netlify: Rollback Site to Previous Deploy ready for the day a bad deploy actually goes live.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can list sites, read deploy and build status, and check the team's build minutes through the same nodes your workflows use. The read-only site, deploy, and build nodes are the safest Netlify surface to hand an agent; keep the delete nodes, the build starters, and the environment variable reads gated.
Rollback, two ways
Netlify: Restore Deploy (Rollback to Deploy) publishes a specific past deploy as the live production version, with the id chosen from Netlify: List Site Deploys. Netlify: Rollback Site to Previous Deploy flips back to whatever was published before the current deploy, no id needed; it returns an empty 204, so follow it with Netlify: Get Site to see the newly published deploy. Both take effect immediately on the live site and both are reversible by restoring another deploy. For a planned freeze rather than a rollback, Netlify: Lock Deploy (Stop Auto-Publishing) pins production at the locked deploy while builds keep running, and Netlify: Unlock Deploy (Resume Auto-Publishing) releases it.
Builds consume build minutes
Netlify: Start Build and Netlify: Trigger Build Hook start real CI builds that consume the account's build minutes; past the plan's included allowance Netlify charges for extra minutes, and Netlify rate-limits deploy-producing calls to 3 per minute and 100 per day. There is no retry endpoint in Netlify's API, so retrying a failed deploy means starting a new build, optionally with clear_cache, and the node descriptions say so plainly. Put Netlify: Get Account Build Status in front of build-triggering automations to check the queue and the minutes counter, and use Netlify: Get Build or Netlify: Get Deploy to follow progress afterwards.
Environment variable secrecy
The environment variable read nodes return unencrypted values, and node outputs are stored in automation execution records, so running Netlify: List Environment Variables or Netlify: Get Environment Variable copies plaintext values into execution history. The integration does not silently redact them: that would break the legitimate read use and fake a safety property the platform does not have. The real fix is Netlify's own secrecy mechanism: create sensitive variables with is_secret true via Netlify: Create Environment Variables, which makes their values write-only afterwards (unreadable via UI, API, and CLI), keeping them out of execution records at the source. For day-to-day changes, Netlify: Set Environment Variable Value updates one deploy context's value and leaves the rest alone; Netlify: Update Environment Variable (Replace) replaces the whole variable and drops any context values missing from the new list, so reach for it deliberately.
Build hooks and the trigger direction
A build hook is an incoming URL on Netlify's side: POST to it and a build of the configured branch starts. Netlify: Create Build Hook returns that URL, and the endpoint needs no authentication, because the unguessable id in the URL is the credential, so treat the URL itself as a secret; anyone holding it can start builds that consume build minutes. Netlify: Trigger Build Hook fires a hook from the canvas, optionally overriding the branch and deploy title or clearing the cache. In the other direction there is no inbound Netlify trigger in this integration: to react to deploy or form changes, poll Netlify: List Site Deploys or Netlify: List Site Form Submissions on a schedule.
Troubleshooting
Test Connection fails with a 401
Every Netlify node suddenly returns 401 after months of working
Netlify: Start Build or Netlify: Trigger Build Hook is refused or rate limited
Environment variable values are appearing in execution records
A secret environment variable comes back with its values missing
Context values disappeared after updating an environment variable
Netlify: Rollback Site to Previous Deploy returned an empty response
A DNS record change has not taken effect, or a delete broke mail or traffic
Related
The Netlify MCP
What connecting Netlify unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Netlify is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.