--- title: "Connect Snowflake for Two-Way Sync: No Certificates" description: "Is connecting Snowflake as easy as a CRM? Yes. Generate an access token, paste it in, and sync both ways. No certificate files, no key-pair rotation to manage." canonical: https://www.stacksync.com/blog/connect-snowflake-two-way-sync-no-certificates last_modified: 2026-07-20 --- # How to Connect Snowflake for Two-Way Sync (No Certificates Needed) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md A practical setup guide for teams asking whether Snowflake is as easy to connect as HubSpot or as fussy as a system that needs certificates. The answer is closer to NetSuite: you generate an access token, paste the account URL and warehouse, and the schema is read for you. Covers what actually makes a warehouse feel hard, token versus certificate auth, the three-step connection, and how it compares to a one-click CRM. Author Ruben Burdin · Founder & CEO Published July 20, 2026 Read time 9 min read ARTICLE One question comes up almost every time a team looks at adding [Snowflake](https://www.stacksync.com/connectors/snowflake) to a sync: is it as painless as connecting a CRM, or is it going to be certificates and support tickets? People have been burned by integrations that ask for TLS certificates, key-pairs, and a rotation schedule, and they want to know which kind of setup they are signing up for before they start. The short answer is that connecting Snowflake sits closer to connecting NetSuite than to any certificate ordeal. You generate an access token, paste in the account URL and warehouse, and the schema is read for you. This guide walks through what actually makes a warehouse feel hard to connect, why a token beats a certificate, the three steps it takes, and how the whole thing compares to a one-click CRM. ![Connecting Snowflake in three steps: generate an access token, paste the account URL and warehouse once, then sync both ways with your CRM](https://www.stacksync.com/images/blog-highlights/connect-snowflake-summary.webp) The setup below assumes a managed sync platform such as Stacksync connecting Snowflake to a CRM or database. For the pairing most teams ask about first, see the [HubSpot to Snowflake sync guide](https://www.stacksync.com/blog/hubspot-snowflake-sync-instant-bidirectional-integration). This post stays on the one thing that decides whether people dread the project: how you connect. ## What actually makes a warehouse feel hard to connect The fear is rarely about Snowflake itself. It is about the memory of an integration that needed a certificate. Certificate and key-pair authentication is not exotic, but it carries a chain of small chores: generate a key-pair, register the public key, store the private key somewhere the tool can reach it, and then re-issue and redeploy the whole thing when it expires. Each step is minor, and together they are why a connection that should take an afternoon slips into next week. The other thing that makes a warehouse feel heavy is uncertainty about access. People worry they will have to hand over broad admin rights. In practice you grant a scoped role: a user, a warehouse for compute, and grants on the specific databases and schemas the sync should touch. That is a normal Snowflake permission, reviewable and revocable like any other, not a master key. ## Snowflake auth is a token, not a certificate Here is the part that settles the question. Stacksync connects to Snowflake with an access token. You create a user in Snowflake, generate a token against it, and hand that token to Stacksync once. There is no certificate file to move around and nothing to rotate on a calendar. If you have connected NetSuite with a token-based login, this will feel familiar. ![Comparison of Snowflake authentication: a certificate or key-pair means generating, storing, and rotating keys, while an access token means creating a user, pasting three values, and connecting](https://www.stacksync.com/images/blog-diagrams/connect-snowflake-auth-compare.webp) *Certificate auth is a chain of chores. A token is three values pasted once.* The difference is not cosmetic. Token auth removes the two steps that cause most of the delay: storing a private key where a service can safely read it, and remembering to re-issue it before it expires. With a token, the connection you set up today keeps working, and when you want to cut it off you revoke the token in Snowflake. That is the whole lifecycle. ## What connecting Snowflake actually looks like Concretely, connecting Snowflake is three steps, and only the first happens inside Snowflake. 1. 01 Create a user and access token In Snowflake, create a user for the sync, grant it the databases, schemas, and warehouse it needs, and generate an access token. 2. 02 Paste three values into Stacksync Give the account URL, the warehouse to run compute on, and the token. That is the entire credential. 3. 03 Let it read the schema Stacksync reads the tables and fields you granted, lists them, and you pick what to sync and in which direction. ![Sequence diagram of connecting Snowflake: you create a user and access token, paste the account URL, warehouse, and token into Stacksync, it authenticates and reads the schema, and the first two-way sync begins](https://www.stacksync.com/images/blog-diagrams-mermaid/connect-snowflake-auth-sequence.webp) *The full handshake: token in, schema read, first sync running. No certificates in the loop.* Once the schema is read, the rest is mapping, not plumbing. You choose the tables, match the fields, and set direction per object. A record change in Snowflake or in the connected system then flows through in real time. For the pattern of deciding which system holds the truth once both are connected, see [warehouse versus CRM as your source of truth](https://www.stacksync.com/blog/data-warehouse-vs-crm-source-of-truth). ## How it compares to a one-click CRM connection A CRM like HubSpot connects with an OAuth pop-up: click, approve, done. Snowflake is one honest step past that, because a warehouse does not do a consumer-style OAuth flow. But the gap is a single token, not a category of pain. Here is the side by side. | | One-click CRM (OAuth) | Certificate / key-pair | Snowflake with a token | | --- | --- | --- | --- | | How you authenticate | OAuth pop-up | Generate and register keys | Create a user, generate a token | | What you store | Nothing, it is handled | A private key, safely | One token, pasted once | | Rotation | None | Re-issue before expiry | Revoke when you choose | | Time to connected | Seconds | Hours to days | Minutes | | Direction | Two-way, per object | Depends on the tool | Two-way, per object | Snowflake connects with a token, so setup lands minutes away from a one-click CRM, not days. The practical takeaway: if the thing holding up your Snowflake project is a worry about certificates, that worry does not apply here. The connection is a token and three fields, and you spend your real time on the interesting decision, which is what to sync and which way it should flow. ## What you can do once Snowflake is connected Connecting is the start, not the point. Once Snowflake is in, the same platform lets you keep it in two-way sync with the tools your teams live in, and stack more systems into the flow later. Two common next moves: - **Keep Snowflake and a CRM in agreement.** Map contacts, companies, and deals so warehouse data and CRM data stop disagreeing, with the direction set per object. - **Chain more systems in.** Land CRM data in a database, model it in Snowflake, and push the clean version back out, all as stacked syncs. See [multi-hop sync](https://www.stacksync.com/blog/multi-hop-sync-hubspot-database-snowflake) for that pattern. Because direction and scope are set per object, you can start with one table as a proof of concept and expand without rebuilding. The connection you make on day one is the same one that carries the full rollout. ## The connection is the easy part So, is connecting Snowflake as easy as a CRM? Nearly. It is a token instead of a pop-up, and everything people fear about certificates simply is not in the path. Generate the token, paste three values, and the schema is yours to map. If Snowflake has been sitting on your roadmap because the setup felt like a project, it is smaller than you think. To see a token-based Snowflake connection and a two-way sync on your own account, [book a demo](https://www.stacksync.com/book-a-demo). FAQ ## Frequently asked questions Is connecting Snowflake as easy as connecting a CRM like HubSpot? It is close. A one-click CRM connection is an OAuth pop-up, and Snowflake is a step past that but not by much. You create a user and an access token in Snowflake, then paste the account URL, warehouse, and token into Stacksync. There is no certificate file to generate and no key-pair to rotate, so the setup feels closer to connecting NetSuite than to wrestling with TLS certificates. Does connecting Snowflake require a certificate or key-pair? No. Stacksync authenticates to Snowflake with an access token. You generate the token against a Snowflake user, give it to Stacksync once, and the connection is live. There are no certificate files to store, distribute, or re-issue when they expire, which is the part of certificate and key-pair auth that usually eats time. How long does it take to connect Snowflake? Minutes, once you have the token. The work is three short steps: create a user and access token in Snowflake, paste the account URL, warehouse, and token into Stacksync, and let it read your schema. After that every table and field is listed and ready to map, so you spend your time choosing what to sync rather than fighting the connection. How does two-way sync work with Snowflake? Two-way, and you set the direction per object. You can read from Snowflake, write to it, or keep specific tables in full two-way sync with a CRM or database. Direction is a choice you make table by table, not a single global setting, so an analytics table can stay read-only while an operational table syncs both ways. What access does Stacksync need inside Snowflake? A user with an access token and the right grants on the databases, schemas, and warehouse you want to sync. You control the scope: grant only the objects the sync should touch and the warehouse it should run compute on. Because access is a normal Snowflake grant, your team can review and revoke it the same way it manages any other role. Can I connect Snowflake and HubSpot in the same sync? Yes. Connect Snowflake with a token and HubSpot with its OAuth flow, then map the objects you want kept in step. A new HubSpot contact can create a matching row in Snowflake, and a change in Snowflake can update HubSpot, with the direction set per object. This is the common shape for teams that want warehouse data and CRM data to agree. Is connecting Snowflake different from connecting a database like Postgres? The idea is the same, the auth differs slightly. Postgres connects with host, port, and credentials, while Snowflake connects with an account URL, warehouse, and access token. Both skip the certificate plumbing people worry about, and both expose their schema to Stacksync so you map tables and fields rather than hand-writing a connection. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Snowflake integrations](https://www.stacksync.com/connectors/snowflake) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [platform Warehouse data flows](https://www.stacksync.com/data-warehouse) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) - [Warehouse data flows guides Choose between ingestion, reverse ETL, and operational write-back for warehouse data.](https://www.stacksync.com/blog#topic-data-warehouse-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering NetSuite Two-Way Snowflake Sync: Enterprise Implementation Framework 9 min read read](https://www.stacksync.com/blog/netsuite-two-way-snowflake-sync-enterprise-implementation-framework) [Data engineering GitHub Into Snowflake Is Solved. The Trip Back Is Not. 13 min read read](https://www.stacksync.com/blog/two-way-sync-github-snowflake) [Data engineering Two-Way Sync Solutions Between Zendesk and Snowflake 8 min read read](https://www.stacksync.com/blog/two-way-sync-solutions-zendesk-snowflake) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)