--- title: "Customer.io connector: setup and compatibility | Stacksync" description: "Customer.io integration guide: plan People and Objects, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/customer-io last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # Customer.io 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 Customer.io workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with People, Objects and Events. 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. - **People** - **Objects** - **Events** **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=customer-io) ## 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 ## Customer.io records to discuss. These Customer.io record examples help scope a technical review. They are not a list of verified Stacksync operations. People 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. Objects Keep file/object ID, container, and version. A path can change and a filename can repeat. Events Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. ### See 3 more record examples Segments Identify this record type and the operation you need to review with Stacksync. Campaigns Keep campaign ID, channel/account context, and separate audience membership IDs. Broadcasts Identify this record type and the operation you need to review with Stacksync. Connection setup ## Customer.io connection requirements. Review Customer.io 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 Customer.io account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Customer.io, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Customer.io integration. Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Customer.io **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 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. Load related records in the right order Resolve the organization relationship and any owner or consent references required by the destination. ### Mapping checks by record type #### People 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. #### Objects 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. #### Events 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. #### Campaigns Confirm object support with Stacksync Identity Keep campaign ID, channel/account context, and separate audience membership IDs. Fields to consider Source campaign ID · Channel reference · Status · Audience references · Measurement window Related records to resolve first Resolve contact/audience identities and channel-account references. Test before going live Test a removed audience member, a paused campaign, and one campaign reported across multiple channels. #### Deliveries / 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. [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 Customer.io integration in four steps. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### View the four setup tests and expected results 1. ### Verify Customer.io 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 People Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test an email change, two records sharing an email, and a person associated with multiple organizations. **Expected result:** An update reaches the intended record, preserves its relationships, and performs each approved side effect once. 3. ### Test the operation your workflow needs Review one Customer.io 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 Customer.io integration. ### Diagnose record matching, delayed changes, and rejected operations A Customer.io record appears under the wrong destination record 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. Resolve the organization relationship and any owner or consent references required by the destination. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Customer.io implementation’s change-detection method for People, Objects and Events. 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 Customer.io 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 Customer.io workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=customer-io) ## Customer.io 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 ## Customer.io connector FAQ ### How should I plan an integration with Customer.io? Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. 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 Customer.io connector write changes back? Write-back support is not established for this connection. Review the Customer.io records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Customer.io data? 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. ### Which related records should I load first for Customer.io? Resolve the organization relationship and any owner or consent references required by the destination. ### How do I validate Customer.io changes after the initial load? Test an email change, two records sharing an email, and a person associated with multiple organizations. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What will we cover in a Customer.io integration demo? Start with one workflow and a sample record from People, Objects and Events. 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 Customer.io 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 Customer.io and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Customer.io. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Customer.io record changes.” - “Create a Genie that answers questions about our Customer.io 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 Customer.io 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 - [Customer.io and Supabase](https://www.stacksync.com/integrations/customer-io-and-supabase) - [Customer.io and Intercom](https://www.stacksync.com/integrations/customer-io-and-intercom) - [Customer.io and Rockset](https://www.stacksync.com/integrations/customer-io-and-rockset) - [Customer.io and Zendesk](https://www.stacksync.com/integrations/customer-io-and-zendesk) - [Amazon S3 and Customer.io](https://www.stacksync.com/integrations/amazon-s3-and-customer-io) - [Customer.io and Slack](https://www.stacksync.com/integrations/customer-io-and-slack) - [Customer.io and HubSpot](https://www.stacksync.com/integrations/customer-io-and-hubspot) - [Customer.io and Salesforce](https://www.stacksync.com/integrations/customer-io-and-salesforce) ### CRM · 33 - [Customer.io and 6sense](https://www.stacksync.com/integrations/6sense-and-customer-io) - [Customer.io and Affinity](https://www.stacksync.com/integrations/affinity-and-customer-io) - [Customer.io and Attio](https://www.stacksync.com/integrations/attio-and-customer-io) - [Customer.io and Chorusai](https://www.stacksync.com/integrations/chorusai-and-customer-io) - [Customer.io and Clearbit](https://www.stacksync.com/integrations/clearbit-and-customer-io) - [Customer.io and Close](https://www.stacksync.com/integrations/close-and-customer-io) - [Customer.io and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-customer-io) - [Customer.io and Dun & Bradstreet](https://www.stacksync.com/integrations/customer-io-and-dun-bradstreet) - [Customer.io and Freshsales](https://www.stacksync.com/integrations/customer-io-and-freshsales) - [Customer.io and Freshworks CRM](https://www.stacksync.com/integrations/customer-io-and-freshworks-crm) - [Customer.io and Gong](https://www.stacksync.com/integrations/customer-io-and-gong) - [Customer.io and Gorgias](https://www.stacksync.com/integrations/customer-io-and-gorgias) - [Customer.io and HubSpot](https://www.stacksync.com/integrations/customer-io-and-hubspot) - [Customer.io and Infor CRM](https://www.stacksync.com/integrations/customer-io-and-infor-crm) - [Customer.io and Insightly](https://www.stacksync.com/integrations/customer-io-and-insightly) - [Customer.io and Intercom](https://www.stacksync.com/integrations/customer-io-and-intercom) - [Customer.io and Kommo](https://www.stacksync.com/integrations/customer-io-and-kommo) - [Customer.io and Kustomer](https://www.stacksync.com/integrations/customer-io-and-kustomer) - [Customer.io and Outreach](https://www.stacksync.com/integrations/customer-io-and-outreach) - [Customer.io and Pipedrive](https://www.stacksync.com/integrations/customer-io-and-pipedrive) - [Customer.io and Salesforce](https://www.stacksync.com/integrations/customer-io-and-salesforce) - [Customer.io and Salesloft](https://www.stacksync.com/integrations/customer-io-and-salesloft) - [Customer.io and SAP Sales Cloud](https://www.stacksync.com/integrations/customer-io-and-sap-sales-cloud) - [Customer.io and Seismic](https://www.stacksync.com/integrations/customer-io-and-seismic) - [Customer.io and Shopify](https://www.stacksync.com/integrations/customer-io-and-shopify) - [Customer.io and SugarCRM](https://www.stacksync.com/integrations/customer-io-and-sugarcrm) - [Customer.io and Twenty CRM](https://www.stacksync.com/integrations/customer-io-and-twenty-crm) - [Customer.io and Veeva CRM](https://www.stacksync.com/integrations/customer-io-and-veeva-crm) - [Customer.io and Vtiger CRM](https://www.stacksync.com/integrations/customer-io-and-vtiger-crm) - [Customer.io and Xactly](https://www.stacksync.com/integrations/customer-io-and-xactly) - [Customer.io and Zoho CRM](https://www.stacksync.com/integrations/customer-io-and-zoho-crm) - [Customer.io and Zoho SalesIQ](https://www.stacksync.com/integrations/customer-io-and-zoho-salesiq) - [Customer.io and ZoomInfo](https://www.stacksync.com/integrations/customer-io-and-zoominfo) ### ERP · 24 - [Customer.io and Acumatica](https://www.stacksync.com/integrations/acumatica-and-customer-io) - [Customer.io and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-customer-io) - [Customer.io and Cin7](https://www.stacksync.com/integrations/cin7-and-customer-io) - [Customer.io and Dynamics 365 Business Central](https://www.stacksync.com/integrations/customer-io-and-microsoft-dynamics-365-business-central) - [Customer.io and Epicor ERP](https://www.stacksync.com/integrations/customer-io-and-epicor-erp) - [Customer.io and Infor LN](https://www.stacksync.com/integrations/customer-io-and-infor-ln) - [Customer.io and Infor M3](https://www.stacksync.com/integrations/customer-io-and-infor-m3) - [Customer.io and Linnworks](https://www.stacksync.com/integrations/customer-io-and-linnworks) - [Customer.io and Microsoft Dynamics GP](https://www.stacksync.com/integrations/customer-io-and-microsoft-dynamics-gp) - [Customer.io and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/customer-io-and-microsoft-dynamics-nav) - [Customer.io and NetSuite](https://www.stacksync.com/integrations/customer-io-and-netsuite) - [Customer.io and Odoo](https://www.stacksync.com/integrations/customer-io-and-odoo) - [Customer.io and Plex ERP](https://www.stacksync.com/integrations/customer-io-and-plex-erp) - [Customer.io and QAD ERP](https://www.stacksync.com/integrations/customer-io-and-qad-erp) - [Customer.io and Sage 100](https://www.stacksync.com/integrations/customer-io-and-sage-100) - [Customer.io and Sage 300](https://www.stacksync.com/integrations/customer-io-and-sage-300) - [Customer.io and Sage Intacct](https://www.stacksync.com/integrations/customer-io-and-sage-intacct) - [Customer.io and Sage X3](https://www.stacksync.com/integrations/customer-io-and-sage-x3) - [Customer.io and SAP](https://www.stacksync.com/integrations/customer-io-and-sap) - [Customer.io and SAP Business ByDesign](https://www.stacksync.com/integrations/customer-io-and-sap-business-bydesign) - [Customer.io and SAP Business One](https://www.stacksync.com/integrations/customer-io-and-sap-business-one) - [Customer.io and SAP S/4HANA](https://www.stacksync.com/integrations/customer-io-and-sap-s4hana) - [Customer.io and Syspro](https://www.stacksync.com/integrations/customer-io-and-syspro) - [Customer.io and TikTok Shop](https://www.stacksync.com/integrations/customer-io-and-tiktok) ### Database · 18 - [Customer.io and Airtable](https://www.stacksync.com/integrations/airtable-and-customer-io) - [Customer.io and Amazon DynamoDB](https://www.stacksync.com/integrations/customer-io-and-dynamo-db) - [Customer.io and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-customer-io) - [Customer.io and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-customer-io) - [Customer.io and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-customer-io) - [Customer.io and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-customer-io) - [Customer.io and Elasticsearch](https://www.stacksync.com/integrations/customer-io-and-elasticsearch) - [Customer.io and Firebase](https://www.stacksync.com/integrations/customer-io-and-firebase) - [Customer.io and IBM Informix](https://www.stacksync.com/integrations/customer-io-and-ibm-informix) - [Customer.io and MariaDB](https://www.stacksync.com/integrations/customer-io-and-mariadb) - [Customer.io and MongoDB](https://www.stacksync.com/integrations/customer-io-and-mongodb) - [Customer.io and MySQL](https://www.stacksync.com/integrations/customer-io-and-mysql) - [Customer.io and Oracle DB](https://www.stacksync.com/integrations/customer-io-and-oracle-db) - [Customer.io and Postgres Heroku](https://www.stacksync.com/integrations/customer-io-and-postgres-heroku) - [Customer.io and PostgreSQL](https://www.stacksync.com/integrations/customer-io-and-postgresql) - [Customer.io and SAP HANA](https://www.stacksync.com/integrations/customer-io-and-sap-hana) - [Customer.io and SQL Server](https://www.stacksync.com/integrations/customer-io-and-sql-server) - [Customer.io and Supabase](https://www.stacksync.com/integrations/customer-io-and-supabase) ### Data warehouse · 10 - [Customer.io and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-customer-io) - [Customer.io and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-customer-io) - [Customer.io and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-customer-io) - [Customer.io and BigQuery](https://www.stacksync.com/integrations/bigquery-and-customer-io) - [Customer.io and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-customer-io) - [Customer.io and Databricks](https://www.stacksync.com/integrations/customer-io-and-databricks) - [Customer.io and Google Cloud Platform](https://www.stacksync.com/integrations/customer-io-and-google-cloud-platform) - [Customer.io and MotherDuck](https://www.stacksync.com/integrations/customer-io-and-motherduck) - [Customer.io and Rockset](https://www.stacksync.com/integrations/customer-io-and-rockset) - [Customer.io and Snowflake](https://www.stacksync.com/integrations/customer-io-and-snowflake) ### Business productivity · 30 - [Customer.io and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-customer-io) - [Customer.io and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-customer-io) - [Customer.io and Asana](https://www.stacksync.com/integrations/asana-and-customer-io) - [Customer.io and Braze](https://www.stacksync.com/integrations/braze-and-customer-io) - [Customer.io and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-customer-io) - [Customer.io and Docusign](https://www.stacksync.com/integrations/customer-io-and-docusign) - [Customer.io and Front](https://www.stacksync.com/integrations/customer-io-and-front) - [Customer.io and FullEnrich](https://www.stacksync.com/integrations/customer-io-and-full-enrich) - [Customer.io and Gainsight](https://www.stacksync.com/integrations/customer-io-and-gainsight) - [Customer.io and GitHub](https://www.stacksync.com/integrations/customer-io-and-github) - [Customer.io and Google Sheets](https://www.stacksync.com/integrations/customer-io-and-google-sheets) - [Customer.io and Ironclad](https://www.stacksync.com/integrations/customer-io-and-ironclad) - [Customer.io and Klaviyo](https://www.stacksync.com/integrations/customer-io-and-klaviyo) - [Customer.io and Lemlist](https://www.stacksync.com/integrations/customer-io-and-lemlist) - [Customer.io and Lusha](https://www.stacksync.com/integrations/customer-io-and-lusha) - [Customer.io and Microsoft Dynamics 365](https://www.stacksync.com/integrations/customer-io-and-microsoft-dynamics-365) - [Customer.io and Microsoft Teams](https://www.stacksync.com/integrations/customer-io-and-microsoft-teams) - [Customer.io and Monday](https://www.stacksync.com/integrations/customer-io-and-monday) - [Customer.io and Notion](https://www.stacksync.com/integrations/customer-io-and-notion) - [Customer.io and Orderful](https://www.stacksync.com/integrations/customer-io-and-orderful) - [Customer.io and Quip](https://www.stacksync.com/integrations/customer-io-and-quip) - [Customer.io and Resend](https://www.stacksync.com/integrations/customer-io-and-resend) - [Customer.io and SendGrid](https://www.stacksync.com/integrations/customer-io-and-sendgrid) - [Customer.io and ServiceMax](https://www.stacksync.com/integrations/customer-io-and-servicemax) - [Customer.io and Slack](https://www.stacksync.com/integrations/customer-io-and-slack) - [Customer.io and Smartsheet](https://www.stacksync.com/integrations/customer-io-and-smartsheet) - [Customer.io and SysAid](https://www.stacksync.com/integrations/customer-io-and-sysaid) - [Customer.io and Twilio](https://www.stacksync.com/integrations/customer-io-and-twilio) - [Customer.io and Wrike](https://www.stacksync.com/integrations/customer-io-and-wrike) - [Customer.io and Zendesk](https://www.stacksync.com/integrations/customer-io-and-zendesk) ### Accounting and finance · 16 - [Customer.io and Adyen](https://www.stacksync.com/integrations/adyen-and-customer-io) - [Customer.io and Anaplan](https://www.stacksync.com/integrations/anaplan-and-customer-io) - [Customer.io and BILL](https://www.stacksync.com/integrations/bill-and-customer-io) - [Customer.io and Braintree](https://www.stacksync.com/integrations/braintree-and-customer-io) - [Customer.io and Chargebee](https://www.stacksync.com/integrations/chargebee-and-customer-io) - [Customer.io and Coupa](https://www.stacksync.com/integrations/coupa-and-customer-io) - [Customer.io and Hyperline](https://www.stacksync.com/integrations/customer-io-and-hyperline) - [Customer.io and Navan](https://www.stacksync.com/integrations/customer-io-and-navan) - [Customer.io and Pigment](https://www.stacksync.com/integrations/customer-io-and-pigment) - [Customer.io and QuickBooks](https://www.stacksync.com/integrations/customer-io-and-quickbooks) - [Customer.io and Ramp](https://www.stacksync.com/integrations/customer-io-and-ramp) - [Customer.io and Recurly](https://www.stacksync.com/integrations/customer-io-and-recurly) - [Customer.io and Rillet](https://www.stacksync.com/integrations/customer-io-and-rillet) - [Customer.io and Stripe](https://www.stacksync.com/integrations/customer-io-and-stripe) - [Customer.io and Workday](https://www.stacksync.com/integrations/customer-io-and-workday) - [Customer.io and Zuora](https://www.stacksync.com/integrations/customer-io-and-zuora) ### AI · 4 - [Customer.io and Autopilot](https://www.stacksync.com/integrations/autopilot-and-customer-io) - [Customer.io and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-customer-io) - [Customer.io and OpenAI](https://www.stacksync.com/integrations/customer-io-and-openai) - [Customer.io and Pinecone](https://www.stacksync.com/integrations/customer-io-and-pinecone) ### Developer tools · 9 - [Customer.io and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-customer-io) - [Customer.io and Datadog](https://www.stacksync.com/integrations/customer-io-and-datadog) - [Customer.io and Jira](https://www.stacksync.com/integrations/customer-io-and-jira) - [Customer.io and JMS](https://www.stacksync.com/integrations/customer-io-and-jms) - [Customer.io and LDAP](https://www.stacksync.com/integrations/customer-io-and-ldap) - [Customer.io and New Relic](https://www.stacksync.com/integrations/customer-io-and-newrelic) - [Customer.io and Opsgenie](https://www.stacksync.com/integrations/customer-io-and-opsgenie) - [Customer.io and PagerDuty](https://www.stacksync.com/integrations/customer-io-and-pagerduty) - [Customer.io and RabbitMQ](https://www.stacksync.com/integrations/customer-io-and-rabbitmq) ### Human resources · 11 - [Customer.io and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-customer-io) - [Customer.io and Greenhouse](https://www.stacksync.com/integrations/customer-io-and-greenhouse) - [Customer.io and Hibob](https://www.stacksync.com/integrations/customer-io-and-hibob) - [Customer.io and Jobvite](https://www.stacksync.com/integrations/customer-io-and-jobvite) - [Customer.io and Lever](https://www.stacksync.com/integrations/customer-io-and-lever) - [Customer.io and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/customer-io-and-oracle-fusion-cloud-hcm) - [Customer.io and Paylocity](https://www.stacksync.com/integrations/customer-io-and-paylocity) - [Customer.io and SmartRecruiters](https://www.stacksync.com/integrations/customer-io-and-smartrecruiters) - [Customer.io and Success Factors](https://www.stacksync.com/integrations/customer-io-and-success-factors) - [Customer.io and UKG Pro](https://www.stacksync.com/integrations/customer-io-and-ukg-pro) - [Customer.io and UKG Ready](https://www.stacksync.com/integrations/customer-io-and-ukg-ready) ### Security and identity · 6 - [Customer.io and Active Directory](https://www.stacksync.com/integrations/active-directory-and-customer-io) - [Customer.io and Auth0](https://www.stacksync.com/integrations/auth0-and-customer-io) - [Customer.io and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-customer-io) - [Customer.io and JumpCloud](https://www.stacksync.com/integrations/customer-io-and-jumpcloud) - [Customer.io and Okta](https://www.stacksync.com/integrations/customer-io-and-okta) - [Customer.io and OneLogin](https://www.stacksync.com/integrations/customer-io-and-onelogin) ### Storage · 4 - [Customer.io and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-customer-io) - [Customer.io and Box](https://www.stacksync.com/integrations/box-and-customer-io) - [Customer.io and Egnyte](https://www.stacksync.com/integrations/customer-io-and-egnyte) - [Customer.io and SharePoint](https://www.stacksync.com/integrations/customer-io-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/)