--- title: "Gmail connector: setup and compatibility | Stacksync" description: "Gmail integration guide: plan Messages and Attachments, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/gmail last_modified: 2026-09-15 --- Communications · Two-way sync platform # Gmail 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 Gmail workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Messages, Attachments and History. 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. - **Messages** - **Threads** - **Labels** **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=gmail) ## 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 ## Gmail records to discuss. These Gmail record examples help scope a technical review. They are not a list of verified Stacksync operations. Messages Retain message ID, conversation/thread ID, channel, and sender identity. Threads Identify this record type and the operation you need to review with Stacksync. Labels Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Drafts Identify this record type and the operation you need to review with Stacksync. Attachments Keep file/object ID, container, and version. A path can change and a filename can repeat. History Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Connection setup ## Gmail connection requirements. Review Gmail 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 Gmail account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Gmail, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Gmail integration. Define whether the goal is reporting communication activity, resolving customer context, or executing a new message/call action. The last option needs its own confirmed write method and business authorization. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Gmail **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 Retain message ID, conversation/thread ID, channel, and sender identity. Load related records in the right order Resolve conversation, participant, and customer context before associating messages. ### Mapping checks by record type #### Messages Confirm object support with Stacksync Identity Retain message ID, conversation/thread ID, channel, and sender identity. Fields to consider Source message ID · Thread reference · Delivery state · Timestamp · Related record ID Related records to resolve first Resolve conversation, participant, and customer context before associating messages. Test before going live Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. #### Attachments Confirm object support with Stacksync Identity Keep file/object ID, container, and version. A path can change and a filename can repeat. Fields to consider Source file ID · Container reference · Version · Metadata · Access classification Related records to resolve first Resolve folder/container and parent-record references before attaching metadata. Test before going live Test a renamed file, a new version, a moved folder, and an access-restricted document. #### History Confirm object support with Stacksync Identity Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Fields to consider Source event ID · Event type · Occurred-at time · Related record ID · Payload version Related records to resolve first Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Test before going live Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. [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 Gmail integration in four steps. The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. ### View the four setup tests and expected results 1. ### Confirm the intended Gmail account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Messages Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. **Expected result:** The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. 3. ### Test the operation your workflow needs Review one Gmail 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 Gmail integration. ### Diagnose record matching, delayed changes, and rejected operations A Gmail record appears under the wrong destination record Retain message ID, conversation/thread ID, channel, and sender identity. Resolve conversation, participant, and customer context before associating messages. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Gmail implementation’s change-detection method for Messages, Attachments and History. 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 Gmail 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 Gmail workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=gmail) ## Gmail 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) - [guide AI Agents for Beverage Brands: Investigate Distributor Delivery Claims](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) - [guide AI Agents for Household Brands: Investigate Refill and Case-Quantity Disputes](https://www.stacksync.com/blog/ai-agents-for-household-brands-investigate-refill-and-case-quantity-disputes) FAQ ## Gmail connector FAQ ### How should I plan an integration with Gmail? Define whether the goal is reporting communication activity, resolving customer context, or executing a new message/call action. The last option needs its own confirmed write method and business authorization. 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 Gmail connector write changes back? Write-back support is not established for this connection. Review the Gmail records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Gmail data? Retain message ID, conversation/thread ID, channel, and sender identity. ### Which related records should I load first for Gmail? Resolve conversation, participant, and customer context before associating messages. ### How do I validate Gmail changes after the initial load? Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. ### What will we cover in a Gmail integration demo? Start with one workflow and a sample record from Messages, Attachments and History. 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 Gmail 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 Gmail and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Gmail. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Gmail record changes.” - “Create a Genie that answers questions about our Gmail 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. AI assistant setup ## Use Gmail through Stacksync MCP. [Explore capabilities and setup →](https://www.stacksync.com/mcp/gmail) - [Claude guide ↗](https://www.stacksync.com/mcp/gmail/claude) - [ChatGPT guide ↗](https://www.stacksync.com/mcp/gmail/chatgpt) ## Explore Gmail 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 - [Gmail and Google Sheets](https://www.stacksync.com/integrations/gmail-and-google-sheets) - [Gmail and HubSpot](https://www.stacksync.com/integrations/gmail-and-hubspot) - [Gmail and Salesforce](https://www.stacksync.com/integrations/gmail-and-salesforce) - [Gmail and Outreach](https://www.stacksync.com/integrations/gmail-and-outreach) - [Asana and Gmail](https://www.stacksync.com/integrations/asana-and-gmail) - [Gmail and Pipedrive](https://www.stacksync.com/integrations/gmail-and-pipedrive) - [Gmail and Notion](https://www.stacksync.com/integrations/gmail-and-notion) - [Gmail and Twenty CRM](https://www.stacksync.com/integrations/gmail-and-twenty-crm) ### CRM · 40 - [Gmail and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-gmail) - [Gmail and Attio](https://www.stacksync.com/integrations/attio-and-gmail) - [Gmail and Chorusai](https://www.stacksync.com/integrations/chorusai-and-gmail) - [Gmail and Clari](https://www.stacksync.com/integrations/clari-and-gmail) - [Gmail and Close](https://www.stacksync.com/integrations/close-and-gmail) - [Gmail and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-gmail) - [Gmail and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-gmail) - [Gmail and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-gmail) - [Gmail and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-gmail) - [Gmail and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-gmail) - [Gmail and Freshsales](https://www.stacksync.com/integrations/freshsales-and-gmail) - [Gmail and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-gmail) - [Gmail and Gladly](https://www.stacksync.com/integrations/gladly-and-gmail) - [Gmail and Gong](https://www.stacksync.com/integrations/gmail-and-gong) - [Gmail and Gorgias](https://www.stacksync.com/integrations/gmail-and-gorgias) - [Gmail and HubSpot](https://www.stacksync.com/integrations/gmail-and-hubspot) - [Gmail and Infor CRM](https://www.stacksync.com/integrations/gmail-and-infor-crm) - [Gmail and Insightly](https://www.stacksync.com/integrations/gmail-and-insightly) - [Gmail and Intercom](https://www.stacksync.com/integrations/gmail-and-intercom) - [Gmail and Kommo](https://www.stacksync.com/integrations/gmail-and-kommo) - [Gmail and Kustomer](https://www.stacksync.com/integrations/gmail-and-kustomer) - [Gmail and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/gmail-and-microsoft-dynamics-365-sales) - [Gmail and Nimble](https://www.stacksync.com/integrations/gmail-and-nimble) - [Gmail and Nutshell](https://www.stacksync.com/integrations/gmail-and-nutshell) - [Gmail and Oracle CX Sales](https://www.stacksync.com/integrations/gmail-and-oracle-cx-sales) - [Gmail and Outreach](https://www.stacksync.com/integrations/gmail-and-outreach) - [Gmail and Pipedrive](https://www.stacksync.com/integrations/gmail-and-pipedrive) - [Gmail and Salesforce](https://www.stacksync.com/integrations/gmail-and-salesforce) - [Gmail and Salesloft](https://www.stacksync.com/integrations/gmail-and-salesloft) - [Gmail and SAP Sales Cloud](https://www.stacksync.com/integrations/gmail-and-sap-sales-cloud) - [Gmail and Seismic](https://www.stacksync.com/integrations/gmail-and-seismic) - [Gmail and Streak CRM](https://www.stacksync.com/integrations/gmail-and-streak-crm) - [Gmail and SugarCRM](https://www.stacksync.com/integrations/gmail-and-sugarcrm) - [Gmail and Twenty CRM](https://www.stacksync.com/integrations/gmail-and-twenty-crm) - [Gmail and Veeva CRM](https://www.stacksync.com/integrations/gmail-and-veeva-crm) - [Gmail and Vitally](https://www.stacksync.com/integrations/gmail-and-vitally) - [Gmail and Vtiger CRM](https://www.stacksync.com/integrations/gmail-and-vtiger-crm) - [Gmail and Xactly](https://www.stacksync.com/integrations/gmail-and-xactly) - [Gmail and Zoho CRM](https://www.stacksync.com/integrations/gmail-and-zoho-crm) - [Gmail and Zoho SalesIQ](https://www.stacksync.com/integrations/gmail-and-zoho-salesiq) ### Database · 7 - [Gmail and Citus](https://www.stacksync.com/integrations/citus-and-gmail) - [Gmail and Google AlloyDB](https://www.stacksync.com/integrations/gmail-and-google-alloydb) - [Gmail and Google Cloud Spanner](https://www.stacksync.com/integrations/gmail-and-google-cloud-spanner) - [Gmail and Google Cloud SQL](https://www.stacksync.com/integrations/gmail-and-google-cloud-sql) - [Gmail and IBM AS/400](https://www.stacksync.com/integrations/gmail-and-ibm-as400) - [Gmail and IBM Db2](https://www.stacksync.com/integrations/gmail-and-ibm-db2) - [Gmail and IBM Informix](https://www.stacksync.com/integrations/gmail-and-ibm-informix) ### Data warehouse · 19 - [Gmail and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-gmail) - [Gmail and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-gmail) - [Gmail and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-gmail) - [Gmail and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-gmail) - [Gmail and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-gmail) - [Gmail and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-gmail) - [Gmail and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-gmail) - [Gmail and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-gmail) - [Gmail and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-gmail) - [Gmail and BigQuery](https://www.stacksync.com/integrations/bigquery-and-gmail) - [Gmail and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-gmail) - [Gmail and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-gmail) - [Gmail and Databricks](https://www.stacksync.com/integrations/databricks-and-gmail) - [Gmail and Dremio](https://www.stacksync.com/integrations/dremio-and-gmail) - [Gmail and Exasol](https://www.stacksync.com/integrations/exasol-and-gmail) - [Gmail and Firebolt](https://www.stacksync.com/integrations/firebolt-and-gmail) - [Gmail and Google Cloud Platform](https://www.stacksync.com/integrations/gmail-and-google-cloud-platform) - [Gmail and Greenplum](https://www.stacksync.com/integrations/gmail-and-greenplum) - [Gmail and IBM Netezza](https://www.stacksync.com/integrations/gmail-and-ibm-netezza) ### Business productivity · 25 - [Gmail and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-gmail) - [Gmail and Agiloft](https://www.stacksync.com/integrations/agiloft-and-gmail) - [Gmail and Asana](https://www.stacksync.com/integrations/asana-and-gmail) - [Gmail and Docusign](https://www.stacksync.com/integrations/docusign-and-gmail) - [Gmail and Front](https://www.stacksync.com/integrations/front-and-gmail) - [Gmail and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-gmail) - [Gmail and Gainsight](https://www.stacksync.com/integrations/gainsight-and-gmail) - [Gmail and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-gmail) - [Gmail and Google Sheets](https://www.stacksync.com/integrations/gmail-and-google-sheets) - [Gmail and Ironclad](https://www.stacksync.com/integrations/gmail-and-ironclad) - [Gmail and Klaviyo](https://www.stacksync.com/integrations/gmail-and-klaviyo) - [Gmail and Lemlist](https://www.stacksync.com/integrations/gmail-and-lemlist) - [Gmail and Microsoft 365](https://www.stacksync.com/integrations/gmail-and-microsoft-365) - [Gmail and Microsoft Dynamics 365](https://www.stacksync.com/integrations/gmail-and-microsoft-dynamics-365) - [Gmail and Monday](https://www.stacksync.com/integrations/gmail-and-monday) - [Gmail and Notion](https://www.stacksync.com/integrations/gmail-and-notion) - [Gmail and Quip](https://www.stacksync.com/integrations/gmail-and-quip) - [Gmail and Resend](https://www.stacksync.com/integrations/gmail-and-resend) - [Gmail and SendGrid](https://www.stacksync.com/integrations/gmail-and-sendgrid) - [Gmail and ServiceMax](https://www.stacksync.com/integrations/gmail-and-servicemax) - [Gmail and ServiceNow](https://www.stacksync.com/integrations/gmail-and-servicenow) - [Gmail and Smartsheet](https://www.stacksync.com/integrations/gmail-and-smartsheet) - [Gmail and SysAid](https://www.stacksync.com/integrations/gmail-and-sysaid) - [Gmail and Wrike](https://www.stacksync.com/integrations/gmail-and-wrike) - [Gmail and Zendesk](https://www.stacksync.com/integrations/gmail-and-zendesk) ### Communications · 5 - [Gmail and Aircall](https://www.stacksync.com/integrations/aircall-and-gmail) - [Gmail and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-gmail) - [Gmail and Infobip](https://www.stacksync.com/integrations/gmail-and-infobip) - [Gmail and RingCentral](https://www.stacksync.com/integrations/gmail-and-ringcentral) - [Gmail and Zoom](https://www.stacksync.com/integrations/gmail-and-zoom) ### Marketing · 9 - [Gmail and Bingads](https://www.stacksync.com/integrations/bingads-and-gmail) - [Gmail and Cvent](https://www.stacksync.com/integrations/cvent-and-gmail) - [Gmail and Demandbase](https://www.stacksync.com/integrations/demandbase-and-gmail) - [Gmail and Eloqua](https://www.stacksync.com/integrations/eloqua-and-gmail) - [Gmail and Iterable](https://www.stacksync.com/integrations/gmail-and-iterable) - [Gmail and Marketo](https://www.stacksync.com/integrations/gmail-and-marketo) - [Gmail and RollWorks](https://www.stacksync.com/integrations/gmail-and-rollworks) - [Gmail and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/gmail-and-salesforce-marketing-cloud) - [Gmail and Twitter Ads](https://www.stacksync.com/integrations/gmail-and-twitter-ads) 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/)