Skip to main content

Snowflake

With Snowflake modules in Make, you can execute SQL commands, and return results in your Snowflake account.

To use the Snowflake modules, you must have a paid Snowflake account. You can create an account at snowflake.com. For subscription information, refer to the Snowflake Pricing page.

Refer to the Snowflake API documentation for a list of available endpoints.

Connect Snowflake to Make

To establish the connection, you must:

  1. For the Snowflake user/password type of connection: Obtain your account details in Snowflake.

  2. For the Snowflake key pair type of connection: Generate your private key in Snowflake.

  3. Establish the connection in Make.

Obtain your account details in Snowflake

To obtain your account name in your Snowflake account:

  1. Log in to your Snowflake account. If you are logging in for the first time, use the email you have received from Snowflake.

  2. At the bottom left, click on your generated account name next to the Snowflake icon.

  3. Copy the Account name and Organization name values shown and store them in a safe place.

You will use these values in the Account field in Make.

Generate your private key in Snowflake

To generate your private key in your Snowflake account, refer to Snowflake documentation.

Note: You need to generate both public and private keys to successfully connect Snowflake in Make. Your public key is associated with your Snowflake account, and your private key connects Snowflake to Make. You may generate either an encrypted or unencrypted private key. If you generate an encrypted key, store your password in a safe place.

Establish the connection with Snowflake in Make

To establish the connection in Make:

  1. Log in to your Make account, add a Snowflake module to your scenario, and click Create a connection.

  2. In the Connection type, select the type of the connection:

    • Snowflake username/password:

      1. Optional: In the Connection name field, enter a name for the connection.

      2. In the Account field, enter your copied Account name and Organization name that you copied above in ORGANIZATION-ACCOUNT format. For example, if your Organization name is ABC, and account name is DEF, enter ABC-DEF.

      3. In the Username and Password fields, enter your Snowflake account's login credentials.

      4. In the Database field, enter the name of the database for which you are going to execute commands. To see the names of the current databases, in the left sidebar, click Data > Databases.

    • Snowflake key pair:

      1. Optional: In the Connection name field, enter a name for the connection.

      2. In the Account field, enter your copied Account name and Organization name that you copied above in ORGANIZATION-ACCOUNT format. For example, if your Organization name is ABC, and account name is DEF, enter ABC-DEF.

      3. In the Username field, enter your Snowflake account's login username.

      4. In the Private key field, enter your unencrypted private key and proceed to the next step. If you use an encrypted private key, follow the steps below:

        1. Click Extract.

        2. In the Extract field, select Private key.

        3. Upload the private key that you generated above.

        4. For encrypted private keys: In the Password field, enter the password for your private key that you generated above.

      5. In the Database field, enter the name of the database for which you are going to execute commands. To see the names of the current databases, in the left sidebar, click Data > Databases.

  3. Click Save.

  4. If prompted, authenticate your account and confirm access.

You have successfully established the connection. You can now edit your scenario and add more Snowflake modules. If your connection requires reauthorization at any point, follow the connection renewal steps here.

Build Snowflake Scenarios

After connecting the app, you can perform the following actions:

Actions

  • Execute SQL

    • Reading from Snowflake (SELECT)

    • Writing back to Snowflake (INSERT)

In this section: