Summation queries Snowflake using a username and password, scoped to a warehouse and role you specify.Documentation Index
Fetch the complete documentation index at: https://docs.summation.com/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll need
Click onView account details link from the menu as seen below:

Config File tab on the Account Details modal, we need the following fields from the code block displayed there

- A Snowflake account identifier, that would be of the form
<orgname>-<account_name> - A warehouse Summation can use to run queries.
- A username and password that can be used to authenticate
Form fields
| Field | Required | Stored as | Notes |
|---|---|---|---|
| Account Identifier | Yes | Config | e.g. myorg-myaccount. Don’t include .snowflakecomputing.com. See Finding the organization and account name in the Snowflake docs. |
| Warehouse | Yes | Config | The compute warehouse, e.g. COMPUTE_WH. See Overview of warehouses. |
| Role | Optional | Config | Snowflake role to assume. Defaults to the user’s default role if blank. See Overview of access control. |
| Username | Yes | Config | Snowflake login name. |
| Password | Yes | Secret |
Recommended Best Practice (Optional)
Setup SQL
Run asACCOUNTADMIN (or another role with sufficient privileges):
Adding datasets
After saving the connection, browse the tree of databases and schemas in the dataset picker and select tables or views. Each dataset’s source reference looks like:Common problems
| Error or symptom | Likely cause |
|---|---|
Authentication failed | Wrong username or password, or the user is locked or password-expired. |
Object does not exist or not authorized | The role can’t see the schema or table. Re-check the GRANT statements. |
Warehouse not found | Warehouse name is case-sensitive in some accounts — match casing exactly. |
| Login blocked by MFA | Summation uses password auth. Use a service user that doesn’t require MFA. |