--- title: "Aircall connector: setup and compatibility | Stacksync" description: "Aircall integration guide: plan Contacts and Calls, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/aircall last_modified: 2026-09-15 --- Communications · Two-way sync platform # Aircall 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 Aircall workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Contacts, Calls and Users. 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. - **Contacts** - **Calls** - **Users** **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=aircall) ## 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 ## Aircall records to discuss. These Aircall record examples help scope a technical review. They are not a list of verified Stacksync operations. 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. Calls Retain the source call ID, provider/account context, and the explicit relationship to a CRM activity. A phone number alone cannot identify one call. Users Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. ### See 3 more record examples Numbers Identify this record type and the operation you need to review with Stacksync. Tags Identify this record type and the operation you need to review with Stacksync. Teams Keep group IDs and membership relationships separately from group names. Connection setup ## Aircall connection requirements. Review Aircall 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 Aircall account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Aircall, including read/write support, authentication, and initial-load limits. [Open the Aircall vendor API reference](https://developer.aircall.io/api-references/) ### Aircall API reference - [Aircall vendor API documentation](https://developer.aircall.io/api-references/) Integration design ## Match records and fields for your Aircall integration. Define whether the goal is reporting communication activity, resolving customer context, or executing a new message/call action. The last option needs its own confirmed write method and business authorization. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Aircall **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 #### 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. #### Calls Confirm object support with Stacksync Identity Retain the source call ID, provider/account context, and the explicit relationship to a CRM activity. A phone number alone cannot identify one call. Fields to consider Source call ID · Participant reference · Start time · Duration · Disposition or outcome Related records to resolve first Resolve participant and business-record identities, provider/account scope, and any related recording access. Test before going live Test two calls to the same number, a corrected disposition, and a delayed call completion. Verify that the intended CRM activity is updated once. #### Users Confirm object support with Stacksync Identity Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Fields to consider Source user ID · Tenant reference · Account status · Group references Related records to resolve first Resolve tenant and group references and establish a protected administrative-account policy. Test before going live Test a renamed login, disabled account, missing group, and a user existing in two tenants. #### Teams Confirm object support with Stacksync Identity Keep group IDs and membership relationships separately from group names. Fields to consider Source group ID · Member references · Tenant reference · Group type Related records to resolve first Resolve user and tenant identities before membership changes. Test before going live Test removed membership, nested groups, and equal group names in different tenants. #### Messages (SMS/MMS) 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 Aircall integration in four steps. The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. ### View the four setup tests and expected results 1. ### Confirm the intended Aircall account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Contacts 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:** The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. 3. ### Test the operation your workflow needs Review one Aircall 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 Aircall integration. ### Diagnose record matching, delayed changes, and rejected operations A Aircall 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 Aircall implementation’s change-detection method for Contacts, Calls and Users. 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 Aircall 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 Aircall workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=aircall) ## Aircall 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 ## Aircall connector FAQ ### How should I plan an integration with Aircall? Define whether the goal is reporting communication activity, resolving customer context, or executing a new message/call action. The last option needs its own confirmed write method and business authorization. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Aircall connector write changes back? Write-back support is not established for this connection. Review the Aircall records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Aircall 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 Aircall? Resolve the organization relationship and any owner or consent references required by the destination. ### How do I validate Aircall changes after the initial load? Test an email change, two records sharing an email, and a person associated with multiple organizations. The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. ### What will we cover in a Aircall integration demo? Start with one workflow and a sample record from Contacts, Calls and Users. 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 Aircall 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 Aircall and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Aircall. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Aircall record changes.” - “Create a Genie that answers questions about our Aircall 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 Aircall 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 - [Aircall and HubSpot](https://www.stacksync.com/integrations/aircall-and-hubspot) - [Aircall and Salesforce](https://www.stacksync.com/integrations/aircall-and-salesforce) - [Aircall and Attio](https://www.stacksync.com/integrations/aircall-and-attio) - [Aircall and Pipedrive](https://www.stacksync.com/integrations/aircall-and-pipedrive) - [Aircall and Intercom](https://www.stacksync.com/integrations/aircall-and-intercom) - [Aircall and Shopify](https://www.stacksync.com/integrations/aircall-and-shopify) - [Aircall and Streak CRM](https://www.stacksync.com/integrations/aircall-and-streak-crm) - [Aircall and Auth0](https://www.stacksync.com/integrations/aircall-and-auth0) ### CRM · 41 - [Aircall and Affinity](https://www.stacksync.com/integrations/affinity-and-aircall) - [Aircall and Apollo.io](https://www.stacksync.com/integrations/aircall-and-apollo-io) - [Aircall and Attio](https://www.stacksync.com/integrations/aircall-and-attio) - [Aircall and Chorusai](https://www.stacksync.com/integrations/aircall-and-chorusai) - [Aircall and Clari](https://www.stacksync.com/integrations/aircall-and-clari) - [Aircall and Close](https://www.stacksync.com/integrations/aircall-and-close) - [Aircall and Copper CRM](https://www.stacksync.com/integrations/aircall-and-copper-crm) - [Aircall and Creatio CRM](https://www.stacksync.com/integrations/aircall-and-creatio-crm) - [Aircall and DealCloud](https://www.stacksync.com/integrations/aircall-and-dealcloud) - [Aircall and Folk CRM](https://www.stacksync.com/integrations/aircall-and-folk-crm) - [Aircall and Freshsales](https://www.stacksync.com/integrations/aircall-and-freshsales) - [Aircall and Freshworks CRM](https://www.stacksync.com/integrations/aircall-and-freshworks-crm) - [Aircall and Gladly](https://www.stacksync.com/integrations/aircall-and-gladly) - [Aircall and Gong](https://www.stacksync.com/integrations/aircall-and-gong) - [Aircall and Gorgias](https://www.stacksync.com/integrations/aircall-and-gorgias) - [Aircall and HubSpot](https://www.stacksync.com/integrations/aircall-and-hubspot) - [Aircall and Infor CRM](https://www.stacksync.com/integrations/aircall-and-infor-crm) - [Aircall and Insightly](https://www.stacksync.com/integrations/aircall-and-insightly) - [Aircall and Intercom](https://www.stacksync.com/integrations/aircall-and-intercom) - [Aircall and Kommo](https://www.stacksync.com/integrations/aircall-and-kommo) - [Aircall and Kustomer](https://www.stacksync.com/integrations/aircall-and-kustomer) - [Aircall and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/aircall-and-microsoft-dynamics-365-sales) - [Aircall and Nimble](https://www.stacksync.com/integrations/aircall-and-nimble) - [Aircall and Nutshell](https://www.stacksync.com/integrations/aircall-and-nutshell) - [Aircall and Oracle CX Sales](https://www.stacksync.com/integrations/aircall-and-oracle-cx-sales) - [Aircall and Outreach](https://www.stacksync.com/integrations/aircall-and-outreach) - [Aircall and Pipedrive](https://www.stacksync.com/integrations/aircall-and-pipedrive) - [Aircall and Salesforce](https://www.stacksync.com/integrations/aircall-and-salesforce) - [Aircall and Salesloft](https://www.stacksync.com/integrations/aircall-and-salesloft) - [Aircall and SAP Sales Cloud](https://www.stacksync.com/integrations/aircall-and-sap-sales-cloud) - [Aircall and Seismic](https://www.stacksync.com/integrations/aircall-and-seismic) - [Aircall and Shopify](https://www.stacksync.com/integrations/aircall-and-shopify) - [Aircall and Streak CRM](https://www.stacksync.com/integrations/aircall-and-streak-crm) - [Aircall and SugarCRM](https://www.stacksync.com/integrations/aircall-and-sugarcrm) - [Aircall and Twenty CRM](https://www.stacksync.com/integrations/aircall-and-twenty-crm) - [Aircall and Veeva CRM](https://www.stacksync.com/integrations/aircall-and-veeva-crm) - [Aircall and Vitally](https://www.stacksync.com/integrations/aircall-and-vitally) - [Aircall and Vtiger CRM](https://www.stacksync.com/integrations/aircall-and-vtiger-crm) - [Aircall and Xactly](https://www.stacksync.com/integrations/aircall-and-xactly) - [Aircall and Zoho CRM](https://www.stacksync.com/integrations/aircall-and-zoho-crm) - [Aircall and Zoho SalesIQ](https://www.stacksync.com/integrations/aircall-and-zoho-salesiq) ### Database · 49 - [Aircall and Airtable](https://www.stacksync.com/integrations/aircall-and-airtable) - [Aircall and Amazon Aurora](https://www.stacksync.com/integrations/aircall-and-amazon-aurora) - [Aircall and Amazon DynamoDB](https://www.stacksync.com/integrations/aircall-and-dynamo-db) - [Aircall and Amazon DynamoDB](https://www.stacksync.com/integrations/aircall-and-amazon-dynamodb) - [Aircall and Amazon Lightsail](https://www.stacksync.com/integrations/aircall-and-amazon-lightsail) - [Aircall and Amazon RDS](https://www.stacksync.com/integrations/aircall-and-amazon-rds) - [Aircall and Apache Cassandra](https://www.stacksync.com/integrations/aircall-and-apache-cassandra) - [Aircall and AWS Aurora MySQL](https://www.stacksync.com/integrations/aircall-and-aws-aurora-mysql) - [Aircall and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aircall-and-aws-aurora-postgresql) - [Aircall and Azure Cosmos DB](https://www.stacksync.com/integrations/aircall-and-azure-cosmos-db) - [Aircall and Azure SQL Database](https://www.stacksync.com/integrations/aircall-and-azure-sql-database) - [Aircall and Citus](https://www.stacksync.com/integrations/aircall-and-citus) - [Aircall and CockroachDB](https://www.stacksync.com/integrations/aircall-and-cockroachdb) - [Aircall and Couchbase](https://www.stacksync.com/integrations/aircall-and-couchbase) - [Aircall and DuckDB](https://www.stacksync.com/integrations/aircall-and-duckdb) - [Aircall and Elasticsearch](https://www.stacksync.com/integrations/aircall-and-elasticsearch) - [Aircall and Firebase](https://www.stacksync.com/integrations/aircall-and-firebase) - [Aircall and Google AlloyDB](https://www.stacksync.com/integrations/aircall-and-google-alloydb) - [Aircall and Google Cloud Spanner](https://www.stacksync.com/integrations/aircall-and-google-cloud-spanner) - [Aircall and Google Cloud SQL](https://www.stacksync.com/integrations/aircall-and-google-cloud-sql) - [Aircall and IBM AS/400](https://www.stacksync.com/integrations/aircall-and-ibm-as400) - [Aircall and IBM Db2](https://www.stacksync.com/integrations/aircall-and-ibm-db2) - [Aircall and IBM Informix](https://www.stacksync.com/integrations/aircall-and-ibm-informix) - [Aircall and InfluxDB](https://www.stacksync.com/integrations/aircall-and-influxdb) - [Aircall and InterSystems IRIS](https://www.stacksync.com/integrations/aircall-and-intersystems-iris) - [Aircall and JDBC](https://www.stacksync.com/integrations/aircall-and-jdbc) - [Aircall and MariaDB](https://www.stacksync.com/integrations/aircall-and-mariadb) - [Aircall and MarkLogic](https://www.stacksync.com/integrations/aircall-and-marklogic) - [Aircall and MongoDB](https://www.stacksync.com/integrations/aircall-and-mongodb) - [Aircall and MySQL](https://www.stacksync.com/integrations/aircall-and-mysql) - [Aircall and Neo4j](https://www.stacksync.com/integrations/aircall-and-neo4j) - [Aircall and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/aircall-and-oci-database) - [Aircall and OpenSearch](https://www.stacksync.com/integrations/aircall-and-opensearch) - [Aircall and Oracle DB](https://www.stacksync.com/integrations/aircall-and-oracle-db) - [Aircall and Postgres Heroku](https://www.stacksync.com/integrations/aircall-and-postgres-heroku) - [Aircall and PostgreSQL](https://www.stacksync.com/integrations/aircall-and-postgresql) - [Aircall and RavenDB](https://www.stacksync.com/integrations/aircall-and-ravendb) - [Aircall and Redis Enterprise](https://www.stacksync.com/integrations/aircall-and-redis-enterprise) - [Aircall and Reltio](https://www.stacksync.com/integrations/aircall-and-reltio) - [Aircall and SAP ASE (Sybase)](https://www.stacksync.com/integrations/aircall-and-sap-ase-sybase) - [Aircall and SAP HANA](https://www.stacksync.com/integrations/aircall-and-sap-hana) - [Aircall and Scaleway Postgres](https://www.stacksync.com/integrations/aircall-and-scaleway-postgres) - [Aircall and SingleStore](https://www.stacksync.com/integrations/aircall-and-singlestore) - [Aircall and SQL Server](https://www.stacksync.com/integrations/aircall-and-sql-server) - [Aircall and Supabase](https://www.stacksync.com/integrations/aircall-and-supabase) - [Aircall and TiDB](https://www.stacksync.com/integrations/aircall-and-tidb) - [Aircall and TimescaleDB](https://www.stacksync.com/integrations/aircall-and-timescaledb) - [Aircall and VoltDB](https://www.stacksync.com/integrations/aircall-and-voltdb) - [Aircall and YugabyteDB](https://www.stacksync.com/integrations/aircall-and-yugabytedb) ### Data warehouse · 28 - [Aircall and Amazon Redshift](https://www.stacksync.com/integrations/aircall-and-amazon-redshift) - [Aircall and Amazon S3](https://www.stacksync.com/integrations/aircall-and-aws-s3) - [Aircall and Apache Doris](https://www.stacksync.com/integrations/aircall-and-apache-doris) - [Aircall and Apache Druid](https://www.stacksync.com/integrations/aircall-and-apache-druid) - [Aircall and Apache Hive](https://www.stacksync.com/integrations/aircall-and-apache-hive) - [Aircall and Apache Impala](https://www.stacksync.com/integrations/aircall-and-apache-impala) - [Aircall and Apache Pinot](https://www.stacksync.com/integrations/aircall-and-apache-pinot) - [Aircall and Azure Synapse Analytics](https://www.stacksync.com/integrations/aircall-and-azure-synapse-analytics) - [Aircall and BigQuery](https://www.stacksync.com/integrations/aircall-and-bigquery) - [Aircall and ClickHouse](https://www.stacksync.com/integrations/aircall-and-clickhouse) - [Aircall and Cloudera Data Platform](https://www.stacksync.com/integrations/aircall-and-cloudera-data-platform) - [Aircall and Databricks](https://www.stacksync.com/integrations/aircall-and-databricks) - [Aircall and Dremio](https://www.stacksync.com/integrations/aircall-and-dremio) - [Aircall and Exasol](https://www.stacksync.com/integrations/aircall-and-exasol) - [Aircall and Firebolt](https://www.stacksync.com/integrations/aircall-and-firebolt) - [Aircall and Google Cloud Platform](https://www.stacksync.com/integrations/aircall-and-google-cloud-platform) - [Aircall and Greenplum](https://www.stacksync.com/integrations/aircall-and-greenplum) - [Aircall and IBM Netezza](https://www.stacksync.com/integrations/aircall-and-ibm-netezza) - [Aircall and Materialize](https://www.stacksync.com/integrations/aircall-and-materialize) - [Aircall and MotherDuck](https://www.stacksync.com/integrations/aircall-and-motherduck) - [Aircall and Rockset](https://www.stacksync.com/integrations/aircall-and-rockset) - [Aircall and Snowflake](https://www.stacksync.com/integrations/aircall-and-snowflake) - [Aircall and Starburst Enterprise](https://www.stacksync.com/integrations/aircall-and-starburst-enterprise) - [Aircall and StarRocks](https://www.stacksync.com/integrations/aircall-and-starrocks) - [Aircall and Teradata Vantage](https://www.stacksync.com/integrations/aircall-and-teradata-vantage) - [Aircall and Tinybird](https://www.stacksync.com/integrations/aircall-and-tinybird) - [Aircall and Vertica](https://www.stacksync.com/integrations/aircall-and-vertica) - [Aircall and Yellowbrick](https://www.stacksync.com/integrations/aircall-and-yellowbrick) ### Communications · 1 - [Aircall and Gmail](https://www.stacksync.com/integrations/aircall-and-gmail) ### Developer tools · 11 - [Aircall and Azure Service Bus](https://www.stacksync.com/integrations/aircall-and-azure-service-bus) - [Aircall and Datadog](https://www.stacksync.com/integrations/aircall-and-datadog) - [Aircall and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/aircall-and-google-pubsub) - [Aircall and Jira](https://www.stacksync.com/integrations/aircall-and-jira) - [Aircall and JMS](https://www.stacksync.com/integrations/aircall-and-jms) - [Aircall and LDAP](https://www.stacksync.com/integrations/aircall-and-ldap) - [Aircall and Microsoft Graph](https://www.stacksync.com/integrations/aircall-and-microsoft-graph) - [Aircall and New Relic](https://www.stacksync.com/integrations/aircall-and-newrelic) - [Aircall and Opsgenie](https://www.stacksync.com/integrations/aircall-and-opsgenie) - [Aircall and PagerDuty](https://www.stacksync.com/integrations/aircall-and-pagerduty) - [Aircall and RabbitMQ](https://www.stacksync.com/integrations/aircall-and-rabbitmq) ### E-commerce · 8 - [Aircall and Akeneo](https://www.stacksync.com/integrations/aircall-and-akeneo) - [Aircall and BigCommerce](https://www.stacksync.com/integrations/aircall-and-bigcommerce) - [Aircall and ChannelEngine](https://www.stacksync.com/integrations/aircall-and-channelengine) - [Aircall and EasyPost](https://www.stacksync.com/integrations/aircall-and-easypost) - [Aircall and Magento](https://www.stacksync.com/integrations/aircall-and-magento) - [Aircall and NuORDER](https://www.stacksync.com/integrations/aircall-and-nuorder) - [Aircall and Shipwire](https://www.stacksync.com/integrations/aircall-and-shipwire) - [Aircall and Shopware](https://www.stacksync.com/integrations/aircall-and-shopware) ### Human resources · 1 - [Aircall and BambooHR](https://www.stacksync.com/integrations/aircall-and-bamboohr) ### Marketing · 9 - [Aircall and Bingads](https://www.stacksync.com/integrations/aircall-and-bingads) - [Aircall and Cvent](https://www.stacksync.com/integrations/aircall-and-cvent) - [Aircall and Demandbase](https://www.stacksync.com/integrations/aircall-and-demandbase) - [Aircall and Eloqua](https://www.stacksync.com/integrations/aircall-and-eloqua) - [Aircall and Iterable](https://www.stacksync.com/integrations/aircall-and-iterable) - [Aircall and Marketo](https://www.stacksync.com/integrations/aircall-and-marketo) - [Aircall and RollWorks](https://www.stacksync.com/integrations/aircall-and-rollworks) - [Aircall and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/aircall-and-salesforce-marketing-cloud) - [Aircall and Twitter Ads](https://www.stacksync.com/integrations/aircall-and-twitter-ads) ### Security and identity · 6 - [Aircall and Active Directory](https://www.stacksync.com/integrations/active-directory-and-aircall) - [Aircall and Auth0](https://www.stacksync.com/integrations/aircall-and-auth0) - [Aircall and Azure Active Directory](https://www.stacksync.com/integrations/aircall-and-azure-active-directory) - [Aircall and JumpCloud](https://www.stacksync.com/integrations/aircall-and-jumpcloud) - [Aircall and Okta](https://www.stacksync.com/integrations/aircall-and-okta) - [Aircall and OneLogin](https://www.stacksync.com/integrations/aircall-and-onelogin) ### Storage · 4 - [Aircall and Amazon S3](https://www.stacksync.com/integrations/aircall-and-amazon-s3) - [Aircall and Box](https://www.stacksync.com/integrations/aircall-and-box) - [Aircall and Egnyte](https://www.stacksync.com/integrations/aircall-and-egnyte) - [Aircall and SharePoint](https://www.stacksync.com/integrations/aircall-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/)