Faster dev cycles
Ship Snowflake integrations quickly with low-code workflows.
Snowflake Connector
Embed Snowflake into your SaaS to run queries, load data and build governed customer automations. Use Cyclr’s low-code builder to publish in-app workflows that run SQL, trigger Snowpipe loads and surface results to end users.
Governed MCP tools
Publish vetted integrations as governed customer-facing tools.
Scale data workloads
Automate Snowpipe loads and scale ingestion pipelines.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Cyclr’s Snowflake connector lets product and engineering teams embed data workflows directly inside a multi-tenant SaaS product. Build in-app reporting, automate ETL loads with Snowpipe, sync customer records to a data warehouse and expose vetted integrations as governed MCP tools for customers to enable and configure.
PRODUCT USE CASES
Top Use Cases for Snowflake Integrations
Use Cyclr to build multi-tenant data features with Snowflake: run live queries for in-app analytics, automate file ingestion with Snowpipe, synchronize customer data to a shared warehouse and expose governed query-and-load automations to customers.
In-app analytics and dashboards
Run parameterized SQL queries in Snowflake and display live results inside your product per customer.
Automate file ingestion with Snowpipe
Trigger Snowpipe loads from cloud storage events to ingest customer files automatically.
Sync customer data to a central warehouse
Periodically push customer records from your app into Snowflake tables for analytics and BI.
ORCHESTRATION
How Snowflake works with Cyclr
Cyclr sits between your SaaS product and Snowflake to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Snowflake
Snowflake processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Snowflake methods you can orchestrate through Cyclr.
Table6
Add Table Rows
ActionAdd rows to a table.
Update Bulk Table Rows
ActionUpdate multiple rows in a table.
List Table Rows
ActionList rows in a table.
Add Bulk Table Rows
ActionAdd multiple rows to a table.
Delete Table Rows
ActionDelete rows from a table.
Update Table Rows
ActionUpdate rows in a table.
Databases1
List Databases
ActionList all accessible databases.
Tables2
List Tables
ActionList all accessible tables.
Get Table Description
ActionGet the description of the requested table.
Schemas1
List Schemas
ActionList all accessible schemas.
View1
List View Rows
ActionList rows in a view.
Warehouses1
List Warehouses
ActionList all accessible warehouses.
Statements1
Get Statement Status
ActionGet the status of a statement.
Views1
List Views
ActionList all views.
TECHNICAL DETAILS
Snowflake integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Snowflake integrations in Cyclr.
API and authentication
- API host
https://.snowflakecomputing.com (account-specific API endpoint)- Authentication
- Key-pair JWT, OAuth, programmatic access tokens and workload identity federation
- Credentials
Account identifier, username, private key (or OAuth token), optional role and warehouse.
- Method categories
Execute SQL, fetch results, load data via Snowpipe, manage users and metadata.
Pagination and rate limits
Pagination
Large result sets are paginated. Fetch additional pages using the Link header URLs (rel=”next”,”first”,”last”).
Rate limits
Snowflake enforces account-level rate limits and returns 429 on excess requests; check account usage views for configured policies.
IMPLEMENTATION
Authentication at a glance
Snowflake APIs accept key-pair JWTs, OAuth tokens, programmatic access tokens or workload identity federation; auth method depends on the specific API (SQL API, Snowpipe) and account configuration.
- Authentication method
- Key-pair JWT, OAuth, programmatic access tokens and workload identity federation
- Credential required
Account identifier, username, private key (or OAuth token), optional role and warehouse.
Before you begin:
View setup guideRequires assigning a public key or OAuth setup and correct user privileges; use account-specific endpoint.
COMMON QUESTIONS
Frequently asked questions
The connector supports key-pair JWTs, OAuth tokens and programmatic access tokens. Exact options depend on the Snowflake API you use and account configuration.
Yes. Use the SQL API to submit statements and fetch results. Ensure each tenant uses credentials scoped to their data and implement role-based access controls.
Snowflake returns the first page in the response body and provides Link headers with rel=”next”,”first”,”last” to fetch remaining pages.
Snowflake does not expose a generic webhook API. For ingestion, Snowpipe integrates with cloud storage event notifications such as AWS SNS or Azure Event Grid.
KEEP EXPLORING
Related resources and connectors
Documentation
How to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductWhat is iPaaS?
Read more →ProductMCP PaaS
Read more →Related connectorAmazon S3
Related Databases connector for customer-facing integration workflows.
Related connectorGoogle BigQuery
Related Databases connector for customer-facing integration workflows.
Related connectorMicrosoft Azure DevOps
Related Databases connector for customer-facing integration workflows.