Resources · Make integration

Netlify Make integrationAutomate Netlify with Make.

Can Make react the moment a Netlify deploy breaks? Yes. The Netlify Make integration gives you 12 modules, including 5 instant triggers. This guide is for people who publish sites on Netlify and want alerts, form leads and deploys handled for them.

Try the Netlify integration on Make See the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Netlify Make integration?

The Netlify Make integration links your Netlify account to Make, a no-code tool where you build a scenario: the automation itself, made of modules. A module is one brick of that chain, like a trigger, an action or a search. Netlify tells Make when a deploy starts, fails or succeeds, or when a visitor sends a form, and the next modules act on it.

A failed deploy never goes unnoticed. Watch Deploy Failure fires as soon as a build breaks, Get a Site adds the site record, and a message module from your chat tool reaches the right person. Nobody has to keep the Netlify dashboard open to find out.

Form leads land where sales works. Watch Form Submissions hands each new submission to Make as a bundle, meaning one item passed from module to module. From there it can create a lead in a CRM or a row in a table, the way the Airtable Make integration does.

Approved content goes live on its own. When an editor signs off a change in another app, Start a Deploy rebuilds the site, and List Site Deploys lets you check what went out.

What the listed modules won't do: remove a site or change its settings. Make an API Call covers the rest of the Netlify API with the same connection. The app exists in n8n too; the Netlify n8n integration page and the n8n vs Make comparison help you choose.

Connect

How do you connect your Netlify account to Make?

01
Add a Netlify module
Open your scenario, add any Netlify module and click Create a connection. The connection is your Netlify account linked to Make once; every Netlify module in every scenario reuses it afterwards.
02
Give it a clear name
The Connection name field is optional. Fill it anyway with something like client-sites: once you link more than one Netlify account, a plain label saves you from picking the wrong one.
03
Authorize Netlify
Netlify signs you in with OAuth 2, so follow the on-screen instructions to approve access. If Make asks for credentials, paste a token generated in Netlify under User settings, Applications, Personal access tokens.

First scenario

Your first scenario: get alerted when a Netlify deploy fails

GoalWhen a deploy fails on Netlify, Make fetches the site record so you can warn the team.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.
02
Place the failure trigger
Search for Netlify, pick Watch Deploy Failure, click Create a webhook, then Create a connection to link your account as described above.
03
Choose the site to watch
Once the connection exists, Make lists the sites it can read. Pick one; only failed deploys on that site will start the scenario.
04
Add Get a Site
Click the + on the right of the trigger, add Get a Site and map the site from the first module, so the next step works with the full site record.
05
Test with Run once
Click Run once, then cause a failed deploy on a test site. Open the bubble above each module to read the bundles it received.
06
Switch it on
Turn the scenario on. From then on, each failed deploy on that site calls Make through the webhook. Add your chat or email module after Get a Site when you are ready.

Triggers

What can start a Netlify scenario?

5 modules start a scenario when something happens in Netlify. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Netlify as soon as it happens.

Netlify1Watch Deploy Events

Watch Deploy Events

Instant trigger

In Make“Triggers when any selected deploy event occurs.”

This is the catch-all deploy trigger: you tick the deploy events you care about and a single module listens for all of them, instead of stacking several narrower triggers.

How it fires

instant, Netlify calls Make through a webhook as soon as a selected event happens.

When to use it

a deploy log that records starts, failures and successes in one shared table, so anyone can see what happened to the site.

Watch out

each event runs the scenario and costs operations (one operation is one module running on one bundle, the unit Make counts on your plan), so leave the events you don't need unticked.

Netlify2Watch Deploy Failure

Watch Deploy Failure

Instant trigger

In Make“Triggers when a new deploy fails for a specific site.”

Netlify tells Make when a new deploy fails on the site you picked, so a broken build turns into a message someone reads instead of a red line nobody checks.

How it fires

instant, Netlify pings Make through a webhook as soon as the deploy fails.

When to use it

an alert for a client site, where the person in charge must hear about the failure before the client notices.

Watch out

it follows one specific site. Covering a second site means a second scenario, and the Free plan only keeps 2 scenarios active at once.

Netlify3Watch Deploy Start

Watch Deploy Start

Instant trigger

In Make“Triggers when a new deploy starts for a specific website.”

A deploy has just begun on a given site, and Make hears about it right away. Handy when people need to know a release is on its way, not only how it ended.

How it fires

instant, the start of the deploy triggers a webhook call to Make.

When to use it

a heads-up to the content team that the site is being rebuilt, so they hold off on reviewing pages until the new version is out.

Watch out

a start says nothing about the outcome. Pair it with Watch Deploy Success or Watch Deploy Failure if you also need the result.

Netlify4Watch Deploy Success

Watch Deploy Success

Instant trigger

In Make“Triggers when a new deploy succeeds for a specific site.”

Once a new deploy goes through on the chosen site, Make receives the news and your scenario can announce, record or follow up on the release.

How it fires

instant, Netlify sends a webhook to Make as soon as the deploy succeeds.

When to use it

after a successful release, pull the shipped files with List Files or post a short what's-new message to your team.

Watch out

every success runs the scenario, so on a site that redeploys often, keep an eye on the operations it uses in your plan.

Netlify5Watch Form Submissions

Watch Form Submissions

Instant trigger

In Make“Triggers when a new form is submitted in a specific site.”

Every time a visitor sends a form on your Netlify site, the submission reaches Make as a bundle you can route anywhere: a CRM, a spreadsheet, an email.

How it fires

instant, Netlify notifies Make through a webhook as soon as the form is submitted.

When to use it

a quote request on a brochure site that should create a lead in the sales tool, with no copy-paste from an inbox.

Watch out

the trigger is tied to one specific site. Send a real test submission during Run once to see what arrives before you map anything.

Modules

What else can Make do in Netlify?

Netlify gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Netlify1

Create Site Deploy

Action

In Make“Create a deploy for a specific site.”

Creates a deploy on the site you choose, straight from a scenario, so a release can begin from something that happened in Make.

When to use it

you want the deploy produced as one step of a larger flow, for example after content gets approved in another tool.

Watch out

its name sits close to Start a Deploy and Make's docs don't spell out the difference, so try both with Run once on a test site before you settle.

Netlify2

Get a Site

Action

In Make“Returns the specified site.”

Fetches one site and returns its record. The next module then has the site details at hand, not just the deploy that fired.

When to use it

right after a deploy trigger, to enrich an alert with the site details before it goes out.

Watch out

it reads a single site. To go through all of them, start with List Sites instead and let Make repeat the next steps for each one.

Netlify3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Netlify API to your scenario, with the connection you already have, for any endpoint the other eleven modules leave out.

When to use it

you need something none of the listed modules does and you'd rather not add a second tool just for that.

Watch out

you write the request yourself, so keep Netlify's API reference open and check the answer with Run once before switching the scenario on.

Netlify4

Start a Deploy

Action

In Make“Starts a new deploy on a specified site.”

Starts a new deploy on a site you pick. It's the module for rebuilding a site because of an event outside Netlify.

When to use it

an approved row in your content table or a product change in your shop should put the updated site online without anyone logging into Netlify.

Watch out

if a Watch Deploy Success scenario on the same site ends with this action, each success starts a new deploy and the loop never stops.

Netlify5

List Files

In Make“Returns a list of all the files in the current deploy.”

Returns the files of the current deploy, each one as its own bundle, so you can see exactly what is online right now.

When to use it

after Watch Deploy Success, to archive the file list or confirm a new page really made it into the release.

Watch out

the modules placed after it run once per file, which adds operations quickly on a site with many pages.

Netlify6

List Site Deploys

In Make“Lists site deploys.”

Pulls the deploy history of a site as a series of bundles, a readable record you get without opening the Netlify dashboard.

When to use it

a release summary for a client, or a check that the latest deploy really went through before you notify anyone.

Watch out

like any search, it can return nothing at all. Test with Run once so you know how the rest of the scenario behaves in that case.

Netlify7

List Sites

In Make“Lists sites deployed on Netlify.”

Lists the sites deployed on your Netlify account, one bundle per site, a natural first step for any flow that has to touch every project.

When to use it

an agency keeping an up-to-date inventory of client sites in a table, refreshed whenever someone asks for it.

Watch out

every module after it runs for each site, so a long list multiplies operations. Check the count with Run once first.

Need help

Need help automating Netlify with Make?

A person reads every message.

FAQ

Netlify and Make: common questions

01Is the Netlify Make integration free?

Yes, Netlify is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Since the five Netlify triggers are instant, the cap on active scenarios is the limit you are more likely to hit. Paid plans (Core, Pro, Teams and Enterprise) raise those limits and count usage in credits each month. Your Netlify subscription is a separate matter, handled on the Netlify side.

02What does it take to connect Netlify to Make?

An active Netlify account and a Make account. Netlify authenticates through OAuth 2: you add a Netlify module, click Create a connection and follow the on-screen instructions. With an instant trigger, click Create a webhook first. If you'd rather use a token, generate one in Netlify from your avatar, then User settings, Applications and Personal access tokens, and copy it while it's displayed. The optional Connection name field just helps you tell accounts apart later. No coding is needed at any point.

03Do Netlify triggers in Make fire in real time?

Yes. All five Netlify triggers are instant: Netlify calls Make through a webhook as soon as the event happens, whether that's a deploy starting, failing or succeeding, any deploy event you selected, or a new form submission. In the editor, those modules carry a lightning badge. That differs from a scheduled trigger, which Make checks on the scenario's schedule, every 15 minutes by default on a new scenario. Test the webhook with Run once before switching the scenario on.

04What if the Netlify module you need is missing?

Use Make an API Call. It sends a request to any endpoint of the Netlify API with the connection you already set up, so it fills the gaps left by the other modules. Keep Netlify's API documentation at hand to shape the request, then test with Run once. Make's page for this app lists no specific quota; it's marked as AI-generated from Netlify's documentation, so confirm anything critical with Netlify directly before you rely on it in production.

05Make or n8n for Netlify: which one fits?

It depends on the tool your team already runs. Netlify is available both as this Make app and as an n8n node, so neither choice leaves you stuck. On Make, you get 12 modules: 5 instant triggers for deploys and forms, 4 actions and 3 searches, plus Make an API Call for anything else, all set up without code. Compare that list with the operations of the n8n node against your exact use case. No verdict between the two holds for every team.

Add a Netlify module

Give it a clear name

Authorize Netlify

Create the scenario

Place the failure trigger

Choose the site to watch

Add Get a Site

Test with Run once

Switch it on

Need help automating Netlify with Make?