--- title: "6sense connector: setup and compatibility | Stacksync" description: "6sense integration guide: plan Accounts and People / Contacts, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/6sense last_modified: 2026-09-15 --- CRM · Two-way sync platform # 6sense 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 6sense workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Accounts and People / Contacts. 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. - **Accounts** - **Segments** - **Buying Stage Scores** **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=6sense) ## 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 ## 6sense records to discuss. These 6sense record examples help scope a technical review. They are not a list of verified Stacksync operations. Accounts Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Segments Identify this record type and the operation you need to review with Stacksync. Buying Stage Scores Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Intent Signals Identify this record type and the operation you need to review with Stacksync. People / Contacts Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Reach Scores Identify this record type and the operation you need to review with Stacksync. Connection setup ## 6sense connection requirements. Review 6sense 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 6sense account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for 6sense, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your 6sense integration. Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks 6sense **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 the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Load related records in the right order Resolve parent organizations, business units, and currency references before dependent transactions. ### Mapping checks by record type #### Accounts Confirm object support with Stacksync Identity Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Fields to consider Source record ID · Legal or display name · Business-unit reference · Lifecycle status Related records to resolve first Resolve parent organizations, business units, and currency references before dependent transactions. Test before going live Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. #### People / Contacts Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. [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 6sense integration in four steps. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. ### View the four setup tests and expected results 1. ### Verify 6sense credentials and resource scope After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object. **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner. 2. ### Test record matching for Accounts Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. **Expected result:** A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. 3. ### Test the operation your workflow needs Review one 6sense 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 6sense integration. ### Diagnose record matching, delayed changes, and rejected operations A 6sense record appears under the wrong destination record Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Resolve parent organizations, business units, and currency references before dependent transactions. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected 6sense implementation’s change-detection method for Accounts and People / Contacts. 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 6sense 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 6sense workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=6sense) ## 6sense 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 ## 6sense connector FAQ ### How should I plan an integration with 6sense? Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. 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 6sense connector write changes back? Write-back support is not established for this connection. Review the 6sense records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for 6sense data? Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. ### Which related records should I load first for 6sense? Resolve parent organizations, business units, and currency references before dependent transactions. ### How do I validate 6sense changes after the initial load? Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. ### What will we cover in a 6sense integration demo? Start with one workflow and a sample record from Accounts and People / Contacts. 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 6sense 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 6sense and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use 6sense. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a 6sense record changes.” - “Create a Genie that answers questions about our 6sense 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 6sense 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 - [6sense and Slack](https://www.stacksync.com/integrations/6sense-and-slack) - [6sense and Salesforce](https://www.stacksync.com/integrations/6sense-and-salesforce) - [6sense and Databricks](https://www.stacksync.com/integrations/6sense-and-databricks) - [6sense and Outreach](https://www.stacksync.com/integrations/6sense-and-outreach) - [6sense and Marketo](https://www.stacksync.com/integrations/6sense-and-marketo) - [6sense and HubSpot](https://www.stacksync.com/integrations/6sense-and-hubspot) - [6sense and Gong](https://www.stacksync.com/integrations/6sense-and-gong) - [6sense and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/6sense-and-salesforce-marketing-cloud) ### CRM · 35 - [6sense and Affinity](https://www.stacksync.com/integrations/6sense-and-affinity) - [6sense and Apollo.io](https://www.stacksync.com/integrations/6sense-and-apollo-io) - [6sense and Attio](https://www.stacksync.com/integrations/6sense-and-attio) - [6sense and Chorusai](https://www.stacksync.com/integrations/6sense-and-chorusai) - [6sense and Clari](https://www.stacksync.com/integrations/6sense-and-clari) - [6sense and Close](https://www.stacksync.com/integrations/6sense-and-close) - [6sense and Copper CRM](https://www.stacksync.com/integrations/6sense-and-copper-crm) - [6sense and Creatio CRM](https://www.stacksync.com/integrations/6sense-and-creatio-crm) - [6sense and DealCloud](https://www.stacksync.com/integrations/6sense-and-dealcloud) - [6sense and Folk CRM](https://www.stacksync.com/integrations/6sense-and-folk-crm) - [6sense and Freshsales](https://www.stacksync.com/integrations/6sense-and-freshsales) - [6sense and Freshworks CRM](https://www.stacksync.com/integrations/6sense-and-freshworks-crm) - [6sense and Gong](https://www.stacksync.com/integrations/6sense-and-gong) - [6sense and HubSpot](https://www.stacksync.com/integrations/6sense-and-hubspot) - [6sense and Infor CRM](https://www.stacksync.com/integrations/6sense-and-infor-crm) - [6sense and Insightly](https://www.stacksync.com/integrations/6sense-and-insightly) - [6sense and Kommo](https://www.stacksync.com/integrations/6sense-and-kommo) - [6sense and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/6sense-and-microsoft-dynamics-365-sales) - [6sense and Nimble](https://www.stacksync.com/integrations/6sense-and-nimble) - [6sense and Nutshell](https://www.stacksync.com/integrations/6sense-and-nutshell) - [6sense and Oracle CX Sales](https://www.stacksync.com/integrations/6sense-and-oracle-cx-sales) - [6sense and Outreach](https://www.stacksync.com/integrations/6sense-and-outreach) - [6sense and Pipedrive](https://www.stacksync.com/integrations/6sense-and-pipedrive) - [6sense and Salesforce](https://www.stacksync.com/integrations/6sense-and-salesforce) - [6sense and Salesloft](https://www.stacksync.com/integrations/6sense-and-salesloft) - [6sense and SAP Sales Cloud](https://www.stacksync.com/integrations/6sense-and-sap-sales-cloud) - [6sense and Seismic](https://www.stacksync.com/integrations/6sense-and-seismic) - [6sense and Streak CRM](https://www.stacksync.com/integrations/6sense-and-streak-crm) - [6sense and SugarCRM](https://www.stacksync.com/integrations/6sense-and-sugarcrm) - [6sense and Twenty CRM](https://www.stacksync.com/integrations/6sense-and-twenty-crm) - [6sense and Veeva CRM](https://www.stacksync.com/integrations/6sense-and-veeva-crm) - [6sense and Vitally](https://www.stacksync.com/integrations/6sense-and-vitally) - [6sense and Vtiger CRM](https://www.stacksync.com/integrations/6sense-and-vtiger-crm) - [6sense and Xactly](https://www.stacksync.com/integrations/6sense-and-xactly) - [6sense and Zoho CRM](https://www.stacksync.com/integrations/6sense-and-zoho-crm) ### ERP · 3 - [6sense and Epicor ERP](https://www.stacksync.com/integrations/6sense-and-epicor-erp) - [6sense and NetSuite](https://www.stacksync.com/integrations/6sense-and-netsuite) - [6sense and SAP](https://www.stacksync.com/integrations/6sense-and-sap) ### Database · 50 - [6sense and Airtable](https://www.stacksync.com/integrations/6sense-and-airtable) - [6sense and Amazon Aurora](https://www.stacksync.com/integrations/6sense-and-amazon-aurora) - [6sense and Amazon DynamoDB](https://www.stacksync.com/integrations/6sense-and-dynamo-db) - [6sense and Amazon DynamoDB](https://www.stacksync.com/integrations/6sense-and-amazon-dynamodb) - [6sense and Amazon Lightsail](https://www.stacksync.com/integrations/6sense-and-amazon-lightsail) - [6sense and Amazon RDS](https://www.stacksync.com/integrations/6sense-and-amazon-rds) - [6sense and Apache Cassandra](https://www.stacksync.com/integrations/6sense-and-apache-cassandra) - [6sense and AWS Aurora MySQL](https://www.stacksync.com/integrations/6sense-and-aws-aurora-mysql) - [6sense and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/6sense-and-aws-aurora-postgresql) - [6sense and Azure Cosmos DB](https://www.stacksync.com/integrations/6sense-and-azure-cosmos-db) - [6sense and Azure SQL Database](https://www.stacksync.com/integrations/6sense-and-azure-sql-database) - [6sense and Citus](https://www.stacksync.com/integrations/6sense-and-citus) - [6sense and CockroachDB](https://www.stacksync.com/integrations/6sense-and-cockroachdb) - [6sense and Couchbase](https://www.stacksync.com/integrations/6sense-and-couchbase) - [6sense and DuckDB](https://www.stacksync.com/integrations/6sense-and-duckdb) - [6sense and Elasticsearch](https://www.stacksync.com/integrations/6sense-and-elasticsearch) - [6sense and Firebase](https://www.stacksync.com/integrations/6sense-and-firebase) - [6sense and Google AlloyDB](https://www.stacksync.com/integrations/6sense-and-google-alloydb) - [6sense and Google Cloud Spanner](https://www.stacksync.com/integrations/6sense-and-google-cloud-spanner) - [6sense and Google Cloud SQL](https://www.stacksync.com/integrations/6sense-and-google-cloud-sql) - [6sense and IBM AS/400](https://www.stacksync.com/integrations/6sense-and-ibm-as400) - [6sense and IBM Db2](https://www.stacksync.com/integrations/6sense-and-ibm-db2) - [6sense and IBM Informix](https://www.stacksync.com/integrations/6sense-and-ibm-informix) - [6sense and InfluxDB](https://www.stacksync.com/integrations/6sense-and-influxdb) - [6sense and InterSystems IRIS](https://www.stacksync.com/integrations/6sense-and-intersystems-iris) - [6sense and JDBC](https://www.stacksync.com/integrations/6sense-and-jdbc) - [6sense and MariaDB](https://www.stacksync.com/integrations/6sense-and-mariadb) - [6sense and MarkLogic](https://www.stacksync.com/integrations/6sense-and-marklogic) - [6sense and MongoDB](https://www.stacksync.com/integrations/6sense-and-mongodb) - [6sense and MySQL](https://www.stacksync.com/integrations/6sense-and-mysql) - [6sense and Neo4j](https://www.stacksync.com/integrations/6sense-and-neo4j) - [6sense and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/6sense-and-oci-database) - [6sense and OpenSearch](https://www.stacksync.com/integrations/6sense-and-opensearch) - [6sense and Oracle DB](https://www.stacksync.com/integrations/6sense-and-oracle-db) - [6sense and Postgres Heroku](https://www.stacksync.com/integrations/6sense-and-postgres-heroku) - [6sense and PostgreSQL](https://www.stacksync.com/integrations/6sense-and-postgresql) - [6sense and RavenDB](https://www.stacksync.com/integrations/6sense-and-ravendb) - [6sense and Redis Enterprise](https://www.stacksync.com/integrations/6sense-and-redis-enterprise) - [6sense and Reltio](https://www.stacksync.com/integrations/6sense-and-reltio) - [6sense and Render Postgres](https://www.stacksync.com/integrations/6sense-and-render-postgres) - [6sense and SAP ASE (Sybase)](https://www.stacksync.com/integrations/6sense-and-sap-ase-sybase) - [6sense and SAP HANA](https://www.stacksync.com/integrations/6sense-and-sap-hana) - [6sense and Scaleway Postgres](https://www.stacksync.com/integrations/6sense-and-scaleway-postgres) - [6sense and SingleStore](https://www.stacksync.com/integrations/6sense-and-singlestore) - [6sense and SQL Server](https://www.stacksync.com/integrations/6sense-and-sql-server) - [6sense and Supabase](https://www.stacksync.com/integrations/6sense-and-supabase) - [6sense and TiDB](https://www.stacksync.com/integrations/6sense-and-tidb) - [6sense and TimescaleDB](https://www.stacksync.com/integrations/6sense-and-timescaledb) - [6sense and VoltDB](https://www.stacksync.com/integrations/6sense-and-voltdb) - [6sense and YugabyteDB](https://www.stacksync.com/integrations/6sense-and-yugabytedb) ### Data warehouse · 28 - [6sense and Amazon Redshift](https://www.stacksync.com/integrations/6sense-and-amazon-redshift) - [6sense and Amazon S3](https://www.stacksync.com/integrations/6sense-and-aws-s3) - [6sense and Apache Doris](https://www.stacksync.com/integrations/6sense-and-apache-doris) - [6sense and Apache Druid](https://www.stacksync.com/integrations/6sense-and-apache-druid) - [6sense and Apache Hive](https://www.stacksync.com/integrations/6sense-and-apache-hive) - [6sense and Apache Impala](https://www.stacksync.com/integrations/6sense-and-apache-impala) - [6sense and Apache Pinot](https://www.stacksync.com/integrations/6sense-and-apache-pinot) - [6sense and Azure Synapse Analytics](https://www.stacksync.com/integrations/6sense-and-azure-synapse-analytics) - [6sense and BigQuery](https://www.stacksync.com/integrations/6sense-and-bigquery) - [6sense and ClickHouse](https://www.stacksync.com/integrations/6sense-and-clickhouse) - [6sense and Cloudera Data Platform](https://www.stacksync.com/integrations/6sense-and-cloudera-data-platform) - [6sense and Databricks](https://www.stacksync.com/integrations/6sense-and-databricks) - [6sense and Dremio](https://www.stacksync.com/integrations/6sense-and-dremio) - [6sense and Exasol](https://www.stacksync.com/integrations/6sense-and-exasol) - [6sense and Firebolt](https://www.stacksync.com/integrations/6sense-and-firebolt) - [6sense and Google Cloud Platform](https://www.stacksync.com/integrations/6sense-and-google-cloud-platform) - [6sense and Greenplum](https://www.stacksync.com/integrations/6sense-and-greenplum) - [6sense and IBM Netezza](https://www.stacksync.com/integrations/6sense-and-ibm-netezza) - [6sense and Materialize](https://www.stacksync.com/integrations/6sense-and-materialize) - [6sense and MotherDuck](https://www.stacksync.com/integrations/6sense-and-motherduck) - [6sense and Rockset](https://www.stacksync.com/integrations/6sense-and-rockset) - [6sense and Snowflake](https://www.stacksync.com/integrations/6sense-and-snowflake) - [6sense and Starburst Enterprise](https://www.stacksync.com/integrations/6sense-and-starburst-enterprise) - [6sense and StarRocks](https://www.stacksync.com/integrations/6sense-and-starrocks) - [6sense and Teradata Vantage](https://www.stacksync.com/integrations/6sense-and-teradata-vantage) - [6sense and Tinybird](https://www.stacksync.com/integrations/6sense-and-tinybird) - [6sense and Vertica](https://www.stacksync.com/integrations/6sense-and-vertica) - [6sense and Yellowbrick](https://www.stacksync.com/integrations/6sense-and-yellowbrick) ### Business productivity · 26 - [6sense and Adobe Sign](https://www.stacksync.com/integrations/6sense-and-adobe-sign) - [6sense and Agiloft](https://www.stacksync.com/integrations/6sense-and-agiloft) - [6sense and Asana](https://www.stacksync.com/integrations/6sense-and-asana) - [6sense and Braze](https://www.stacksync.com/integrations/6sense-and-braze) - [6sense and Customer.io](https://www.stacksync.com/integrations/6sense-and-customer-io) - [6sense and Docusign](https://www.stacksync.com/integrations/6sense-and-docusign) - [6sense and Gainsight](https://www.stacksync.com/integrations/6sense-and-gainsight) - [6sense and Gatekeeper](https://www.stacksync.com/integrations/6sense-and-gatekeeper) - [6sense and Google Sheets](https://www.stacksync.com/integrations/6sense-and-google-sheets) - [6sense and Ironclad](https://www.stacksync.com/integrations/6sense-and-ironclad) - [6sense and Klaviyo](https://www.stacksync.com/integrations/6sense-and-klaviyo) - [6sense and Lemlist](https://www.stacksync.com/integrations/6sense-and-lemlist) - [6sense and Microsoft Dynamics 365](https://www.stacksync.com/integrations/6sense-and-microsoft-dynamics-365) - [6sense and Monday](https://www.stacksync.com/integrations/6sense-and-monday) - [6sense and NextGen Healthcare](https://www.stacksync.com/integrations/6sense-and-nextgen-healthcare) - [6sense and Notion](https://www.stacksync.com/integrations/6sense-and-notion) - [6sense and Quip](https://www.stacksync.com/integrations/6sense-and-quip) - [6sense and Resend](https://www.stacksync.com/integrations/6sense-and-resend) - [6sense and SendGrid](https://www.stacksync.com/integrations/6sense-and-sendgrid) - [6sense and ServiceMax](https://www.stacksync.com/integrations/6sense-and-servicemax) - [6sense and Slack](https://www.stacksync.com/integrations/6sense-and-slack) - [6sense and Smartsheet](https://www.stacksync.com/integrations/6sense-and-smartsheet) - [6sense and SysAid](https://www.stacksync.com/integrations/6sense-and-sysaid) - [6sense and Twilio](https://www.stacksync.com/integrations/6sense-and-twilio) - [6sense and Wrike](https://www.stacksync.com/integrations/6sense-and-wrike) - [6sense and Zendesk](https://www.stacksync.com/integrations/6sense-and-zendesk) ### Accounting and finance · 1 - [6sense and Workday](https://www.stacksync.com/integrations/6sense-and-workday) ### Analytics · 3 - [6sense and Pendo](https://www.stacksync.com/integrations/6sense-and-pendo) - [6sense and Splunk](https://www.stacksync.com/integrations/6sense-and-splunk) - [6sense and Treasure Data](https://www.stacksync.com/integrations/6sense-and-treasuredata) ### E-commerce · 8 - [6sense and Akeneo](https://www.stacksync.com/integrations/6sense-and-akeneo) - [6sense and BigCommerce](https://www.stacksync.com/integrations/6sense-and-bigcommerce) - [6sense and ChannelEngine](https://www.stacksync.com/integrations/6sense-and-channelengine) - [6sense and EasyPost](https://www.stacksync.com/integrations/6sense-and-easypost) - [6sense and Magento](https://www.stacksync.com/integrations/6sense-and-magento) - [6sense and NuORDER](https://www.stacksync.com/integrations/6sense-and-nuorder) - [6sense and Shipwire](https://www.stacksync.com/integrations/6sense-and-shipwire) - [6sense and Shopware](https://www.stacksync.com/integrations/6sense-and-shopware) ### Human resources · 13 - [6sense and Ceridian Dayforce](https://www.stacksync.com/integrations/6sense-and-ceridian-dayforce) - [6sense and D2L Brightspace](https://www.stacksync.com/integrations/6sense-and-d2l-brightspace) - [6sense and Greenhouse](https://www.stacksync.com/integrations/6sense-and-greenhouse) - [6sense and Hibob](https://www.stacksync.com/integrations/6sense-and-hibob) - [6sense and Jobvite](https://www.stacksync.com/integrations/6sense-and-jobvite) - [6sense and Lever](https://www.stacksync.com/integrations/6sense-and-lever) - [6sense and Namely](https://www.stacksync.com/integrations/6sense-and-namely) - [6sense and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/6sense-and-oracle-fusion-cloud-hcm) - [6sense and Paylocity](https://www.stacksync.com/integrations/6sense-and-paylocity) - [6sense and SmartRecruiters](https://www.stacksync.com/integrations/6sense-and-smartrecruiters) - [6sense and Success Factors](https://www.stacksync.com/integrations/6sense-and-success-factors) - [6sense and UKG Pro](https://www.stacksync.com/integrations/6sense-and-ukg-pro) - [6sense and UKG Ready](https://www.stacksync.com/integrations/6sense-and-ukg-ready) ### Marketing · 9 - [6sense and Bingads](https://www.stacksync.com/integrations/6sense-and-bingads) - [6sense and Cvent](https://www.stacksync.com/integrations/6sense-and-cvent) - [6sense and Demandbase](https://www.stacksync.com/integrations/6sense-and-demandbase) - [6sense and Eloqua](https://www.stacksync.com/integrations/6sense-and-eloqua) - [6sense and Iterable](https://www.stacksync.com/integrations/6sense-and-iterable) - [6sense and Marketo](https://www.stacksync.com/integrations/6sense-and-marketo) - [6sense and RollWorks](https://www.stacksync.com/integrations/6sense-and-rollworks) - [6sense and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/6sense-and-salesforce-marketing-cloud) - [6sense and Twitter Ads](https://www.stacksync.com/integrations/6sense-and-twitter-ads) ### Storage · 4 - [6sense and Amazon S3](https://www.stacksync.com/integrations/6sense-and-amazon-s3) - [6sense and Box](https://www.stacksync.com/integrations/6sense-and-box) - [6sense and Egnyte](https://www.stacksync.com/integrations/6sense-and-egnyte) - [6sense and SharePoint](https://www.stacksync.com/integrations/6sense-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/)