Domo on Snowflake

​

Intro

​

Architectural Overview

​

Prerequisites

1. Create a Snowflake service account — Create a new Snowflake account specifically for this integration. This account must have read access to your default Snowflake environment in order to create virtual Snowflake tables in Domo. For the required permissions, see Snowflake Minimum Permissions for Domo.
2. (Optional) Create a Domo service account — Create a new Domo account specifically for this integration. The account role must have the Manage Cloud Accounts and Manage DataSet grants enabled.

​

Account Creation—Write

1. Create a default Snowflake database — You need a Snowflake database that is exclusively for Domo to write Domo-managed tables. During setup, this database is the default.
   Note: Any tables not managed by Domo in this database are not seen by the Snowflake Cloud Integration.
2. (Conditional) Place IP Addresses on an allowlist — If your Snowflake environment restricts access based on IP address, place Domo IPs on an allowlist.

​

Create or Manage Your Snowflake Integrations

1. Navigate to Data Warehouse.
2. Select Connect Data.
3. Select Snowflake from the list of Cloud Integrations.

4. The Domo on Snowflake page appears.
   • To create a new integration, select Connect Snowflake and continue to Create a Snowflake Integration.
   • To modify an existing integration, select Manage Integrations. The Snowflake cloud integrations list appears. Select the wrench icon next to an integration to see management options based on your access level.

​

Create a Snowflake Integration

1. In the Name field, enter a label to identify this Snowflake integration in Domo.
   The name doesn’t need to match anything in Snowflake and can be changed later.
2. (Optional) In the Description field, enter a description to help others understand the purpose of the integration.
   This is only visible in the integration details.
3. Select an existing Snowflake service account, or select Add account to create a new one.
   This account authenticates to Snowflake and determines access to tables. For guidance on creating a service account, see Create a Snowflake Account.

4. Select the warehouse to use for querying data.
   You can assign multiple warehouses later for optimization or specific use cases.

5. Select Finish Setup. When the integration is created successfully, a confirmation screen appears.

​

Create a Snowflake Account

1. In the Name field, enter a name to identify the Snowflake service account within Domo.
   This name can be changed later.

2. In the Account Identifier field, enter your Snowflake account identifier. The account identifier is the subdomain that appears before .snowflakecomputing.com in your Snowflake URL. You can locate it in several ways:
   • From the Snowflake URL — When you’re signed in to Snowsight, the browser URL takes the form https://<account_identifier>.snowflakecomputing.com (for example, xy12345.us-east-1.snowflakecomputing.com). The portion before .snowflakecomputing.com is your account identifier.
   • From Snowsight — In the lower-left corner of Snowsight, hover over your account name to display the account details popover, which lists the account identifier and locator. You can also navigate to Admin > Accounts to view account identifiers for the accounts in your organization.
   • From a SQL worksheet — Run SELECT CURRENT_ACCOUNT(); to return the account locator, or SELECT CURRENT_ORGANIZATION_NAME(); together with SELECT CURRENT_ACCOUNT_NAME(); to return the organization-qualified identifier.
   
   For full details on the available identifier formats, see the Snowflake account identifier documentation.
3. Select your authentication method:
   • Key Pair (Recommended)
     Snowflake is phasing out single-factor password sign-ins. Key-pair authentication is more secure and future-proof. See their security MFA rollout and key pair auth documentation. Add the public key to your Snowflake user:
     ALTER USER "<username>" SET RSA_PUBLIC_KEY='<public_key>'
     
     Replace username and public_key with your actual values. In the Private Key field, upload your private key file (.p8 format). Optionally, enter the passphrase if your key pair includes one.

• Username & Password
  Enter your Snowflake username and password.

4. (Optional) In the Default Role field, enter the Snowflake role to assign to this service account.
   If left blank, Snowflake applies the default role configured for the user in Snowflake.

​

Configure Write & Native Transform

• Write to Snowflake from connectors — Allows Domo to create and update tables in Snowflake using data loaded through connectors.
• Execute Magic ETL transformations natively — Runs Magic ETL DataFlows directly in Snowflake rather than in Domo’s execution environment.

​

Prerequisites

​

Setup

1. Toggle on the capabilities you want to enable:
   • Write to Snowflake from connectors
   • Execute Magic ETL transformations natively
2. Select the default Database and Schema where Domo writes data.
   If the schema doesn’t exist, Domo creates it when selected in Magic ETL.

3. In the Default Role field, enter the Snowflake role Domo uses for write and transform operations.
   Domo uses this role to generate the SQL in the next step.

4. Have a Snowflake user with the ACCOUNTADMIN role run the generated SQL to:
   • Create the write-back database
   • Grant access to the service account
   • Create a DOMO_UTIL schema for Domo-managed resources

5. In the Temporary artifact storage field, specify the database Domo uses for temporary storage during native transform execution.
   This can be the same database selected in step 2, or a separate database if you prefer to isolate temporary artifacts.

6. On the Finalize Write & Native Transform Integration page, review the permissions Domo requires.
   Select I understand that Domo can make changes to my Snowflake environment, then select Done.

​

Configure OAuth

​

Prerequisites

​

Configure OAuth in Snowflake

1. In Snowflake, modify and run the following query to define the security integration.
   Replace name_goes_here with a meaningful name—this name is used in subsequent queries.
   create or replace security integration <name_goes_here>
   type = oauth
   enabled = true
   oauth_client = custom
   oauth_client_type = 'CONFIDENTIAL'
   oauth_redirect_uri = 'https://oauth.domo.com/api/data/v1/oauth/providers/snowflake-oauth/exchange'
   oauth_issue_refresh_tokens = true
   oauth_refresh_token_validity = 86400;
   
2. Update oauth_refresh_token_validity to set how long refresh tokens remain valid:
   • 1 day = 86400 seconds
   • Max = 7776000 seconds (90 days)
   • Min = 3600 seconds (1 hour)
3. Run the following query to verify the integration:
   desc security integration <name_goes_here>;
   
4. Run the following query to retrieve the client ID and secret:
   select system$show_oauth_client_secrets('<name_goes_here>');
   
5. Copy the client ID and secret for use in Domo.

​

Configure OAuth in Domo

1. In the Name field, enter a name to identify this OAuth configuration within Domo.
2. In the Account Identifier field, enter your Snowflake account identifier.
   You can find it under Account > View Account Details in Snowflake.
3. In the Client ID and Client Secret fields, paste the values retrieved from Snowflake.
4. In the Primary Role field, select the Snowflake role to apply to all Domo users.

5. Select Connect, then sign in using your Snowflake credentials.
6. Review the requested permissions and select Allow to complete the setup.

​

FAQ

​

Troubleshoot

​

Missing Tables

​

Setup Problems

​

Check Snowflake Service Account

1. Log in to Snowflake with the service account credentials.
2. Ensure you can view the default Snowflake Database and query the tables you expect to import.

​

Assign Correct Role

​

Use the Correct URL

​

Next Steps