Skip to main content
Administrator Guide
Last Updated: 2026-11-13
Connect Snowflake to Decision Intelligence

Connect Snowflake to Decision Intelligence

  • A Decision Intelligence (DI)-enabled instance to create the Snowflake connection.
  • Access to an account with the ACCOUNTADMIN role in Snowflake.
  • A default warehouse assigned to each Snowflake user who will connect, with usage on that warehouse granted to the user's role.
You can connect your Snowflake warehouse to DI using OAuth authentication. This integration enables DI to pull your warehouse data into an analysis alongside your Adaptive Planning data or uploaded files. A Snowflake administrator creates 1 OAuth security integration for the entire account. After the initial setup, any user can authenticate their own connection in WDI using standard SSO and the three provided credentials.
If you have the
Manage Decision Intelligence
permission, there is an alternate way that you can connect Snowflake to DI. This permission enables you to create the Snowflake connection for all users as a DI administrator, instead of each user setting up their own connection. As an administrator you can set up the OAuth security integration so that all users don’t have to provide the 3 credentials themselves when connecting to Snowflake.
To access the Snowflake connector as an administrator, click
Manage Data Sources
from your user profile, and then click
Set Up
for Snowflake. You can follow the instructions on the interactive Snowflake page rather than the instructions in this document. Make sure to use the correct redirect URI when you connect Snowflake as an administrator, since it's different than if you are setting up the connection as an individual user. Once the OAuth security integration and connection is complete, users can log in to Snowflake without any extra configuration steps.
  1. Determine if your Snowflake account restricts inbound connections by IP address.
    1. Run this SQL query in a Snowflake worksheet:
      SHOW PARAMETERS LIKE 'NETWORK_POLICY' IN ACCOUNT;
    2. If the query returns:
      • A policy name, you must add DI’s IP range to this policy in Step 2.
      • Nothing, your account has no network policy. Proceed to Step 3.
    3. To check whether a specific user has their own policy, run this SQL query:
      SHOW PARAMETERS LIKE 'NETWORK_POLICY' IN USER <username>;
      If level = USER in the Level column, the user has their own policy. A user’s own policy doesn’t need DI’s range, but it replaces the account policy for that user’s sign-in, so it must allow their own network.
  2. Add DI’s IP range to Snowflake’s account policy, if required.
    DI connects to Snowflake from this IP range, which is the same for every DI environment: 44.223.89.56/29
    You must have SECURITYADMIN access or higher to update the account policy.
    Add the range to your existing account policy. Don’t create a separate policy for DI, and don’t attach a policy to individual users to add DI to the allowlist. A user-level policy replaces the account policy for that user’s sign-in. If it doesn’t include the user’s own network, they’ll be locked out of Snowflake.
    1. Run this SQL script to review the current network policy. You can find the name of your policy in Step 1.b.
      DESCRIBE NETWORK POLICY <policy_name>;
    2. Review the results to determine if there are blocked entries and how the allowed list is stored.
      A blocked entry overrides an allowed one. Make sure nothing in BLOCKED_IP_LIST or BLOCKED_NETWORK_RULE_LIST covers 44.223.89.56/29. If the policy uses blocked network rules, run DESCRIBE NETWORK RULE <rule_name>; to see the IPs in each one.
    3. Add DI’s range to the allowed list.
      If the policy uses ALLOWED_IP_LIST, copy the existing list into the command and add DI’s range. SET replaces the whole list, so leaving out existing IPs will lock out systems that rely on them.
      ALTER NETWORK POLICY <policy_name> SET ALLOWED_IP_LIST = (<existing entries>, ... '44.223.89.56/29');
      If the policy uses network rules, create a rule for DI’s range and add it to the policy:
      USE SCHEMA <database>.<schema>; CREATE NETWORK RULE wdi_egress_rule MODE = INGRESS TYPE = IPV4 VALUE_LIST = ('44.223.89.56/29'); ALTER NETWORK POLICY <policy_name> ADD ALLOWED_NETWORK_RULE_LIST = ('<database>.<schema>.wdi_egress_rule');
  3. Set up OAuth authentication.
    A Snowflake administrator creates 1 OAuth security integration for the whole account. The security integration produces these values that are the same for all users connecting to that Snowflake account:
    • Client ID
    • Client Secret
    • Snowflake Account URL
    1. Create the security integration.
      Sign in to Snowflake with an ACCOUNTADMIN role, and then run this SQL query in a Snowflake worksheet. Replace <integration_name> with whatever name you want for the integration. Example: WDI_OAUTH. The redirect URI is fixed and should be entered exactly as shown.
      USE ROLE ACCOUNTADMIN; CREATE SECURITY INTEGRATION <integration_name> TYPE = OAUTH ENABLED = TRUE OAUTH_CLIENT = CUSTOM OAUTH_CLIENT_TYPE = 'CONFIDENTIAL' OAUTH_REDIRECT_URI = 'https://api.pipedream.com/connect/oauth_callback/snowflake_oauth' OAUTH_ISSUE_REFRESH_TOKENS = TRUE OAUTH_ACCESS_TOKEN_VALIDITY = 3600; -- Optional keep access token valid for 1 hour to avoid spurious disconnects OAUTH_REFRESH_TOKEN_VALIDITY = 7776000; -- Optional: Keep refresh token valid for 90 days
    2. Run this SQL script to get the Client ID and Client Secret. Replace <integration_name> with the name you used in Step 3.a.
      SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('<integration_name>');
      This query returns both the Client ID and Client Secret in a single JSON result. Save both somewhere secure, since you'll give them to all users connecting DI to this Snowflake account.
    3. Run this SQL script to get the Snowflake Account URL.
      DESCRIBE SECURITY INTEGRATION <integration_name>;
      Look at the OAUTH_AUTHORIZATION_ENDPOINT property in the results. If it shows https://example.com/oauth/authorize, then the Snowflake Account URL to share is: https://example.com. You can remove the /oauth/authorize part.
    4. Share the Client ID, Client Secret, and Snowflake Account URL values with users.
      You can share these values, through a secrets manager or a similarly secure channel, with anyone in your org who needs to connect DI to this Snowflake account. These three values are identical for every user. Each user needs their own Snowflake login, which is what actually scopes WDI's access to that person's own role and permissions.
  4. Confirm each connecting user has a default warehouse in Snowflake.
    To ensure the connection works, the signed-in user must have a default Snowflake warehouse and a USERADMIN, SECURITYADMIN, or equivalent role.
    1. To confirm a connection for a single user, run this SQL query, check the current setting, and look for DEFAULT_WAREHOUSE in the results:
      DESCRIBE USER <username>;
      If it’s empty, set it, and make sure the user’s role can use that warehouse. Run this SQL query to set the DEFAULT_WAREHOUSE value:
      ALTER USER <username> SET DEFAULT_WAREHOUSE = <warehouse_name>; GRANT USAGE ON WAREHOUSE <warehouse_name> TO ROLE <role_name>;
      The grant in this query is per role, so it only needs to be run once for each role, not once per user.
      To confirm a connection for many users, generate the statements, review them, and then run them. This lists every active user with no default warehouse and writes an ALTER USER statement for each:
      SHOW USERS; SELECT 'ALTER USER "' || "name" || '" SET DEFAULT_WAREHOUSE = <warehouse_name>;' FROM TABLE(RESULT_SCAN(LAST_QUERY_ID())) WHERE ("default_warehouse" IS NULL OR "default_warehouse" = '') AND "disabled" = 'false';
    2. Copy the output, remove any user who shouldn’t change, and run the rest.
      Only include users who will connect DI, because a default warehouse applies to every tool a user connects with, not just DI. If you change it account-wide you shift other workloads and compute costs onto that warehouse.
    3. If your users are provisioned through an identity provider such as Okta or Microsoft Entra ID (SCIM), set the default warehouse there instead, using the
      defaultWarehouse
      attribute.
      In Okta, enter the warehouse name in all uppercase. Otherwise, a manual change can be overwritten on the next sync, and setting it in the identity provider means new users get it automatically.
  5. Connect to Snowflake as a DI user.
    1. In DI, click
      Sources
      in the chat prompt, and then click
      Connectors
      .
    2. For Snowflake, click
      Connect
      .
    3. Click
      Continue
      to agree to connect to Snowflake through Pipedream.
    4. Review the Terms of Service and Privacy Policy, and then click
      Continue
      .
    5. Fill out the form using these provided fields from Step 3:
      • Client ID
      • Client Secret
      • Snowflake Account URL
    6. Click
      Continue
      .
    7. Log in to Snowflake with SSO or your username and password.
      Your Snowflake role determines your access within Snowflake.
When you’ve successfully logged in to Snowflake, DI checks that it can run a query. If that check passes, you'll see Snowflake display as connected. If the check fails, you’ll receive a message asking you to check your credentials or account information and try again.
The most common reasons this check fails, in order of occurrence.
Issue
Solution
The signed-in user has no default warehouse, or their role doesn't have USAGE on it.
Review Step 4 to confirm each connecting user has a default warehouse in Snowflake.
DI’s IP range isn’t on the account’s network policy, or a blocked entry covers it. This usually shows up as a successful Snowflake sign-in followed by a messaging stating
400 error when making access_token request
, with nothing in Snowflake’s login history.
Review Step 2 to ensure you added DI’s IP range to Snowflake’s account policy correctly.
A user can’t sign in to Snowflake after a policy was attached to them. A user-level policy replaces the account policy for that user’s sign-in, so it has to allow their own network.
Remove the user-level policy for the user so they can use the account policy, or add their network to the user-level policy.
The Snowflake Account URL doesn't match the endpoint.
Review Steps 1 and 2 to ensure there isn’t an extra or missing path segment or an incorrect protocol.
The Client ID or Client Secret doesn’t match the integration record.
Review your entries for the Client ID and Client Secret to ensure accuracy.
The security integration was disabled or recreated after the fields were shared, which invalidates the existing Client ID and Secret.
Enter the new Client ID and Secret values.
The Snowflake login was canceled or denied, or the signed-in user's role doesn't have access to the database or schema being queried.
Review Step 1 through 4 and validate data access in Snowflake.