--- title: "Google Cloud SQL connector | Stacksync" description: "Google Cloud SQL integration planning: Instances, Databases and Schemas. Compatibility, identity, dependencies, and validation." canonical: https://www.stacksync.com/connectors/google-cloud-sql last_modified: 2026-09-15 --- Database · Two-way sync platform # Google Cloud SQL integration. > 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 Connect your Google Cloud SQL workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Instances, Databases and Schemas. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Instances** - **Databases** - **Schemas** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=google-cloud-sql) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Google Cloud SQL records to discuss. These Google Cloud SQL record examples help scope a technical review. They are not a list of verified Stacksync operations. Instances Identify this record type and the operation you need to review with Stacksync. Databases Identify this record type and the operation you need to review with Stacksync. Schemas Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Tables Identify this record type and the operation you need to review with Stacksync. Rows Identify this record type and the operation you need to review with Stacksync. Views Identify this record type and the operation you need to review with Stacksync. Connection setup ## Google Cloud SQL connection requirements. Review Google Cloud SQL access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Google Cloud SQL account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Google Cloud SQL, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Google Cloud SQL integration. Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Google Cloud SQL **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve 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 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. Load related records in the right order List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### Mapping checks by record type #### Instances, Databases and Schemas Confirm object support with Stacksync 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 List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. 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)](https://www.stacksync.com/downloads/sync-planning/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 Google Cloud SQL integration in four steps. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. ### View the four setup tests and expected results 1. ### Verify Google Cloud SQL connectivity and database privileges After confirming an implementation path, validate the selected access method 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. ### Test record matching for Instances, Databases and Schemas Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record. **Expected result:** Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. 3. ### Test the operation your workflow needs Review one Google Cloud SQL record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **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 For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **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](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Google Cloud SQL integration. ### Diagnose record matching, delayed changes, and rejected operations A Google Cloud SQL record appears under the wrong destination record 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. List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Google Cloud SQL implementation’s change-detection method for Instances, Databases and Schemas. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Google Cloud SQL 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](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Google Cloud SQL workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=google-cloud-sql) ## Google Cloud SQL integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Google Cloud SQL connector FAQ ### How should I plan an integration with Google Cloud SQL? Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Google Cloud SQL connector write changes back? Write-back support is not established for this connection. Review the Google Cloud SQL records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Google Cloud SQL data? 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. ### Which related records should I load first for Google Cloud SQL? List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### How do I validate Google Cloud SQL changes after the initial load? Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. ### What will we cover in a Google Cloud SQL integration demo? Start with one workflow and a sample record from Instances, Databases and Schemas. 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. AI assistant ## Set up Google Cloud SQL from Claude or ChatGPT 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. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### 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. 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](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Google Cloud SQL and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Google Cloud SQL. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Google Cloud SQL record changes.” - “Create a Genie that answers questions about our Google Cloud SQL data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Google Cloud SQL connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Google Cloud SQL and Rockset](https://www.stacksync.com/integrations/google-cloud-sql-and-rockset) - [Braze and Google Cloud SQL](https://www.stacksync.com/integrations/braze-and-google-cloud-sql) - [Google Cloud SQL and Google Sheets](https://www.stacksync.com/integrations/google-cloud-sql-and-google-sheets) - [ClickHouse and Google Cloud SQL](https://www.stacksync.com/integrations/clickhouse-and-google-cloud-sql) - [Google Cloud SQL and IBM AS/400](https://www.stacksync.com/integrations/google-cloud-sql-and-ibm-as400) - [Google Cloud SQL and Supabase](https://www.stacksync.com/integrations/google-cloud-sql-and-supabase) - [Google Cloud SQL and PostgreSQL](https://www.stacksync.com/integrations/google-cloud-sql-and-postgresql) - [Amazon Redshift and Google Cloud SQL](https://www.stacksync.com/integrations/amazon-redshift-and-google-cloud-sql) ### CRM · 30 - [Google Cloud SQL and 6sense](https://www.stacksync.com/integrations/6sense-and-google-cloud-sql) - [Google Cloud SQL and Affinity](https://www.stacksync.com/integrations/affinity-and-google-cloud-sql) - [Google Cloud SQL and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-google-cloud-sql) - [Google Cloud SQL and Attio](https://www.stacksync.com/integrations/attio-and-google-cloud-sql) - [Google Cloud SQL and Chorusai](https://www.stacksync.com/integrations/chorusai-and-google-cloud-sql) - [Google Cloud SQL and Close](https://www.stacksync.com/integrations/close-and-google-cloud-sql) - [Google Cloud SQL and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-google-cloud-sql) - [Google Cloud SQL and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-google-cloud-sql) - [Google Cloud SQL and Freshsales](https://www.stacksync.com/integrations/freshsales-and-google-cloud-sql) - [Google Cloud SQL and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-google-cloud-sql) - [Google Cloud SQL and Gong](https://www.stacksync.com/integrations/gong-and-google-cloud-sql) - [Google Cloud SQL and Gorgias](https://www.stacksync.com/integrations/google-cloud-sql-and-gorgias) - [Google Cloud SQL and HubSpot](https://www.stacksync.com/integrations/google-cloud-sql-and-hubspot) - [Google Cloud SQL and Infor CRM](https://www.stacksync.com/integrations/google-cloud-sql-and-infor-crm) - [Google Cloud SQL and Insightly](https://www.stacksync.com/integrations/google-cloud-sql-and-insightly) - [Google Cloud SQL and Intercom](https://www.stacksync.com/integrations/google-cloud-sql-and-intercom) - [Google Cloud SQL and Kommo](https://www.stacksync.com/integrations/google-cloud-sql-and-kommo) - [Google Cloud SQL and Outreach](https://www.stacksync.com/integrations/google-cloud-sql-and-outreach) - [Google Cloud SQL and Pipedrive](https://www.stacksync.com/integrations/google-cloud-sql-and-pipedrive) - [Google Cloud SQL and Salesforce](https://www.stacksync.com/integrations/google-cloud-sql-and-salesforce) - [Google Cloud SQL and Salesloft](https://www.stacksync.com/integrations/google-cloud-sql-and-salesloft) - [Google Cloud SQL and SAP Sales Cloud](https://www.stacksync.com/integrations/google-cloud-sql-and-sap-sales-cloud) - [Google Cloud SQL and Seismic](https://www.stacksync.com/integrations/google-cloud-sql-and-seismic) - [Google Cloud SQL and Shopify](https://www.stacksync.com/integrations/google-cloud-sql-and-shopify) - [Google Cloud SQL and SugarCRM](https://www.stacksync.com/integrations/google-cloud-sql-and-sugarcrm) - [Google Cloud SQL and Veeva CRM](https://www.stacksync.com/integrations/google-cloud-sql-and-veeva-crm) - [Google Cloud SQL and Vtiger CRM](https://www.stacksync.com/integrations/google-cloud-sql-and-vtiger-crm) - [Google Cloud SQL and Xactly](https://www.stacksync.com/integrations/google-cloud-sql-and-xactly) - [Google Cloud SQL and Zoho CRM](https://www.stacksync.com/integrations/google-cloud-sql-and-zoho-crm) - [Google Cloud SQL and Zoho SalesIQ](https://www.stacksync.com/integrations/google-cloud-sql-and-zoho-salesiq) ### ERP · 24 - [Google Cloud SQL and Acumatica](https://www.stacksync.com/integrations/acumatica-and-google-cloud-sql) - [Google Cloud SQL and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-google-cloud-sql) - [Google Cloud SQL and Cin7](https://www.stacksync.com/integrations/cin7-and-google-cloud-sql) - [Google Cloud SQL and Dynamics 365 Business Central](https://www.stacksync.com/integrations/google-cloud-sql-and-microsoft-dynamics-365-business-central) - [Google Cloud SQL and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-google-cloud-sql) - [Google Cloud SQL and Infor LN](https://www.stacksync.com/integrations/google-cloud-sql-and-infor-ln) - [Google Cloud SQL and Infor M3](https://www.stacksync.com/integrations/google-cloud-sql-and-infor-m3) - [Google Cloud SQL and Linnworks](https://www.stacksync.com/integrations/google-cloud-sql-and-linnworks) - [Google Cloud SQL and Microsoft Dynamics GP](https://www.stacksync.com/integrations/google-cloud-sql-and-microsoft-dynamics-gp) - [Google Cloud SQL and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/google-cloud-sql-and-microsoft-dynamics-nav) - [Google Cloud SQL and NetSuite](https://www.stacksync.com/integrations/google-cloud-sql-and-netsuite) - [Google Cloud SQL and Odoo](https://www.stacksync.com/integrations/google-cloud-sql-and-odoo) - [Google Cloud SQL and Plex ERP](https://www.stacksync.com/integrations/google-cloud-sql-and-plex-erp) - [Google Cloud SQL and QAD ERP](https://www.stacksync.com/integrations/google-cloud-sql-and-qad-erp) - [Google Cloud SQL and Sage 100](https://www.stacksync.com/integrations/google-cloud-sql-and-sage-100) - [Google Cloud SQL and Sage 300](https://www.stacksync.com/integrations/google-cloud-sql-and-sage-300) - [Google Cloud SQL and Sage Intacct](https://www.stacksync.com/integrations/google-cloud-sql-and-sage-intacct) - [Google Cloud SQL and Sage X3](https://www.stacksync.com/integrations/google-cloud-sql-and-sage-x3) - [Google Cloud SQL and SAP](https://www.stacksync.com/integrations/google-cloud-sql-and-sap) - [Google Cloud SQL and SAP Business ByDesign](https://www.stacksync.com/integrations/google-cloud-sql-and-sap-business-bydesign) - [Google Cloud SQL and SAP Business One](https://www.stacksync.com/integrations/google-cloud-sql-and-sap-business-one) - [Google Cloud SQL and SAP S/4HANA](https://www.stacksync.com/integrations/google-cloud-sql-and-sap-s4hana) - [Google Cloud SQL and Syspro](https://www.stacksync.com/integrations/google-cloud-sql-and-syspro) - [Google Cloud SQL and TikTok Shop](https://www.stacksync.com/integrations/google-cloud-sql-and-tiktok) ### Database · 20 - [Google Cloud SQL and Airtable](https://www.stacksync.com/integrations/airtable-and-google-cloud-sql) - [Google Cloud SQL and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-google-cloud-sql) - [Google Cloud SQL and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-google-cloud-sql) - [Google Cloud SQL and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-google-cloud-sql) - [Google Cloud SQL and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-google-cloud-sql) - [Google Cloud SQL and Firebase](https://www.stacksync.com/integrations/firebase-and-google-cloud-sql) - [Google Cloud SQL and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-google-cloud-sql) - [Google Cloud SQL and IBM AS/400](https://www.stacksync.com/integrations/google-cloud-sql-and-ibm-as400) - [Google Cloud SQL and IBM Informix](https://www.stacksync.com/integrations/google-cloud-sql-and-ibm-informix) - [Google Cloud SQL and InfluxDB](https://www.stacksync.com/integrations/google-cloud-sql-and-influxdb) - [Google Cloud SQL and InterSystems IRIS](https://www.stacksync.com/integrations/google-cloud-sql-and-intersystems-iris) - [Google Cloud SQL and MongoDB](https://www.stacksync.com/integrations/google-cloud-sql-and-mongodb) - [Google Cloud SQL and MySQL](https://www.stacksync.com/integrations/google-cloud-sql-and-mysql) - [Google Cloud SQL and Neo4j](https://www.stacksync.com/integrations/google-cloud-sql-and-neo4j) - [Google Cloud SQL and PostgreSQL](https://www.stacksync.com/integrations/google-cloud-sql-and-postgresql) - [Google Cloud SQL and SAP ASE (Sybase)](https://www.stacksync.com/integrations/google-cloud-sql-and-sap-ase-sybase) - [Google Cloud SQL and SAP HANA](https://www.stacksync.com/integrations/google-cloud-sql-and-sap-hana) - [Google Cloud SQL and SQL Server](https://www.stacksync.com/integrations/google-cloud-sql-and-sql-server) - [Google Cloud SQL and Supabase](https://www.stacksync.com/integrations/google-cloud-sql-and-supabase) - [Google Cloud SQL and TimescaleDB](https://www.stacksync.com/integrations/google-cloud-sql-and-timescaledb) ### Data warehouse · 9 - [Google Cloud SQL and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-google-cloud-sql) - [Google Cloud SQL and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-google-cloud-sql) - [Google Cloud SQL and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-google-cloud-sql) - [Google Cloud SQL and BigQuery](https://www.stacksync.com/integrations/bigquery-and-google-cloud-sql) - [Google Cloud SQL and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-google-cloud-sql) - [Google Cloud SQL and Databricks](https://www.stacksync.com/integrations/databricks-and-google-cloud-sql) - [Google Cloud SQL and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-google-cloud-sql) - [Google Cloud SQL and Rockset](https://www.stacksync.com/integrations/google-cloud-sql-and-rockset) - [Google Cloud SQL and Snowflake](https://www.stacksync.com/integrations/google-cloud-sql-and-snowflake) ### Business productivity · 26 - [Google Cloud SQL and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-google-cloud-sql) - [Google Cloud SQL and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-google-cloud-sql) - [Google Cloud SQL and Asana](https://www.stacksync.com/integrations/asana-and-google-cloud-sql) - [Google Cloud SQL and Atlassian](https://www.stacksync.com/integrations/atlassian-and-google-cloud-sql) - [Google Cloud SQL and Braze](https://www.stacksync.com/integrations/braze-and-google-cloud-sql) - [Google Cloud SQL and Campfire](https://www.stacksync.com/integrations/campfire-and-google-cloud-sql) - [Google Cloud SQL and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-google-cloud-sql) - [Google Cloud SQL and Docusign](https://www.stacksync.com/integrations/docusign-and-google-cloud-sql) - [Google Cloud SQL and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-google-cloud-sql) - [Google Cloud SQL and Front](https://www.stacksync.com/integrations/front-and-google-cloud-sql) - [Google Cloud SQL and Gainsight](https://www.stacksync.com/integrations/gainsight-and-google-cloud-sql) - [Google Cloud SQL and GitHub](https://www.stacksync.com/integrations/github-and-google-cloud-sql) - [Google Cloud SQL and Google Sheets](https://www.stacksync.com/integrations/google-cloud-sql-and-google-sheets) - [Google Cloud SQL and Ironclad](https://www.stacksync.com/integrations/google-cloud-sql-and-ironclad) - [Google Cloud SQL and Klaviyo](https://www.stacksync.com/integrations/google-cloud-sql-and-klaviyo) - [Google Cloud SQL and Microsoft Dynamics 365](https://www.stacksync.com/integrations/google-cloud-sql-and-microsoft-dynamics-365) - [Google Cloud SQL and Monday](https://www.stacksync.com/integrations/google-cloud-sql-and-monday) - [Google Cloud SQL and NextGen Healthcare](https://www.stacksync.com/integrations/google-cloud-sql-and-nextgen-healthcare) - [Google Cloud SQL and Notion](https://www.stacksync.com/integrations/google-cloud-sql-and-notion) - [Google Cloud SQL and Quip](https://www.stacksync.com/integrations/google-cloud-sql-and-quip) - [Google Cloud SQL and ServiceMax](https://www.stacksync.com/integrations/google-cloud-sql-and-servicemax) - [Google Cloud SQL and ServiceNow](https://www.stacksync.com/integrations/google-cloud-sql-and-servicenow) - [Google Cloud SQL and Smartsheet](https://www.stacksync.com/integrations/google-cloud-sql-and-smartsheet) - [Google Cloud SQL and SysAid](https://www.stacksync.com/integrations/google-cloud-sql-and-sysaid) - [Google Cloud SQL and Wrike](https://www.stacksync.com/integrations/google-cloud-sql-and-wrike) - [Google Cloud SQL and Zendesk](https://www.stacksync.com/integrations/google-cloud-sql-and-zendesk) ### Accounting and finance · 13 - [Google Cloud SQL and Adyen](https://www.stacksync.com/integrations/adyen-and-google-cloud-sql) - [Google Cloud SQL and Anaplan](https://www.stacksync.com/integrations/anaplan-and-google-cloud-sql) - [Google Cloud SQL and BILL](https://www.stacksync.com/integrations/bill-and-google-cloud-sql) - [Google Cloud SQL and Braintree](https://www.stacksync.com/integrations/braintree-and-google-cloud-sql) - [Google Cloud SQL and Chargebee](https://www.stacksync.com/integrations/chargebee-and-google-cloud-sql) - [Google Cloud SQL and Coupa](https://www.stacksync.com/integrations/coupa-and-google-cloud-sql) - [Google Cloud SQL and Navan](https://www.stacksync.com/integrations/google-cloud-sql-and-navan) - [Google Cloud SQL and QuickBooks](https://www.stacksync.com/integrations/google-cloud-sql-and-quickbooks) - [Google Cloud SQL and Ramp](https://www.stacksync.com/integrations/google-cloud-sql-and-ramp) - [Google Cloud SQL and Recurly](https://www.stacksync.com/integrations/google-cloud-sql-and-recurly) - [Google Cloud SQL and Stripe](https://www.stacksync.com/integrations/google-cloud-sql-and-stripe) - [Google Cloud SQL and Workday](https://www.stacksync.com/integrations/google-cloud-sql-and-workday) - [Google Cloud SQL and Zuora](https://www.stacksync.com/integrations/google-cloud-sql-and-zuora) ### AI · 4 - [Google Cloud SQL and Autopilot](https://www.stacksync.com/integrations/autopilot-and-google-cloud-sql) - [Google Cloud SQL and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-google-cloud-sql) - [Google Cloud SQL and OpenAI](https://www.stacksync.com/integrations/google-cloud-sql-and-openai) - [Google Cloud SQL and Pinecone](https://www.stacksync.com/integrations/google-cloud-sql-and-pinecone) ### Analytics · 6 - [Google Cloud SQL and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-google-cloud-sql) - [Google Cloud SQL and Microsoft Power BI](https://www.stacksync.com/integrations/google-cloud-sql-and-microsoft-power-bi) - [Google Cloud SQL and Mixpanel](https://www.stacksync.com/integrations/google-cloud-sql-and-mixpanel) - [Google Cloud SQL and Pendo](https://www.stacksync.com/integrations/google-cloud-sql-and-pendo) - [Google Cloud SQL and Splunk](https://www.stacksync.com/integrations/google-cloud-sql-and-splunk) - [Google Cloud SQL and Tableau](https://www.stacksync.com/integrations/google-cloud-sql-and-tableau) ### Communications · 6 - [Google Cloud SQL and Aircall](https://www.stacksync.com/integrations/aircall-and-google-cloud-sql) - [Google Cloud SQL and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-google-cloud-sql) - [Google Cloud SQL and Gmail](https://www.stacksync.com/integrations/gmail-and-google-cloud-sql) - [Google Cloud SQL and Infobip](https://www.stacksync.com/integrations/google-cloud-sql-and-infobip) - [Google Cloud SQL and RingCentral](https://www.stacksync.com/integrations/google-cloud-sql-and-ringcentral) - [Google Cloud SQL and Zoom](https://www.stacksync.com/integrations/google-cloud-sql-and-zoom) ### Developer tools · 9 - [Google Cloud SQL and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-google-cloud-sql) - [Google Cloud SQL and Datadog](https://www.stacksync.com/integrations/datadog-and-google-cloud-sql) - [Google Cloud SQL and Jira](https://www.stacksync.com/integrations/google-cloud-sql-and-jira) - [Google Cloud SQL and JMS](https://www.stacksync.com/integrations/google-cloud-sql-and-jms) - [Google Cloud SQL and LDAP](https://www.stacksync.com/integrations/google-cloud-sql-and-ldap) - [Google Cloud SQL and New Relic](https://www.stacksync.com/integrations/google-cloud-sql-and-newrelic) - [Google Cloud SQL and Opsgenie](https://www.stacksync.com/integrations/google-cloud-sql-and-opsgenie) - [Google Cloud SQL and PagerDuty](https://www.stacksync.com/integrations/google-cloud-sql-and-pagerduty) - [Google Cloud SQL and RabbitMQ](https://www.stacksync.com/integrations/google-cloud-sql-and-rabbitmq) ### E-commerce · 6 - [Google Cloud SQL and Akeneo](https://www.stacksync.com/integrations/akeneo-and-google-cloud-sql) - [Google Cloud SQL and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-google-cloud-sql) - [Google Cloud SQL and EasyPost](https://www.stacksync.com/integrations/easypost-and-google-cloud-sql) - [Google Cloud SQL and Magento](https://www.stacksync.com/integrations/google-cloud-sql-and-magento) - [Google Cloud SQL and Shipwire](https://www.stacksync.com/integrations/google-cloud-sql-and-shipwire) - [Google Cloud SQL and Shopware](https://www.stacksync.com/integrations/google-cloud-sql-and-shopware) ### Human resources · 12 - [Google Cloud SQL and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-google-cloud-sql) - [Google Cloud SQL and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-google-cloud-sql) - [Google Cloud SQL and Greenhouse](https://www.stacksync.com/integrations/google-cloud-sql-and-greenhouse) - [Google Cloud SQL and Hibob](https://www.stacksync.com/integrations/google-cloud-sql-and-hibob) - [Google Cloud SQL and Jobvite](https://www.stacksync.com/integrations/google-cloud-sql-and-jobvite) - [Google Cloud SQL and Lever](https://www.stacksync.com/integrations/google-cloud-sql-and-lever) - [Google Cloud SQL and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/google-cloud-sql-and-oracle-fusion-cloud-hcm) - [Google Cloud SQL and Paylocity](https://www.stacksync.com/integrations/google-cloud-sql-and-paylocity) - [Google Cloud SQL and SmartRecruiters](https://www.stacksync.com/integrations/google-cloud-sql-and-smartrecruiters) - [Google Cloud SQL and Success Factors](https://www.stacksync.com/integrations/google-cloud-sql-and-success-factors) - [Google Cloud SQL and UKG Pro](https://www.stacksync.com/integrations/google-cloud-sql-and-ukg-pro) - [Google Cloud SQL and UKG Ready](https://www.stacksync.com/integrations/google-cloud-sql-and-ukg-ready) ### Marketing · 8 - [Google Cloud SQL and Bingads](https://www.stacksync.com/integrations/bingads-and-google-cloud-sql) - [Google Cloud SQL and Cvent](https://www.stacksync.com/integrations/cvent-and-google-cloud-sql) - [Google Cloud SQL and Demandbase](https://www.stacksync.com/integrations/demandbase-and-google-cloud-sql) - [Google Cloud SQL and Eloqua](https://www.stacksync.com/integrations/eloqua-and-google-cloud-sql) - [Google Cloud SQL and Iterable](https://www.stacksync.com/integrations/google-cloud-sql-and-iterable) - [Google Cloud SQL and Marketo](https://www.stacksync.com/integrations/google-cloud-sql-and-marketo) - [Google Cloud SQL and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/google-cloud-sql-and-salesforce-marketing-cloud) - [Google Cloud SQL and Twitter Ads](https://www.stacksync.com/integrations/google-cloud-sql-and-twitter-ads) ### Security and identity · 6 - [Google Cloud SQL and Active Directory](https://www.stacksync.com/integrations/active-directory-and-google-cloud-sql) - [Google Cloud SQL and Auth0](https://www.stacksync.com/integrations/auth0-and-google-cloud-sql) - [Google Cloud SQL and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-google-cloud-sql) - [Google Cloud SQL and JumpCloud](https://www.stacksync.com/integrations/google-cloud-sql-and-jumpcloud) - [Google Cloud SQL and Okta](https://www.stacksync.com/integrations/google-cloud-sql-and-okta) - [Google Cloud SQL and OneLogin](https://www.stacksync.com/integrations/google-cloud-sql-and-onelogin) ### Storage · 4 - [Google Cloud SQL and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-google-cloud-sql) - [Google Cloud SQL and Box](https://www.stacksync.com/integrations/box-and-google-cloud-sql) - [Google Cloud SQL and Egnyte](https://www.stacksync.com/integrations/egnyte-and-google-cloud-sql) - [Google Cloud SQL and SharePoint](https://www.stacksync.com/integrations/google-cloud-sql-and-sharepoint) 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](https://www.stacksync.com/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 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)