Resources · Zapier integration

Netlify Zapier integrationAutomate Netlify with Zapier.

The Netlify Zapier integration gives you 4 triggers and 1 action, with no search step. All four triggers are instant, so a deploy or a form entry reaches your Zap at once, even on the free plan. Here is what each one does, what it costs and where it breaks.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Netlify Zapier integration actually does

Connecting Netlify to Zapier means your sites can start automations, and an automation can start a build. Netlify reports three moments of a deploy (started, succeeded, failed) plus every new form entry, and Zapier can ask Netlify to run a new deploy of a site that already exists.

Three results people build with it. A failed-build alert: New Deploy Failed pushes the bad news to the place your team actually reads, instead of a dashboard nobody opens. A form inbox outside Netlify: New Form Submission sends each entry to a spreadsheet, a CRM or an email, so leads stop living in the site admin. A chained rebuild: New Deploy Succeeded on a main site fires Start Deploy on a second site that depends on it, like a docs or a landing site.

What it does not do matters as much. There is a single action, so Zapier cannot create a site, change a setting, publish a form or delete anything on Netlify. There is no search step either, so a Zap cannot look up a past deploy or an old form entry. Everything starts from something happening now.

If you want to compare tools before you commit, the same app is covered on the Netlify n8n integration and the Netlify Make integration pages, written the same way.

Vocabulary

Zapier words in one minute

Seven terms come back on every line of this page. Read them once, the rest gets easier.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, sends or kicks off something for you, here a new deploy.
Task
What Zapier bills you for: one action your Zap completes successfully. Your plan is a count of those.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier the second the event happens. Every Netlify trigger is instant.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
Connection
Your Netlify account linked to Zapier once, then reused by every step that talks to Netlify.
Cost

What a Netlify Zap really costs

Short answer: Netlify is not a premium app, so it works on the free plan, and its triggers never cost a thing.

  • Tasks on the free plan100 per month
  • Steps on the free plan2 (one trigger, one action)
  • Premium appNo
  • Cost of a trigger0 tasks

You pay in tasks, and only for actions that succeed. A Start Deploy that fails is not counted, and neither is the trigger, however many deploys or form entries it reports. Each action in a Zap counts on its own, so a Zap with three actions uses three times as many tasks as a Zap with one. The free plan stops at two steps: one trigger, one action. Add a filter or a second action and the Zap needs a paid plan.

Connect

Connect your Netlify account in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Netlify account, and access to every site you want a Zap to watch or rebuild, including the ones a teammate owns.

  2. 02

    Pick Netlify

    Type Netlify in the search box of the dialog that opens, then select it, then click Add connection. A new browser tab opens on the Netlify sign-in page.

  3. 03

    Sign in and grant access

    Log in to Netlify in that tab and authorize Zapier on your account. The tab closes and the connection shows up in the list. From then on, every Netlify step of every Zap reuses it.

First Zap

Your first Zap: form entries straight to your inbox

GoalA successful deploy of your main site rebuilds two sites that depend on it, without anyone clicking anything in Netlify.

  1. 01

    Create the Zap

    Start a new Zap in the editor. Building comes first: you pick the app and the event that start it, then the app and the action that follow, and you map the fields between them.

  2. 02

    Set the trigger

    Pick Netlify, choose New Deploy Succeeded, select your connection, then pick the main site in the required Site field. Without it, the trigger has nothing to listen to.

  3. 03

    Test with a real deploy

    Run the test. Zapier brings back the three most recent deploys of that site, so a site that has never deployed gives you nothing to pick yet.

  4. 04

    Add two Start Deploy steps

    Add Start Deploy and pick the first dependent site, then add it again for the second one. Never pick the main site here, or the Zap would rebuild itself in a loop.

  5. 05

    Test, then publish

    Test each step once and read what came back, then click Publish. Two actions make this a multi-step Zap, so a paid plan, and each successful rebuild counts as one task.

Triggers

The 4 Netlify triggers

4 events start a Zap when something happens in Netlify, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Deploy Succeeded

Instant trigger

In Zapier“Triggers when a new version of your site has successfully deployed.”

Your Zap starts as soon as a new version of the chosen site is live. That makes it the natural starting point for anything that should happen after a release, like telling the team or rebuilding a second site.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketing site goes live and the sales team should hear about it without checking Netlify.
Watch out
one Zap watches one site, picked in a required field, so three sites mean three Zaps or three copies.
2

New Deploy Started

Instant trigger

In Zapier“Triggers when a new deploy of your site has started building.”

This one reacts earlier, the second Netlify begins building a new version of the site. Nothing is live yet, so it is about warning people rather than celebrating a release.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a content editor wants a heads-up in chat that a build is running before reloading the page.
Watch out
every build fires it, including the ones that end in failure, so pair it with the failed trigger if you track outcomes.
3

New Deploy Failed

Instant trigger

In Zapier“Triggers when a new deploy of your site has failed.”

When a build breaks, this trigger hands the bad news to Zapier straight away. It is the most useful of the four for small teams, because a failed deploy otherwise stays silent until someone notices the site did not change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
open a ticket or ping the developer on duty the minute a production build fails.
Watch out
never answer it with Start Deploy on the same site: a build that keeps failing would relaunch itself in a loop.
4

New Form Submission

Instant trigger

In Zapier“Triggers when a form receives a new submission.”

Each time a visitor fills in a form hosted on your Netlify site, the entry goes to Zapier with its fields ready to map. It turns your Netlify forms into the front door of your CRM, your sheet or your inbox.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a freelancer wants every quote request copied into a spreadsheet and answered the same day.
Watch out
the site is required, the form is not: leave the Form field empty and every form on that site feeds the same Zap.
Actions

The Netlify action

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

1

Start Deploy

Action

In Zapier“Performs a new deploy of an existing site.”

This action asks Netlify to run a new deploy of a site that already exists. It is how something happening in another tool, or a deploy on a first site, can refresh a second one.

When to use it
rebuild a site when a record changes in the tool where your content lives.
Watch out
clearing the build cache is an optional box in the step; the site, picked in a required field, must not be the one your trigger watches.
When it breaks

When a Netlify Zap breaks

Zapier ties no help article to Netlify, so the traps below come from how Zaps work in general and from the fields the app requires.

Most broken Netlify Zaps fall into four cases. None of them shows an error on the site itself, which is why they go unnoticed. For a wider checklist, the Zapier troubleshooting guide covers what is not specific to Netlify.

  • Old deploys and entries are ignored

    A Zap only reacts to what happens after you publish it. Form entries received last month stay in Netlify, and moving them is a separate job.

  • The deploy loop

    Start Deploy on the same site that a deploy trigger watches makes the Zap fire itself again and again, and each round burns a task.

  • One Zap, one site

    Each trigger and Start Deploy point at a single site, picked in a required field. Watching three sites means three Zaps, and a forgotten copy keeps running.

  • A burst of entries held back

    When a form suddenly receives a large batch at once, Zapier's flood protection can hold the trigger back instead of running the Zap for every entry.
Need help

Need help automating Netlify with Zapier?

A person reads every message.

FAQ

Netlify and Zapier: your questions

01Is the Netlify Zapier integration free?
Yes. Netlify is not a premium app, so it works on the free Zapier plan. That plan gives you 100 tasks per month and Zaps limited to two steps, one trigger and one action. A Zap that sends each form entry to a spreadsheet fits inside it. The moment you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. The four triggers themselves never cost anything, whatever the plan.
02How many tasks does a Netlify Zap use?
One task per action that succeeds, nothing for the trigger. A Zap that turns each new form entry into an email uses one task per entry. Add a second action, say a row in a sheet, and the same entry costs two tasks, because every successful action is counted on its own. An action that fails is not counted. A few apps use more than one task per action, so check the editor if your total looks off.
03Do Netlify triggers work in real time?
Yes, all four are instant. Netlify itself tells Zapier when a deploy starts, succeeds or fails, and when a form receives an entry, so the Zap starts at once. The polling interval of your plan, 15 minutes on the free plan, does not apply to them. That is rare: most Zapier triggers are polling ones and wait for the next check. In the editor, an instant trigger shows a lightning bolt next to its name.
04What does it take to connect Netlify to Zapier?
A Netlify account and access to the sites you want to automate. The connection goes through the Apps page of Zapier: add a connection, pick Netlify, then sign in and authorize Zapier in the tab that opens. If a site belongs to a teammate, your account needs access to it before a Zap can watch or rebuild it. Every trigger and the Start Deploy action then ask you to pick the site in a required field, one site per step.
05Can one Zap watch several Netlify sites?
No. Each Netlify trigger asks for one site in a required field, and Start Deploy works the same way. To follow three sites, you build three Zaps, or one Zap and two copies with a different site picked. For forms, the Form field is optional: leave it empty and every form of the chosen site starts the Zap, fill it and only that form does. Keep the copies named clearly, because a forgotten one keeps running and keeps counting tasks on its action.
06What if the Netlify operation you need does not exist?
Then Zapier cannot do it for Netlify today. The app has one action, Start Deploy, and no search, so creating a site, changing a setting, publishing a form or reading old entries is out of reach. What still works is chaining: let a Netlify trigger start the Zap, then hand the data to another app that covers the missing part, like a spreadsheet or a CRM. If the gap is on the Netlify side itself, another automation tool may expose more of it, with more setup to plan for.
07Zapier, Make or n8n for Netlify?
It depends on what matters to you, and this page only covers the Zapier side. On Zapier, Netlify gives you four instant triggers and one action, Start Deploy, with no search, and it works on the free plan as long as the Zap stays at two steps. If that is enough for your alerts and form routing, there is no reason to look further. If you need more, compare what the Make and n8n pages list for Netlify before you pick, and weigh who will maintain the automation.
Same platform

Other docs you might need on this stack.

Browse all integrations