Integrate the Snowflake API.Caddi writes and runs the integration for you.
Snowflake has a REST API (the Snowflake SQL API). Any Snowflake account can use the SQL API. The integration signs in as a Snowflake user or service user, and what it can query or change is set by that user's role and grants.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code.
Register an app, store Snowflake credentials, refresh tokens.
Connect your Snowflake account once. Caddi holds the connection.
The job doesn't stop at Snowflake.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Snowflake API only reaches Snowflake.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves. The SQL API does not support the PUT and GET commands, so staging local files goes through a driver or connector instead. Transactions and USE or ALTER SESSION run only inside a multi-statement request.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the Snowflake API gives you
- Type
- REST (JSON)
- Authentication
- OAuth, key-pair authentication (a signed JWT), programmatic access tokens, or workload identity federation
- Who can get access
- Any Snowflake account can use the SQL API. The integration signs in as a Snowflake user or service user, and what it can query or change is set by that user's role and grants.
- What it covers
- Submitting SQL statements, checking their status, cancelling them and fetching results in partitions; standard queries and most DDL and DML, including managing users, roles and tables.
- Worth knowing
- The SQL API does not support the PUT and GET commands, so staging local files goes through a driver or connector instead. Transactions and USE or ALTER SESSION run only inside a multi-statement request.
Official docs: docs.snowflake.com. Checked October 2026. Vendors change access terms, so confirm with Snowflake before you build.
When to build the Snowflake integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Snowflake work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Snowflake API for
Warehouse to CRM sync
Caddi queries Snowflake on a schedule and writes matched results onto the right Salesforce or HubSpot records.
Scheduled report delivery
Caddi runs the query, builds the sheet and posts it to the team channel before the weekly meeting.
Tool data into the warehouse
Caddi pulls new records from the systems your firm runs on and writes them to tables in Caddi's own Snowflake schema.
Threshold alerts
Caddi runs a check query and alerts the owner in Teams when a number crosses the line you set.
Everything Caddi does with Snowflake.
Snowflake API questions
Does Snowflake have an API?
Yes. Snowflake has a REST API (the Snowflake SQL API), authenticated with OAuth, key-pair authentication (a signed JWT), programmatic access tokens, or workload identity federation. The official documentation is at https://docs.snowflake.com/en/developer-guide/sql-api/intro.
How do I get access to the Snowflake API?
Any Snowflake account can use the SQL API. The integration signs in as a Snowflake user or service user, and what it can query or change is set by that user's role and grants.
Can I connect Snowflake to my other tools without writing code against its API?
Yes. With Caddi you show the Snowflake task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Snowflake and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate Snowflake with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Snowflake is reviewed before it runs in production, and every run is logged.