--- title: "JMS connector: setup and compatibility | Stacksync" description: "JMS integration guide: plan TextMessage, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/jms last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # JMS 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 JMS workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with TextMessage. 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. - **Queue** - **Topic** - **TextMessage** **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=jms) ## 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 ## JMS records to discuss. These JMS record examples help scope a technical review. They are not a list of verified Stacksync operations. Queue Identify this record type and the operation you need to review with Stacksync. Topic Identify this record type and the operation you need to review with Stacksync. TextMessage Retain message ID, conversation/thread ID, channel, and sender identity. ### See 3 more record examples MapMessage Identify this record type and the operation you need to review with Stacksync. BytesMessage Identify this record type and the operation you need to review with Stacksync. Durable Subscription Identify this record type and the operation you need to review with Stacksync. Connection setup ## JMS connection requirements. Review JMS 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 JMS account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for JMS, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your JMS integration. Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks JMS **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 #### TextMessage 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. [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 JMS integration in four steps. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### View the four setup tests and expected results 1. ### Verify JMS 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 TextMessage 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:** A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. 3. ### Test the operation your workflow needs Review one JMS 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 JMS integration. ### Diagnose record matching, delayed changes, and rejected operations A JMS 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 JMS implementation’s change-detection method for TextMessage. 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 JMS 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 JMS workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=jms) ## JMS 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 ## JMS connector FAQ ### How should I plan an integration with JMS? Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. 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 JMS connector write changes back? Write-back support is not established for this connection. Review the JMS records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for JMS data? Retain message ID, conversation/thread ID, channel, and sender identity. ### Which related records should I load first for JMS? Resolve conversation, participant, and customer context before associating messages. ### How do I validate JMS changes after the initial load? Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### What will we cover in a JMS integration demo? Start with one workflow and a sample record from TextMessage. 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 JMS 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 JMS and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use JMS. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a JMS record changes.” - “Create a Genie that answers questions about our JMS 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 JMS 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 - [JMS and Rockset](https://www.stacksync.com/integrations/jms-and-rockset) - [JMS and JumpCloud](https://www.stacksync.com/integrations/jms-and-jumpcloud) - [JMS and Microsoft 365](https://www.stacksync.com/integrations/jms-and-microsoft-365) - [JMS and Okta](https://www.stacksync.com/integrations/jms-and-okta) - [Apache Druid and JMS](https://www.stacksync.com/integrations/apache-druid-and-jms) - [JMS and Slack](https://www.stacksync.com/integrations/jms-and-slack) - [JMS and Pendo](https://www.stacksync.com/integrations/jms-and-pendo) - [Amazon S3 and JMS](https://www.stacksync.com/integrations/amazon-s3-and-jms) ### Database · 50 - [JMS and Airtable](https://www.stacksync.com/integrations/airtable-and-jms) - [JMS and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-jms) - [JMS and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-jms) - [JMS and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-jms) - [JMS and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-jms) - [JMS and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-jms) - [JMS and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-jms) - [JMS and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-jms) - [JMS and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-jms) - [JMS and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-jms) - [JMS and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-jms) - [JMS and Citus](https://www.stacksync.com/integrations/citus-and-jms) - [JMS and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-jms) - [JMS and Couchbase](https://www.stacksync.com/integrations/couchbase-and-jms) - [JMS and DuckDB](https://www.stacksync.com/integrations/duckdb-and-jms) - [JMS and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-jms) - [JMS and Firebase](https://www.stacksync.com/integrations/firebase-and-jms) - [JMS and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-jms) - [JMS and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-jms) - [JMS and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-jms) - [JMS and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-jms) - [JMS and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-jms) - [JMS and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-jms) - [JMS and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-jms) - [JMS and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-jms) - [JMS and JDBC](https://www.stacksync.com/integrations/jdbc-and-jms) - [JMS and MariaDB](https://www.stacksync.com/integrations/jms-and-mariadb) - [JMS and MarkLogic](https://www.stacksync.com/integrations/jms-and-marklogic) - [JMS and MongoDB](https://www.stacksync.com/integrations/jms-and-mongodb) - [JMS and MySQL](https://www.stacksync.com/integrations/jms-and-mysql) - [JMS and Neo4j](https://www.stacksync.com/integrations/jms-and-neo4j) - [JMS and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/jms-and-oci-database) - [JMS and OpenSearch](https://www.stacksync.com/integrations/jms-and-opensearch) - [JMS and Oracle DB](https://www.stacksync.com/integrations/jms-and-oracle-db) - [JMS and Postgres Heroku](https://www.stacksync.com/integrations/jms-and-postgres-heroku) - [JMS and PostgreSQL](https://www.stacksync.com/integrations/jms-and-postgresql) - [JMS and RavenDB](https://www.stacksync.com/integrations/jms-and-ravendb) - [JMS and Redis Enterprise](https://www.stacksync.com/integrations/jms-and-redis-enterprise) - [JMS and Reltio](https://www.stacksync.com/integrations/jms-and-reltio) - [JMS and Render Postgres](https://www.stacksync.com/integrations/jms-and-render-postgres) - [JMS and SAP ASE (Sybase)](https://www.stacksync.com/integrations/jms-and-sap-ase-sybase) - [JMS and SAP HANA](https://www.stacksync.com/integrations/jms-and-sap-hana) - [JMS and Scaleway Postgres](https://www.stacksync.com/integrations/jms-and-scaleway-postgres) - [JMS and SingleStore](https://www.stacksync.com/integrations/jms-and-singlestore) - [JMS and SQL Server](https://www.stacksync.com/integrations/jms-and-sql-server) - [JMS and Supabase](https://www.stacksync.com/integrations/jms-and-supabase) - [JMS and TiDB](https://www.stacksync.com/integrations/jms-and-tidb) - [JMS and TimescaleDB](https://www.stacksync.com/integrations/jms-and-timescaledb) - [JMS and VoltDB](https://www.stacksync.com/integrations/jms-and-voltdb) - [JMS and YugabyteDB](https://www.stacksync.com/integrations/jms-and-yugabytedb) ### Data warehouse · 28 - [JMS and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-jms) - [JMS and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-jms) - [JMS and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-jms) - [JMS and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-jms) - [JMS and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-jms) - [JMS and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-jms) - [JMS and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-jms) - [JMS and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-jms) - [JMS and BigQuery](https://www.stacksync.com/integrations/bigquery-and-jms) - [JMS and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-jms) - [JMS and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-jms) - [JMS and Databricks](https://www.stacksync.com/integrations/databricks-and-jms) - [JMS and Dremio](https://www.stacksync.com/integrations/dremio-and-jms) - [JMS and Exasol](https://www.stacksync.com/integrations/exasol-and-jms) - [JMS and Firebolt](https://www.stacksync.com/integrations/firebolt-and-jms) - [JMS and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-jms) - [JMS and Greenplum](https://www.stacksync.com/integrations/greenplum-and-jms) - [JMS and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-jms) - [JMS and Materialize](https://www.stacksync.com/integrations/jms-and-materialize) - [JMS and MotherDuck](https://www.stacksync.com/integrations/jms-and-motherduck) - [JMS and Rockset](https://www.stacksync.com/integrations/jms-and-rockset) - [JMS and Snowflake](https://www.stacksync.com/integrations/jms-and-snowflake) - [JMS and Starburst Enterprise](https://www.stacksync.com/integrations/jms-and-starburst-enterprise) - [JMS and StarRocks](https://www.stacksync.com/integrations/jms-and-starrocks) - [JMS and Teradata Vantage](https://www.stacksync.com/integrations/jms-and-teradata-vantage) - [JMS and Tinybird](https://www.stacksync.com/integrations/jms-and-tinybird) - [JMS and Vertica](https://www.stacksync.com/integrations/jms-and-vertica) - [JMS and Yellowbrick](https://www.stacksync.com/integrations/jms-and-yellowbrick) ### Business productivity · 37 - [JMS and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-jms) - [JMS and Agiloft](https://www.stacksync.com/integrations/agiloft-and-jms) - [JMS and Asana](https://www.stacksync.com/integrations/asana-and-jms) - [JMS and Atlassian](https://www.stacksync.com/integrations/atlassian-and-jms) - [JMS and Braze](https://www.stacksync.com/integrations/braze-and-jms) - [JMS and Campfire](https://www.stacksync.com/integrations/campfire-and-jms) - [JMS and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-jms) - [JMS and Customer.io](https://www.stacksync.com/integrations/customer-io-and-jms) - [JMS and Docusign](https://www.stacksync.com/integrations/docusign-and-jms) - [JMS and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-jms) - [JMS and Front](https://www.stacksync.com/integrations/front-and-jms) - [JMS and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-jms) - [JMS and Gainsight](https://www.stacksync.com/integrations/gainsight-and-jms) - [JMS and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-jms) - [JMS and GitHub](https://www.stacksync.com/integrations/github-and-jms) - [JMS and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-jms) - [JMS and Ironclad](https://www.stacksync.com/integrations/ironclad-and-jms) - [JMS and Klaviyo](https://www.stacksync.com/integrations/jms-and-klaviyo) - [JMS and Lemlist](https://www.stacksync.com/integrations/jms-and-lemlist) - [JMS and Microsoft 365](https://www.stacksync.com/integrations/jms-and-microsoft-365) - [JMS and Microsoft Dynamics 365](https://www.stacksync.com/integrations/jms-and-microsoft-dynamics-365) - [JMS and Microsoft Teams](https://www.stacksync.com/integrations/jms-and-microsoft-teams) - [JMS and Monday](https://www.stacksync.com/integrations/jms-and-monday) - [JMS and NextGen Healthcare](https://www.stacksync.com/integrations/jms-and-nextgen-healthcare) - [JMS and Notion](https://www.stacksync.com/integrations/jms-and-notion) - [JMS and Orderful](https://www.stacksync.com/integrations/jms-and-orderful) - [JMS and Quip](https://www.stacksync.com/integrations/jms-and-quip) - [JMS and Resend](https://www.stacksync.com/integrations/jms-and-resend) - [JMS and SendGrid](https://www.stacksync.com/integrations/jms-and-sendgrid) - [JMS and ServiceMax](https://www.stacksync.com/integrations/jms-and-servicemax) - [JMS and ServiceNow](https://www.stacksync.com/integrations/jms-and-servicenow) - [JMS and Slack](https://www.stacksync.com/integrations/jms-and-slack) - [JMS and Smartsheet](https://www.stacksync.com/integrations/jms-and-smartsheet) - [JMS and SysAid](https://www.stacksync.com/integrations/jms-and-sysaid) - [JMS and Twilio](https://www.stacksync.com/integrations/jms-and-twilio) - [JMS and Wrike](https://www.stacksync.com/integrations/jms-and-wrike) - [JMS and Zendesk](https://www.stacksync.com/integrations/jms-and-zendesk) ### Analytics · 3 - [JMS and Pendo](https://www.stacksync.com/integrations/jms-and-pendo) - [JMS and Splunk](https://www.stacksync.com/integrations/jms-and-splunk) - [JMS and Treasure Data](https://www.stacksync.com/integrations/jms-and-treasuredata) ### Communications · 5 - [JMS and Aircall](https://www.stacksync.com/integrations/aircall-and-jms) - [JMS and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-jms) - [JMS and Infobip](https://www.stacksync.com/integrations/infobip-and-jms) - [JMS and RingCentral](https://www.stacksync.com/integrations/jms-and-ringcentral) - [JMS and Zoom](https://www.stacksync.com/integrations/jms-and-zoom) ### Security and identity · 6 - [JMS and Active Directory](https://www.stacksync.com/integrations/active-directory-and-jms) - [JMS and Auth0](https://www.stacksync.com/integrations/auth0-and-jms) - [JMS and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-jms) - [JMS and JumpCloud](https://www.stacksync.com/integrations/jms-and-jumpcloud) - [JMS and Okta](https://www.stacksync.com/integrations/jms-and-okta) - [JMS and OneLogin](https://www.stacksync.com/integrations/jms-and-onelogin) ### Storage · 4 - [JMS and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-jms) - [JMS and Box](https://www.stacksync.com/integrations/box-and-jms) - [JMS and Egnyte](https://www.stacksync.com/integrations/egnyte-and-jms) - [JMS and SharePoint](https://www.stacksync.com/integrations/jms-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/)