Snowflake Connector

Connect Snowflake so Applied can run controlled SQL queries against a Snowflake warehouse.

This guide covers direct Snowflake database credentials. It does not cover the Snowflake Hosted MCP setup strategy.

Common use cases

Look up account, order, or entitlement data from Snowflake.
Run read-only support queries from a Flow.
Update records only after explicit customer or teammate approval.
Use Snowflake query results to route or enrich support workflows.

Start with read-only access unless your workflow truly needs writes.

Before you begin

Before connecting Snowflake, make sure:

You know the account identifier.
You have a dedicated Snowflake user for Applied.
You know the warehouse, database, schema, and optional role.
You know whether the user authenticates with a password or private key.
The Snowflake network policy allows Applied to connect.

Applied’s Snowflake resource form requires either a password or a private key.

Get Snowflake connection details

Snowflake connection details are available in Snowsight and through SQL.

In Snowsight, use the account selector or Connect a tool to Snowflake to find the account identifier and connection settings.

Useful SQL checks include:


SELECT CURRENT_ACCOUNT(), CURRENT_USER(), CURRENT_ROLE();
SELECT CURRENT_WAREHOUSE(), CURRENT_DATABASE(), CURRENT_SCHEMA();

Ask your Snowflake admin for the exact role, warehouse, database, and schema Applied should use.

Configure Snowflake privileges

Grant privileges to a role, then grant that role to the Applied user.

For read-only workflows, the role usually needs:

USAGE on the warehouse.
USAGE on the database.
USAGE on the schema.
SELECT on the specific tables or views Applied should query.

For write workflows, add only the needed privileges, such as INSERT, UPDATE, DELETE, or TRUNCATE on specific objects.

Connect Snowflake in Applied

Open Connectors.
Click New.
Choose Snowflake.
Choose the direct database credentials setup, not Hosted MCP.
Enter the account identifier.
Enter the username.
Enter either the password or the PEM private key.
Enter the warehouse, database, schema, and optional role.
Create the connection.

Validate the connection

After setup:

Run a harmless query such as SELECT 1.
Run one read-only query against an approved test table or view.
Confirm the query uses the expected warehouse, database, schema, and role.
If write access is enabled, test against a non-production table first.

Common issues

Authentication fails

Confirm the username and password or private key match the Snowflake user. If using key-pair authentication, make sure the public key is assigned to the user in Snowflake.

Queries fail with permission errors

Review the role’s warehouse, database, schema, and object privileges.

Applied connects to the wrong account

Check the account identifier. Snowflake account identifiers can include organization and account names or region-specific locator formats.