Skip to content
Data warehouse · Two-way sync platform

Snowflake connector for two-way sync.

Keep Snowflake and your business systems aligned with Stacksync. Sync Standard tables (including Permanent, Transient and Temporary tables) within the connector’s object and field requirements, with two-way sync for eligible records.

  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Snowflake

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Record types

Snowflake objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Standard tables (including Permanent, Transient and Temporary tables)
Supported
Views (including materialized and non-materialized views)
Coming soon
External tables
Not supported

Read the Snowflake object and setup guide

Connection setup

Snowflake connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Account access
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITYADMIN and ACCOUNTADMIN roles
How changes are detected
The Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Sync directions

  • Read data Documented
  • Write data Documented
SnowflakeStacksync setup guide
Setup prerequisites for your administrator
  • Have an administrator run the documented setup script for a dedicated service user and role with RSA key-pair authentication.
  • Specify the correct warehouse, database, schema, and account identifier. Verify table grants for the service role.
  • Existing tables need a non-null primary key with a UUIDSTRING() default, as specified in the connector guide.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Snowflake integration.

Choose the dataset grain, stable business key, and model refresh schedule. If results update an application, restrict writes to fields owned by the analytical process.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
SnowflakeSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
For existing tables, follow the documented non-null primary key with a UUID_STRING() default. Keep the external application key separate from this generated local identifier.
Load related records in the right order
Choose a supported table and verify the warehouse, database, schema, and service-role grants. External tables and ordinary/materialized views are excluded by the current support matrix.

Mapping checks by record type

Standard tables (including Permanent, Transient and Temporary tables)

Check the object requirements below

Identity
Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema.
Fields to consider
Local record key · External application ID · Required business fields · Parent record references
Related records to resolve first
Choose a supported table and verify the warehouse, database, schema, and service-role grants. External tables and ordinary/materialized views are excluded by the current support matrix.
Test before going live
Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Snowflake integration in four steps.

The destination can trace a value to its source dataset and computation time, and a model refresh does not create duplicate operational records.

View the four setup tests and expected results

  1. Verify Snowflake connectivity and database privileges

    Use the documented setup from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture.

    Expected result: The approved role can access the selected data and capture later changes without depending on an administrator’s personal session.

  2. Validate the service role against the selected table

    Use the configured RSA-authenticated service user to access a test table, then exercise the permitted create/update path with its generated key.

    Expected result: The correct table is accessible, the key rule is met, and geography/geometry fields are excluded from the mapped dataset.

  3. Test writes in the directions you need

    Select one eligible Snowflake object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Snowflake records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Snowflake integration.

Diagnose record matching, delayed changes, and rejected operations
Authentication works but a table cannot participate
Check role grants and the selected object type. A Snowflake object being queryable does not make it supported by the connector.
The first load looks correct but later results differ
The Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Snowflake object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Snowflake workflow with an engineer

Snowflake integration guides

FAQ

Snowflake connector FAQ

How should I plan an integration with Snowflake?

Eligible tables, generated keys, and the dedicated service role determine the supported dataset. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Snowflake connector write changes back?

Stacksync supports reads and writes for eligible Snowflake objects. Check the selected fields, account permissions, and the other system’s connector. Use the configured RSA-authenticated service user to access a test table, then exercise the permitted create/update path with its generated key.

Which identifiers should I preserve for Snowflake data?

For existing tables, follow the documented non-null primary key with a UUIDSTRING() default. Keep the external application key separate from this generated local identifier.

Which related records should I load first for Snowflake?

Choose a supported table and verify the warehouse, database, schema, and service-role grants. External tables and ordinary/materialized views are excluded by the current support matrix.

What should I check if Snowflake data is missing or delayed?

Check role grants and the selected object type. A Snowflake object being queryable does not make it supported by the connector.

What will we cover in a Snowflake integration demo?

Start with one workflow and a sample record from Standard tables (including Permanent, Transient and Temporary tables). We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Explore Snowflake connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

295 integration guides

CRM · 46

ERP · 43

Database · 50

Data warehouse · 29

Business productivity · 41

Accounting and finance · 17

AI · 5

Analytics · 7

Communications · 5

Developer tools · 11

E-commerce · 8

Human resources · 14

Marketing · 9

Security and identity · 6

Storage · 4

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started