Snowflake is a cloud-based data platform that combines the power of a data warehouse with the flexibility of a cloud solution, enabling organizations to store, analyze, and share large volumes of data seamlessly. Using the Superblocks integration with Snowflake, teams can effortlessly build custom internal tools that leverage real-time data, streamlining workflows and enhancing operational efficiency across the organization.
Setting up Snowflake
If you’re using Superblocks Cloud, you may need to allowlist Superblocks IP addresses to connect to your database.
Learn how to configure this in Snowflake’s guide on
Controlling network traffic with network policies.
Alternatively, use Superblocks Hybrid or Cloud-Prem architectures to keep your data within your VPC.
1. Add integration
Select Snowflake from the
integrations page.
Fill out the form with the following settings based on your authentication method:
| Field | Required | Description |
|---|
| Account identifier | ✓ | Snowflake account identifier. The account identifier does not include the snowflakecomputing.com suffix |
| Username | ✓ | Login name for the user |
| Password | ✓ | Password for the user |
| Database | ✓ | Name of the database to use |
| Default warehouse | ✗ | Name of the warehouse to use. Defaults to the user’s default warehouse |
| Default schema | ✗ | Name of the schema to use for the database. Defaults to public |
| Default role | ✗ | Name of the role to use. Defaults to the user’s default role |
| Field | Required | Description |
|---|
| Account identifier | ✓ | Snowflake account identifier. The account identifier does not include the snowflakecomputing.com suffix |
| Username | ✓ | User name of Okta user |
| Password | ✓ | Password of Okta user |
| Authenticator URL | ✓ | The URL endpoint for your Okta account (e.g. https://<okta_account_name>.okta.com) |
| Database | ✓ | Name of the database to use |
| Default warehouse | ✗ | Name of the warehouse to use. Defaults to the user’s default warehouse |
| Default schema | ✗ | Name of the schema to use for the database. Defaults to public |
| Default role | ✗ | Name of the role to use. Defaults to the user’s default role |
| Field | Required | Description |
|---|
| Account identifier | ✓ | Snowflake account identifier. The account identifier does not include the snowflakecomputing.com suffix |
| Username | ✓ | Login name for the user |
| Private key | ✓ | The private key used for authentication. For more information, see Using key-pair authentication and key-pair rotation. |
| Passphrase | ✗ | The passphrase used to decrypt the private key for the specified user. See Using key-pair authentication and key-pair rotation. |
| Database | ✓ | Name of the database to use |
| Default warehouse | ✗ | Name of the warehouse to use. Defaults to the user’s default warehouse |
| Default schema | ✗ | Name of the schema to use for the database. Defaults to public |
| Default role | ✗ | Name of the role to use. Defaults to the user’s default role |
| Field | Required | Description |
|---|
| Account identifier | ✓ | Snowflake account identifier. The account identifier does not include the snowflakecomputing.com suffix |
| Subject token source | ✓ | |
| Token URL | ✓ | The token endpoint of the authorization server, used to exchange an authorization code for an access token |
| Client ID | ✓ | The ID issues to your OAuth client during registration |
| Client secret | ✓ | The secret issued to your OAuth client during registration |
| Audience | ✓ | Snowflake account url |
| Scopes | ✓ | session:role-any |
| Database | ✓ | Name of the database to use |
| Default warehouse | ✗ | Name of the warehouse to use. Defaults to the user’s default warehouse |
| Default schema | ✗ | Name of the schema to use for the database. Defaults to public |
| Default role | ✗ | Name of the role to use. Defaults to the user’s default role |
3. Test and save
Click Test Connection to check that Superblocks can connect to the data source.
After connecting successfully, click Create to save the integration.
4. Set profiles
Optionally, configure different profiles for separate development environments.
Troubleshooting
If you run into issues, see Troubleshooting Database Integrations. 
