Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Keep supported Snowflake and Supabase records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Set this up from Claude or ChatGPT
Example workflow
Validate the selected objects and operations even where connector-level direction is documented.
Starting eventA selected source table needs an operational replica, a reporting projection, or a migration copy.
Choose actual tables in Snowflake and Supabase and compare their schemas and record types.
Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.
Plan two-way sync around connector support and your update rules; use a source-to-destination copy for read-only records. Keep source views, aggregate outputs, and writable base tables distinct.
What to verifyCounts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.
Review records and field ownershipAI assistant
Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.
Server URL
https://mcp.stacksync.com/mcp codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksyncComplete the browser sign-in with your Stacksync account, then start a new Codex session.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcpOpen Claude Code, run /mcp, select stacksync and complete the browser sign-in.
Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.
Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.
Create a two-way sync between my Snowflake and Supabase.
You can also ask for workflows and AI agents (Genies) that use Snowflake and Supabase. The assistant checks what each app supports, for example:
New to Stacksync? Create an account first, then sign in from your assistant.
Mapping essentials
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
Choose the tables you need in Snowflake and Supabase, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.
Why teams connect Snowflake and Supabase
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Snowflake and Supabase workflow to test, define what success looks like, and decide who handles failed updates.
Land CRM and ERP records in Snowflake continuously so BI reflects business systems without nightly batch ETL
Activate modeled Snowflake tables by syncing scores and attributes back into CRM fields sales can act on
Sync application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
Mirror billing and subscription records into Supabase tables the application can join directly
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Supported. Confirm field permissions and sync direction. |
| Coming soon. Confirm field permissions and sync direction. |
| Not supported. Confirm field permissions and sync direction. |
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | Snowflake | Supabase |
|---|---|---|
| Integration interface | SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API | PostgreSQL connection through the Supabase IPv4-compatible Transaction Pooler |
| Authentication | Dedicated Snowflake service user + role with RSA key-pair authentication | Postgres database credentials entered in the secure Stacksync connection form |
| Change detection | The saved Stacksync guide does not specify the change-detection mechanism. | Postgres connector requirements apply. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-10-20. Check the linked guides for current account and record requirements.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Setup guides: Authorize Snowflake
Setup guides: Authorize SupabasePostgres connectorRequired Postgres permissions
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Snowflake and Supabase planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Choose the tables you need in Snowflake and Supabase, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.
Choose your tables and update rules before the integration method. A live application copy, a reporting table, and a one-time migration need different handling for updates, history, deletes, and reconciliation.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A selected source table needs an operational replica, a reporting projection, or a migration copy.
Expected result: Counts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.
If it fails: Compare current source state, key mapping, and destination constraints before retrying. Reconcile the backlog after any schema or permission change.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
Use an actual Snowflake and Supabase table. Compare key uniqueness, nulls, decimal precision, timezone conversions, and counts within identical filters.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Check the Snowflake and Supabase connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in Supabase. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesPostgres connector requirements apply. If logical replication permissions are unavailable, the documented Postgres Heroku connector provides a trigger-based alternative, including for non-Heroku databases.
Apply updatesSelected writable fields update in Snowflake. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects Snowflake and Supabase with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have an administrator run the documented setup script for a dedicated service user and role with RSA key-pair authentication. Connect the Supabase database through the Postgres connection flow using an IPv4-compatible Transaction Pooler connection string. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Choose the tables you need in Snowflake and Supabase, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.
Choose your tables and update rules before the integration method. A live application copy, a reporting table, and a one-time migration need different handling for updates, history, deletes, and reconciliation.
Further reading
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 581 integrations listed for Snowflake and Supabase.
Next step
Walk through your Snowflake and Supabase records, field mappings, and requirements with an integration engineer.
