Snowflake
Snowflake integration
Data PlatformAvailable
BRAIAN connects to Snowflake through Snowflake SQL API, key-pair authentication. Agents can warehouse queries, role-scoped table access and result set retrieval. Every action is scoped by the permissions granted to the integration and executed under a versioned policy. Each one is recorded in the audit log with the agent, timestamp and record touched.
What can BRAIAN do?
Agents run queries against Snowflake under a dedicated role and receive only the result set a process needs. No bulk extraction takes place: the data stays where it is governed.
| Capability | Agent | Read or write |
|---|---|---|
| Warehouse queries | All agents | Read |
| Role-scoped table access | All agents | Read |
| Result set retrieval | All agents | Read |
How does it connect?
- Connection method
- Snowflake SQL API, key-pair authentication
- Credential
- A Snowflake service user authenticated with an RSA key pair; the private key is held in the secrets store.
Credentials are held in an encrypted secrets store. BRAIAN never stores end-user passwords.
Which permissions are required?
- role-based grantsA dedicated role holds USAGE on the warehouse and SELECT on the specific schemas required.
Permissions are requested at the minimum scope the configured processes require. Unused scopes are not granted.
Which processes use it?
Processes that run on this connection, and the domains they belong to.
Expense audit
Third-party due diligence
Data access review
Used across every business domain.
How do you revoke access?
Access is revoked in Snowflake itself — by disabling the credential or removing the granted scopes — or in BRAIAN by disconnecting the integration. Processes already running stop at their next call to Snowflake and are held for review rather than completed with partial data; the interruption and the state of each process are recorded in the audit log.
FAQ
Does BRAIAN store data from Snowflake?
BRAIAN reads what a process needs, when it needs it. Records retrieved from Snowflake are held only for the duration of the process and in the audit trail of the actions taken; Snowflake remains the system of record.
What happens if the connection fails mid-process?
The process stops at the failed step and is held for review. Nothing is written twice: completed writes stay recorded in the audit log and the remaining steps resume only once the connection is restored.
Can permissions be scoped per agent?
Yes. Scopes are defined per agent, not per system, so one agent can read while another cannot, on the same connection to Snowflake.
