connector

Snowflake

Cloud data warehouse with separate storage and compute.

Connection fields

Field	Required	Description
`account`	Yes	Account identifier (e.g. "xy12345" or "xy12345.us-east-1"), used to build https://{account}.snowflakecomputing.com.
`user`	Yes	Snowflake username.
`private_key`	No	PEM-encoded RSA private key (PKCS#1 or PKCS#8) for key-pair auth. Not marked required by the form, but connecting fails without it — see the note below.
`warehouse`	No	Warehouse to run queries on.
`database`	Yes	Database to connect to. Required for schema introspection.
`schema`	No	Default schema. Defaults to "PUBLIC".
`role`	No	Role to assume for the session.

Snowflake's SQL REST API v2 (what this connector uses) only supports OAuth, key-pair JWT, or programmatic access tokens — never plain username/password. private_key is effectively required: register the matching public key on the Snowflake user with ALTER USER ... SET RSA_PUBLIC_KEY = '...', then paste the private key PEM here.

Example configuration

{
  "account": "xy12345.us-east-1",
  "user": "ARCODASH_READER",
  "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----",
  "warehouse": "COMPUTE_WH",
  "database": "ANALYTICS",
  "schema": "PUBLIC"
}

Caveats

Not yet live-verified against a real Snowflake account — the JWT signing is tested against a real RS256 round trip, but DATE/TIMESTAMP decoding is implemented from Snowflake's documented response format rather than confirmed against a live query result.
The key-pair JWT is valid for under an hour and is rebuilt on every request, so there's no persistent session to worry about expiring mid-query.