Resources · Make integration

Snowflake Make integrationAutomate Snowflake with Make.

Can Make talk to your Snowflake warehouse without a data engineer on call? Yes: the Snowflake Make integration gives you one action module that runs the SQL you write. This page shows what that single module covers, how to link your account, and how to build a first working scenario.

Try the Snowflake integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Snowflake Make integration actually do?

The Snowflake Make integration lets a Make scenario (the automation you build in Make, a chain of steps) send a SQL command to your Snowflake database and get the results back. There is exactly one module for it, Execute SQL, so everything depends on the statement you give it. Make handles the plumbing; you still write the SQL.

Closed deals written to the warehouse. A sales team wants every won deal from the CRM in Snowflake next to product data. Another app's module catches the deal, and Execute SQL runs an INSERT with the amount and company mapped in. No CSV exports passed around anymore.

A query result pushed to the people who need it. Finance asks for a figure that only lives in the warehouse. Execute SQL runs a SELECT, and the next module sends the answer to a chat channel or a spreadsheet.

Status fixes after an outside event. When a refund is approved elsewhere, an UPDATE flags the order in Snowflake so reports stay honest.

What Make will not do here: react to a change inside Snowflake. The app has no trigger, so a scenario always starts from a schedule or from another app. There is no generic API call module either. If you are comparing tools, the same warehouse also has a Snowflake n8n integration, and the n8n vs Make comparison lays out the criteria. New to the editor? The Make training starts from zero.

Connect

How do you connect Snowflake to Make?

  1. 01

    Collect your Snowflake details first

    In Snowflake, click your account name icon, then View account details. Note the Organization Name and the Account Name. You will type them together, joined by a hyphen, like ABC-DEF. Going the OAuth route? Copy the Account Identifier from the same screen. Also note the database Make will work in.

  2. 02

    Open the connection window in Make

    Add the Snowflake module to your scenario and click Create a connection. A connection is your Snowflake account linked to Make once, then reused by any Snowflake module. Give it a clear Connection name if you run several databases.

  3. 03

    Pick a connection type and save

    Under Connection type, choose Snowflake key pair (account, username, private key, database) or Snowflake OAuth (client ID, client secret, account identifier, database). For key pair, generate the public and private keys in Snowflake beforehand. Fill the fields, then click Save.

First scenario

Build your first scenario with Snowflake

GoalWhen a new form entry arrives in another app, Make inserts it as a row in a Snowflake table.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. Pick the app where the event happens first, for example your form tool, since Snowflake cannot start a scenario itself.

  2. 02

    Add Execute SQL

    Click the + to the right of that first module, search for Snowflake and choose Execute SQL. Select the connection you created, or click Create a connection now.

  3. 03

    Write the statement and map the data

    Type an INSERT into your table, then drop values from the first module into it. Each bundle, meaning one item passing from one module to the next, becomes one execution of your SQL.

  4. 04

    Test with Run once

    Click Run once, submit a test entry, and open the bubble above each module to read what it received and returned. Then check the table in Snowflake to confirm the row is there.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) and turn the scenario on. From here, every entry becomes a row without you touching it.

Modules

What the Snowflake app can do in Make

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

Snowflake1

Execute SQL

Action

In Make“Executes SQL command and returns results.”

Runs one SQL command against the database set in your connection and hands the results to the next module. Reads and writes both go through it.

When to use it
a deal closes in your CRM and its amount has to land in a sales table your analysts already query.
Watch out
every bundle that reaches the module runs your SQL again, so a DELETE or an unfiltered UPDATE repeats as many times as items arrive. Test on a copy table.
Need help

Need help automating Snowflake with Make?

A person reads every message.

FAQ

Snowflake and Make: common questions

01Is the Snowflake Make integration free?
Yes on the Make side: Snowflake is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and allow 40 minutes of execution. Each run of Execute SQL counts as an operation, the unit Make bills against. On the Snowflake side, though, you need a paid Snowflake account.
02What do you need to connect Snowflake to Make?
A paid Snowflake account, the name of the database Make should work in, and one of two connection types. Key pair asks for your account in Organization-Account format, your username and a private key you generate in Snowflake, encrypted or not. OAuth asks for a client ID and client secret, which you get by creating a security integration in a SQL worksheet, plus your account identifier. Creating that integration takes the ACCOUNTADMIN role or a role with the global CREATE INTEGRATION privilege.
03Can a Snowflake change trigger a Make scenario in real time?
No. The Snowflake app has no trigger module, so nothing inside Snowflake can wake a scenario up. You start it another way: a schedule on the first module (every 15 minutes by default, down to 1 minute on paid plans), a trigger from another app such as a form or a CRM, or a Make webhook that an external system calls. For a scheduled read, filter your query so Execute SQL only picks up recent rows.
04What if Execute SQL does not cover your use case?
It depends on the need. Since the module runs any SQL command your role allows, most data jobs fit inside it: adding, updating and reading rows. What it cannot reach is anything in Snowflake that is not a SQL command, and the app has no Make an API Call module to fill that gap. If you hit that wall, look at whether another app in Make reaches the same data, or ask the Hack'celeration team to scope a workaround with you.
05Make or n8n: which one fits Snowflake better?
It depends on who will maintain the automation. Make suits a team that wants a visual editor, the connection handled for them, and a quick first scenario, knowing that Snowflake offers a single SQL module there. n8n also has a Snowflake node and tends to appeal to people who want to self-host or write more logic by hand. Both need you to know some SQL. Pick based on hosting, who edits the scenarios, and what the rest of your stack already runs on.
Same platform

Other docs you might need on this stack.

Browse all integrations