Resources · Zapier integration

Snowflake Zapier integrationAutomate Snowflake with Zapier.

The Snowflake Zapier integration offers 5 triggers, 4 actions and 1 search. New rows, tables, views or columns can start a Zap, and a Zap can insert, update, delete or find rows in your warehouse, or run a SQL statement you write yourself.

Premium app Zapier reserves this app to its paid plans.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Snowflake Zapier integration is for

The Snowflake Zapier integration moves data between your Snowflake warehouse and everyday apps without a data pipeline project. Zapier reads rows, or spots new tables and columns, then writes rows back or passes them to another tool. It suits small, steady flows, not heavy loads.

Three results justify setting it up. A business event stored in the warehouse: a signed deal or a form reply in another app becomes a row through Create Rows, so analysts get it without an export. A warehouse signal sent to people: New Row runs your own query and every new result turns into an alert, a sheet line or a CRM update. A record kept current: Find Row locates the matching line and Update Rows rewrites it when the source changes.

What Zapier does not do here matters just as much as what it does. Every Snowflake trigger is checked on a timer, so nothing arrives the instant it lands. Any SQL you give it must finish in under 30 seconds. And the database, schema and warehouse are fixed by your connection, not chosen step by step, which shapes how many connections you will need.

If you are comparing tools, the same app is covered on our Snowflake n8n integration and Snowflake Make integration pages.

Vocabulary

Zapier vocabulary in one minute

Seven words cover the whole page. Each is explained here once, then used without a reminder.

Zap
The automation you build on Zapier: 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 on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that inserts, updates, sends or deletes something for you.
Task
The unit Zapier bills: one action that completes successfully. Your plan's allowance is counted in tasks.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is pushed by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up data that already exists, so the steps after it can reuse what it found.
Cost

What a Snowflake Zap really costs

Snowflake is a premium app on Zapier: the free plan does not include it, so you need a paid plan or the free trial.

  • Premium appYes, paid plan or trial
  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps, no premium apps

Triggers never cost a task, and neither do Zapier's checks on your tables, however often they run. You pay for actions that succeed: a Zap that inserts rows and then updates another table uses two tasks per run. An action that fails is not counted. Adding a filter, a search or a second action makes the Zap multi-step, which is a paid feature anyway. With five polling triggers, your plan also sets how quickly new data shows up.

Connect

Connect Snowflake to Zapier in three steps

  1. 01

    Open your apps

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Snowflake account linked once, then reused by every Zap that needs it.

  2. 02

    Pick Snowflake

    Search for Snowflake in the dialog, select it and click Add connection. A new tab opens where you sign in to Snowflake with the account the Zaps will use.

  3. 03

    Sign in and grant access

    Log in, then allow Zapier to use the account. It needs read rights on every table your triggers watch, and write rights on every table your actions insert into, update or delete from.

First Zap

Your first Snowflake Zap

GoalPost a message to your team each time your query returns a row worth knowing about.

  1. 01

    Create the Zap

    From your Zapier dashboard, start a new Zap. The editor opens on an empty trigger step, which is where Snowflake comes in.

  2. 02

    Set the trigger

    Pick Snowflake, then New Row and your connection. Write the SQL select statement that returns the rows to watch, and keep it fast: it has to finish in under 30 seconds.

  3. 03

    Test on real rows

    Run the trigger test. Zapier brings back the three most recent rows your query returns, so you map the next steps on real data rather than a guess.

  4. 04

    Add the filter and the action

    Add a filter that keeps only the rows that matter, then the Slack step. Map the row's columns into the message and test that step once as well.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, new rows are picked up at each check, at the pace your plan allows, and never before.

Triggers

Snowflake triggers

5 events start a Zap when something happens in Snowflake. Zapier checks for them at the interval your plan allows.

1

New Column

Polling trigger

In Zapier“Triggers when a new column is created on a selected table.”

Watches one table and starts a Zap when someone adds a column to it. It tracks the structure of your data rather than the data itself.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
the analytics team wants to hear about schema changes on a table that dashboards depend on.
Watch out
the table to watch is required, so one Zap covers one table.
2

New Row

Polling trigger

In Zapier“Triggers when a new row is created.”

You write a SQL select statement, and every new row it returns starts a Zap with its columns ready to map. That makes it the most flexible Snowflake trigger, because the query decides what counts.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a precise slice of data, like high-value orders, should alert someone.
Watch out
the statement must finish in under 30 seconds.
3

New Table

Polling trigger

In Zapier“Triggers when a new table is created.”

Reacts when a table appears in the part of Snowflake your connection points to, and passes its details to the next step. Run the test to see what it brings back about a table.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
data owners want a log, or a heads-up in a channel, whenever a new table is created.
Watch out
it reports new tables, not the rows inside them.
4

New View

Polling trigger

In Zapier“Triggers when a new view is created (from yesterday onwards).”

Spots views created in Snowflake and starts a Zap for each one. Each new view reaches the Zap on its own run, ready to be logged or announced.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
you keep a catalogue of shared views up to date.
Watch out
it only picks up views created from yesterday onwards, never older ones.
5

New or Updated Row

Polling trigger

In Zapier“Triggers when a row is either created or updated.”

Covers both cases in one trigger: a row that is created and a row that changes in the table you name. Zapier tells the two apart through a date column that records the last change.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a CRM or a sheet must mirror a Snowflake table.
Watch out
without a reliable Updated Date Column, changes go unnoticed.
Actions

Snowflake actions

Snowflake gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Rows

Action

In Zapier“Insert data into a table by specifying the column names and values to insert.”

Inserts data into a table: you name the columns and give each one its value from earlier steps.

When to use it
form replies, payments or sign-ups should land in the warehouse as they happen, not in a monthly export.
Watch out
the table and the column names are required, and the table must sit in the database your connection sets.
2

Delete Rows

Action

In Zapier“Deletes row(s) in an existing table in Snowflake”

Removes rows from a table, picked by their primary key.

When to use it
a deletion request or a cancelled record in another app must disappear from Snowflake as well.
Watch out
both the primary key column and its values are required. The key values decide which rows go, so map them from an earlier step such as Find Row.
3

Execute SQL

Action

In Zapier“Execute SQL and output resulting rows of data.”

Runs a SQL statement you write and hands the resulting rows to the next steps. It is the way out when the other actions are too narrow.

When to use it
you need a join, an aggregate or a write the menu does not cover.
Watch out
the statement must complete in under 30 seconds, so heavy queries belong elsewhere.
4

Update Rows

Action

In Zapier“Updates row(s) of an existing table in Snowflake”

Rewrites one or more existing rows, found through the primary key column and the key values you supply.

When to use it
a status or an amount changes in another tool and the warehouse copy must follow.
Watch out
the key column, the key values and the columns to write are all required, and the key values decide which rows get rewritten.
Searches

Snowflake search

1 search step looks for data that already exists in Snowflake, so a later step can use it.

A search step changes nothing: it finds data that already exists so the rest of the Zap can use it. Searches sit at the bottom of the action list, under SEARCH. Three settings decide what happens next.

1

Find Row

Search

In Zapier“Find data in a table by specifying a WHERE clause. The query will be set to LIMIT 1 result.”

Looks up a row in a table using a WHERE clause you write, and returns a single result, since the query is capped at one row.

When to use it
just before Update Rows or Delete Rows, to fetch the key of the row to change.
Watch out
the table and the WHERE clause are required. If your condition matches several rows, you get one, so make it precise.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into a find-or-create. Snowflake has no such variant, so the option does not apply here.
  3. If multiple search results are found?
    Three exits when several items match: keep the first, which is the default, stop the Zap, or pass them all on at once.
When it breaks

When a Snowflake Zap breaks

Most failures here come from slow SQL, the wrong database or timing, rarely from Zapier itself.

Zapier links one help article to this app, on getting started with Snowflake. No rate limit specific to Snowflake is published with it. The cases below come from the app's own fields and from the limits that apply to every Zap. When a run fails and the reason is not obvious, our Zapier troubleshooting page goes further.

  • The SQL takes too long

    New Row and Execute SQL both demand a statement that completes in under 30 seconds. A slow query fails the step, so narrow it or move heavy work out of the Zap.

  • The table sits in another database

    Tables are read from the database, schema and warehouse set in your connection. A table stored elsewhere needs a connection that points there.

  • Old rows never arrive

    A Zap only reacts to what happens after you publish it. Rows already in the table are not picked up, and loading that history is a separate job.

  • The Zap keeps setting itself off

    A Zap that writes into the table its own trigger watches restarts again and again, and burns through your tasks quickly.

  • A bulk load is held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • Updates slip through

    New or Updated Row relies on the Updated Date Column. If that column is not refreshed on every change, Zapier has no way to see the update.
Need help

Need help automating Snowflake with Zapier?

A person reads every message.

FAQ

Snowflake Zapier integration: FAQ

01Is the Snowflake Zapier integration free?
No. Snowflake is a premium app on Zapier, and premium apps are only open to paid plans and the free trial. The free plan gives 100 tasks a month and unlimited Zaps, but it excludes premium apps and only builds two-step Zaps. Once the trial ends, even a simple Snowflake Zap needs a subscription. Prices are not listed here because Zapier's grids change too often to publish: check its pricing page when you decide.
02How many tasks does a Snowflake Zap use?
One task per successful action, nothing for the trigger. Zapier never bills the checks it runs on your tables. A Zap that inserts one set of rows uses one task per run; one that inserts rows and then updates another table uses two, if both succeed. An action that fails is not counted. Keep loops in mind: a Zap writing into the table it watches can multiply tasks very fast.
03Is Snowflake on Zapier real time?
No. All five Snowflake triggers are polling triggers. Zapier checks on a timer, and the timer depends on your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. Paid plans can also run a check by hand from the editor while you test. If a flow must react within seconds, that delay is built in on this app, whatever you configure in the Zap itself.
04What does it take to connect Snowflake to Zapier?
A Snowflake account, a paid Zapier plan or a trial, and the right rights. The account you sign in with sets the database, schema and warehouse every step will use, and it needs read access on the tables your triggers watch and write access where your actions insert, update or delete. If your Zaps span several databases, plan one connection per database. Check those rights before the first test, not after a failed run.
05Why does a New Row trigger fail on Snowflake?
A common cause is a statement that is too slow. Zapier requires the select statement behind New Row to finish in under 30 seconds, and the same rule applies to Execute SQL. Narrow the condition so the query returns only what the Zap needs. Also check that the statement is a select that returns rows, which is what the field asks for, and that the table sits in the database your connection sets. Then test the trigger again and read the rows it brings back.
06What if the Snowflake action you need is missing?
Execute SQL usually covers it. It runs any statement you write and passes the resulting rows to the next steps, which fills the gaps left by Create Rows, Update Rows and Delete Rows. The same 30-second limit applies, and you need someone comfortable with SQL. When the change is a simple insert, update or delete by primary key, the dedicated actions are easier to maintain. Test the step once and read the rows it returns before you publish, as with any action.
07Zapier, Make or n8n for Snowflake?
It depends on your criteria rather than on a single winner. Zapier offers a quick setup and simple menus, but Snowflake is premium there and every trigger is polled on a plan-based timer. Make and n8n each have their own Snowflake page. Compare the operations you need, the volume you expect to move, how runs are billed, and who will maintain the flows. On Zapier, remember that Snowflake needs a paid plan from the first Zap.
Same platform

Other docs you might need on this stack.

Browse all integrations