Netlify n8n integrationAutomate Netlify with n8n.
Can a workflow start a deploy and read what came out of it? Yes, and that is the whole job of the Netlify n8n integration. The node exposes 7 operations across 2 resources, Deploy and Site. The trigger listens to 4 events in 2 families, deploys and form submissions. Useful once you ship more than once a week.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Netlify n8n integration actually give you?
The Netlify n8n integration is two pieces working together. A node that calls the Netlify API from inside a workflow, and a trigger that reacts to what happens on your sites. The node covers 7 operations on 2 resources, Deploy and Site. The trigger covers 4 events, three about deploys and one about form submissions. Nothing to install, nothing to host: one access token and a few fields.
First scenario, the broken build nobody noticed. The trigger fires on deployFailed, the workflow calls Get a deployment to pull the record of that deploy, and the message lands wherever the team already works, for example Slack. The point is not the alert itself, it is that the alert carries the deploy data instead of a bare ping.
Second scenario, publishing driven by content instead of by a person. A new row lands in Google Sheets, or an editor marks an article ready, and the workflow runs Create a deployment on the right site. The public n8n template library has one workflow built exactly on that idea, 1254, Deploy site when new content gets added. Same logic works from a repository event coming out of GitHub.
Third scenario, forms. Netlify collects a submission, submissionCreated fires, and the workflow routes it: a row in a spreadsheet, a record in a database, a notification to the person who owns that form. No inbox rule to maintain.
When the node has no operation for what you need, the HTTP Request node calls any endpoint of the Netlify API and reuses the same credential through predefined authentication. That is the normal escape hatch, and it means the 7 operations are a starting point rather than a ceiling.
Two things to keep in mind before building. On list operations, Return All pages through the API until everything is back, and leaving it off means you only get up to Limit. And the deploy operations pick the site from a dropdown (Site Name or ID), while the site operations take a plain Site ID string, so a value copied from one is not always usable in the other. If you want the reasoning behind the whole tool, the n8n review goes into it.
How do you connect Netlify to n8n?
- 01
Create the access token in Netlify
You need a Netlify account first. The node and the trigger both authenticate the same way, with an API access token. Generate it in Applications > Personal Access Tokens. Copy the value on the spot: a token is shown once, and starting over is faster than hunting for it later.
- 02
Save the credential in n8n
In n8n, open the Credentials menu and create a Netlify credential. A credential is a stored login that workflows reuse, so you do this once and never paste the token into a node again. Fill the Access Token field with the value from Netlify. The same credential serves both the Netlify node and the Netlify Trigger.
- 03
Pick it in the node and test
Drop a Netlify node on the canvas and select the credential from its dropdown. Run Get many sites with nothing else configured: it needs no required field, so it is the cheapest way to prove the token works. If sites come back, authentication is done and every other operation will use the same connection.
What can start a workflow from Netlify ?
Netlify Trigger is the node that starts a workflow when something happens in Netlify. It listens to 4 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Netlify account.
What you see in n8n
Every event, by family
One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.
deploy.*3submission.*1Configuration notes
01Set Up the Netlify Trigger
The Netlify Trigger, version 1, receives events by webhook. A webhook is a URL that Netlify calls the moment something happens, so the workflow starts within seconds and n8n never has to ask whether anything changed.
Key parameters
- Site Name or ID: the site being watched, picked from the dropdown or set with an expression such as
{{ $json.site_id }}, an expression being a small formula that reads a field from the incoming item. - Form Name or ID: a form on that site, also required, so have one form available even when the workflow is really about deploys.
- Event: which of the 4 events starts the workflow.
- Simplify: on, n8n hands you a trimmed version of the payload instead of the raw one.
02Deploy Events
Three of the 4 events belong to the deploy family, and together they cover the life of a build. deployCreated says a deploy has been registered, deployBuilding says it is running, deployFailed says it stopped short.
Key parameters
- Event: one event per trigger node, so watching two of them means two trigger nodes in the same workflow.
- Site Name or ID: the events are scoped to the site selected here, not to the whole account.
deployFailed is the one most teams wire first, because a failed build is silent otherwise. deployCreated is useful when you want a record of who published what and when. deployBuilding suits a status board that should show a build in progress rather than a stale green light.03Form Submitted
The submission family has a single event, submissionCreated, and it fires when someone sends the form you selected on the site you selected.
Key parameters
- Form Name or ID: the form this trigger listens to, chosen from the dropdown so you do not have to know its identifier by heart.
- Simplify: worth turning on here, since a form payload carries more metadata than most workflows need.
What can the Netlify node do?
The Netlify node exposes 7 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Deploy
4 operationsCancel a deployment
deploy.cancelWhat you see in n8n
Notes & use cases
Stops a deploy in Netlify before it goes any further, which keeps a build you already know is wrong from finishing.
Key parameters
- Deploy ID: the identifier of the deploy to stop, most often
{{ $json.id }}from the trigger item or from an earlier list operation.
Create a deployment
deploy.createWhat you see in n8n
Notes & use cases
Starts a new deploy on the site you choose, so publishing becomes something a workflow does rather than something a person remembers to do.
Key parameters
- Site Name or ID: the target site, picked from the dropdown or supplied with an expression.
- Branch: in Additional Fields, sets which branch the deploy uses.
- Title: in Additional Fields, labels the deploy so the history reads like something other than a list of hashes.
Get a deployment
deploy.getWhat you see in n8n
Notes & use cases
Returns the full record of one deploy, which is how a workflow finds out what actually happened rather than guessing from the event alone.
Key parameters
- Site Name or ID: the site the deploy belongs to, selected from the list.
- Deploy ID: the deploy itself, typically carried over from the trigger with an expression.
deployFailed, the workflow pulls the record and puts the details in the alert, so nobody has to open the dashboard to learn anything.Get many deployments
deploy.getAllWhat you see in n8n
Notes & use cases
Lists the deploy history of a site, newest activity first, and gives a workflow something to count or compare.
Key parameters
- Site Name or ID: whose history you are reading.
- Return All: on, n8n walks the pages of the API until every deploy is back; off, it stops at Limit.
- Limit: how many deploys come back when Return All stays off.
Site
3 operationsDelete a site
site.deleteWhat you see in n8n
Notes & use cases
Removes a site from the Netlify account. Irreversible, so it belongs in workflows where something else has already decided the site is finished.
Key parameters
- Site ID: a plain text field here, not a dropdown, so the value comes from Get many sites or from an expression rather than from a list you click.
Get a site
site.getWhat you see in n8n
Notes & use cases
Reads one site's record, which is the usual way to turn an identifier sitting in a workflow into something readable.
Key parameters
- Site ID: the site to read, entered as text or built with an expression such as
{{ $json.site_id }}from an earlier node.
Get many sites
site.getAllWhat you see in n8n
Notes & use cases
Returns the sites the token can see, and needs no required field, which makes it the natural first call when you are testing a connection.
Key parameters
- Return All: on, every site comes back across as many API pages as it takes; off, the node stops at Limit.
- Limit: the cap applied when Return All is off.
Need help automating Netlify with n8n?
A person reads every message.
