--- title: "Infobip connector: setup and compatibility | Stacksync" description: "Infobip integration guide: plan Persons (People CDP) and SMS Messages, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/infobip last_modified: 2026-09-15 --- Communications · Two-way sync platform # Infobip 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 Infobip workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Persons (People CDP) and SMS Messages. 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. - **Persons (People CDP)** - **SMS Messages** - **WhatsApp Messages** **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=infobip) ## 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 ## Infobip records to discuss. These Infobip record examples help scope a technical review. They are not a list of verified Stacksync operations. Persons (People CDP) 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. SMS Messages Retain message ID, conversation/thread ID, channel, and sender identity. WhatsApp Messages Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Email Identify this record type and the operation you need to review with Stacksync. Conversations Identify this record type and the operation you need to review with Stacksync. Numbers / Senders Identify this record type and the operation you need to review with Stacksync. Connection setup ## Infobip connection requirements. Review Infobip 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 Infobip account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Infobip, including read/write support, authentication, and initial-load limits. [Open the Infobip vendor API reference](https://www.infobip.com/docs/api) ### Infobip API reference - [Infobip vendor API documentation](https://www.infobip.com/docs/api) Integration design ## Match records and fields for your Infobip 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 Infobip **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 #### Persons (People CDP) 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. #### SMS 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 Infobip 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 Infobip 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 Persons (People CDP) 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 Infobip 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 Infobip integration. ### Diagnose record matching, delayed changes, and rejected operations A Infobip 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 Infobip implementation’s change-detection method for Persons (People CDP) and SMS Messages. 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 Infobip 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 Infobip workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=infobip) ## Infobip 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 ## Infobip connector FAQ ### How should I plan an integration with Infobip? 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 Infobip connector write changes back? Write-back support is not established for this connection. Review the Infobip records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Infobip 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 Infobip? Resolve the organization relationship and any owner or consent references required by the destination. ### How do I validate Infobip 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 Infobip integration demo? Start with one workflow and a sample record from Persons (People CDP) and SMS Messages. 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 Infobip 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 Infobip and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Infobip. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Infobip record changes.” - “Create a Genie that answers questions about our Infobip 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 Infobip 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 - [Infobip and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/infobip-and-microsoft-dynamics-365-sales) - [Infobip and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/infobip-and-salesforce-marketing-cloud) - [Infobip and Materialize](https://www.stacksync.com/integrations/infobip-and-materialize) - [Infobip and Iterable](https://www.stacksync.com/integrations/infobip-and-iterable) - [Infobip and Rockset](https://www.stacksync.com/integrations/infobip-and-rockset) - [Amazon DynamoDB and Infobip](https://www.stacksync.com/integrations/dynamo-db-and-infobip) - [Gorgias and Infobip](https://www.stacksync.com/integrations/gorgias-and-infobip) - [Infobip and SharePoint](https://www.stacksync.com/integrations/infobip-and-sharepoint) ### CRM · 41 - [Infobip and Affinity](https://www.stacksync.com/integrations/affinity-and-infobip) - [Infobip and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-infobip) - [Infobip and Attio](https://www.stacksync.com/integrations/attio-and-infobip) - [Infobip and Chorusai](https://www.stacksync.com/integrations/chorusai-and-infobip) - [Infobip and Clari](https://www.stacksync.com/integrations/clari-and-infobip) - [Infobip and Close](https://www.stacksync.com/integrations/close-and-infobip) - [Infobip and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-infobip) - [Infobip and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-infobip) - [Infobip and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-infobip) - [Infobip and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-infobip) - [Infobip and Freshsales](https://www.stacksync.com/integrations/freshsales-and-infobip) - [Infobip and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-infobip) - [Infobip and Gladly](https://www.stacksync.com/integrations/gladly-and-infobip) - [Infobip and Gong](https://www.stacksync.com/integrations/gong-and-infobip) - [Infobip and Gorgias](https://www.stacksync.com/integrations/gorgias-and-infobip) - [Infobip and HubSpot](https://www.stacksync.com/integrations/hubspot-and-infobip) - [Infobip and Infor CRM](https://www.stacksync.com/integrations/infobip-and-infor-crm) - [Infobip and Insightly](https://www.stacksync.com/integrations/infobip-and-insightly) - [Infobip and Intercom](https://www.stacksync.com/integrations/infobip-and-intercom) - [Infobip and Kommo](https://www.stacksync.com/integrations/infobip-and-kommo) - [Infobip and Kustomer](https://www.stacksync.com/integrations/infobip-and-kustomer) - [Infobip and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/infobip-and-microsoft-dynamics-365-sales) - [Infobip and Nimble](https://www.stacksync.com/integrations/infobip-and-nimble) - [Infobip and Nutshell](https://www.stacksync.com/integrations/infobip-and-nutshell) - [Infobip and Oracle CX Sales](https://www.stacksync.com/integrations/infobip-and-oracle-cx-sales) - [Infobip and Outreach](https://www.stacksync.com/integrations/infobip-and-outreach) - [Infobip and Pipedrive](https://www.stacksync.com/integrations/infobip-and-pipedrive) - [Infobip and Salesforce](https://www.stacksync.com/integrations/infobip-and-salesforce) - [Infobip and Salesloft](https://www.stacksync.com/integrations/infobip-and-salesloft) - [Infobip and SAP Sales Cloud](https://www.stacksync.com/integrations/infobip-and-sap-sales-cloud) - [Infobip and Seismic](https://www.stacksync.com/integrations/infobip-and-seismic) - [Infobip and Shopify](https://www.stacksync.com/integrations/infobip-and-shopify) - [Infobip and Streak CRM](https://www.stacksync.com/integrations/infobip-and-streak-crm) - [Infobip and SugarCRM](https://www.stacksync.com/integrations/infobip-and-sugarcrm) - [Infobip and Twenty CRM](https://www.stacksync.com/integrations/infobip-and-twenty-crm) - [Infobip and Veeva CRM](https://www.stacksync.com/integrations/infobip-and-veeva-crm) - [Infobip and Vitally](https://www.stacksync.com/integrations/infobip-and-vitally) - [Infobip and Vtiger CRM](https://www.stacksync.com/integrations/infobip-and-vtiger-crm) - [Infobip and Xactly](https://www.stacksync.com/integrations/infobip-and-xactly) - [Infobip and Zoho CRM](https://www.stacksync.com/integrations/infobip-and-zoho-crm) - [Infobip and Zoho SalesIQ](https://www.stacksync.com/integrations/infobip-and-zoho-salesiq) ### Database · 49 - [Infobip and Airtable](https://www.stacksync.com/integrations/airtable-and-infobip) - [Infobip and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-infobip) - [Infobip and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-infobip) - [Infobip and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-infobip) - [Infobip and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-infobip) - [Infobip and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-infobip) - [Infobip and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-infobip) - [Infobip and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-infobip) - [Infobip and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-infobip) - [Infobip and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-infobip) - [Infobip and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-infobip) - [Infobip and Citus](https://www.stacksync.com/integrations/citus-and-infobip) - [Infobip and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-infobip) - [Infobip and Couchbase](https://www.stacksync.com/integrations/couchbase-and-infobip) - [Infobip and DuckDB](https://www.stacksync.com/integrations/duckdb-and-infobip) - [Infobip and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-infobip) - [Infobip and Firebase](https://www.stacksync.com/integrations/firebase-and-infobip) - [Infobip and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-infobip) - [Infobip and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-infobip) - [Infobip and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-infobip) - [Infobip and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-infobip) - [Infobip and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-infobip) - [Infobip and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-infobip) - [Infobip and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-infobip) - [Infobip and InterSystems IRIS](https://www.stacksync.com/integrations/infobip-and-intersystems-iris) - [Infobip and JDBC](https://www.stacksync.com/integrations/infobip-and-jdbc) - [Infobip and MariaDB](https://www.stacksync.com/integrations/infobip-and-mariadb) - [Infobip and MarkLogic](https://www.stacksync.com/integrations/infobip-and-marklogic) - [Infobip and MongoDB](https://www.stacksync.com/integrations/infobip-and-mongodb) - [Infobip and MySQL](https://www.stacksync.com/integrations/infobip-and-mysql) - [Infobip and Neo4j](https://www.stacksync.com/integrations/infobip-and-neo4j) - [Infobip and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/infobip-and-oci-database) - [Infobip and OpenSearch](https://www.stacksync.com/integrations/infobip-and-opensearch) - [Infobip and Oracle DB](https://www.stacksync.com/integrations/infobip-and-oracle-db) - [Infobip and Postgres Heroku](https://www.stacksync.com/integrations/infobip-and-postgres-heroku) - [Infobip and PostgreSQL](https://www.stacksync.com/integrations/infobip-and-postgresql) - [Infobip and RavenDB](https://www.stacksync.com/integrations/infobip-and-ravendb) - [Infobip and Redis Enterprise](https://www.stacksync.com/integrations/infobip-and-redis-enterprise) - [Infobip and Reltio](https://www.stacksync.com/integrations/infobip-and-reltio) - [Infobip and SAP ASE (Sybase)](https://www.stacksync.com/integrations/infobip-and-sap-ase-sybase) - [Infobip and SAP HANA](https://www.stacksync.com/integrations/infobip-and-sap-hana) - [Infobip and Scaleway Postgres](https://www.stacksync.com/integrations/infobip-and-scaleway-postgres) - [Infobip and SingleStore](https://www.stacksync.com/integrations/infobip-and-singlestore) - [Infobip and SQL Server](https://www.stacksync.com/integrations/infobip-and-sql-server) - [Infobip and Supabase](https://www.stacksync.com/integrations/infobip-and-supabase) - [Infobip and TiDB](https://www.stacksync.com/integrations/infobip-and-tidb) - [Infobip and TimescaleDB](https://www.stacksync.com/integrations/infobip-and-timescaledb) - [Infobip and VoltDB](https://www.stacksync.com/integrations/infobip-and-voltdb) - [Infobip and YugabyteDB](https://www.stacksync.com/integrations/infobip-and-yugabytedb) ### Data warehouse · 28 - [Infobip and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-infobip) - [Infobip and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-infobip) - [Infobip and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-infobip) - [Infobip and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-infobip) - [Infobip and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-infobip) - [Infobip and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-infobip) - [Infobip and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-infobip) - [Infobip and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-infobip) - [Infobip and BigQuery](https://www.stacksync.com/integrations/bigquery-and-infobip) - [Infobip and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-infobip) - [Infobip and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-infobip) - [Infobip and Databricks](https://www.stacksync.com/integrations/databricks-and-infobip) - [Infobip and Dremio](https://www.stacksync.com/integrations/dremio-and-infobip) - [Infobip and Exasol](https://www.stacksync.com/integrations/exasol-and-infobip) - [Infobip and Firebolt](https://www.stacksync.com/integrations/firebolt-and-infobip) - [Infobip and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-infobip) - [Infobip and Greenplum](https://www.stacksync.com/integrations/greenplum-and-infobip) - [Infobip and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-infobip) - [Infobip and Materialize](https://www.stacksync.com/integrations/infobip-and-materialize) - [Infobip and MotherDuck](https://www.stacksync.com/integrations/infobip-and-motherduck) - [Infobip and Rockset](https://www.stacksync.com/integrations/infobip-and-rockset) - [Infobip and Snowflake](https://www.stacksync.com/integrations/infobip-and-snowflake) - [Infobip and Starburst Enterprise](https://www.stacksync.com/integrations/infobip-and-starburst-enterprise) - [Infobip and StarRocks](https://www.stacksync.com/integrations/infobip-and-starrocks) - [Infobip and Teradata Vantage](https://www.stacksync.com/integrations/infobip-and-teradata-vantage) - [Infobip and Tinybird](https://www.stacksync.com/integrations/infobip-and-tinybird) - [Infobip and Vertica](https://www.stacksync.com/integrations/infobip-and-vertica) - [Infobip and Yellowbrick](https://www.stacksync.com/integrations/infobip-and-yellowbrick) ### Communications · 1 - [Infobip and Gmail](https://www.stacksync.com/integrations/gmail-and-infobip) ### Developer tools · 11 - [Infobip and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-infobip) - [Infobip and Datadog](https://www.stacksync.com/integrations/datadog-and-infobip) - [Infobip and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/google-pubsub-and-infobip) - [Infobip and Jira](https://www.stacksync.com/integrations/infobip-and-jira) - [Infobip and JMS](https://www.stacksync.com/integrations/infobip-and-jms) - [Infobip and LDAP](https://www.stacksync.com/integrations/infobip-and-ldap) - [Infobip and Microsoft Graph](https://www.stacksync.com/integrations/infobip-and-microsoft-graph) - [Infobip and New Relic](https://www.stacksync.com/integrations/infobip-and-newrelic) - [Infobip and Opsgenie](https://www.stacksync.com/integrations/infobip-and-opsgenie) - [Infobip and PagerDuty](https://www.stacksync.com/integrations/infobip-and-pagerduty) - [Infobip and RabbitMQ](https://www.stacksync.com/integrations/infobip-and-rabbitmq) ### E-commerce · 8 - [Infobip and Akeneo](https://www.stacksync.com/integrations/akeneo-and-infobip) - [Infobip and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-infobip) - [Infobip and ChannelEngine](https://www.stacksync.com/integrations/channelengine-and-infobip) - [Infobip and EasyPost](https://www.stacksync.com/integrations/easypost-and-infobip) - [Infobip and Magento](https://www.stacksync.com/integrations/infobip-and-magento) - [Infobip and NuORDER](https://www.stacksync.com/integrations/infobip-and-nuorder) - [Infobip and Shipwire](https://www.stacksync.com/integrations/infobip-and-shipwire) - [Infobip and Shopware](https://www.stacksync.com/integrations/infobip-and-shopware) ### Human resources · 1 - [Infobip and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-infobip) ### Marketing · 9 - [Infobip and Bingads](https://www.stacksync.com/integrations/bingads-and-infobip) - [Infobip and Cvent](https://www.stacksync.com/integrations/cvent-and-infobip) - [Infobip and Demandbase](https://www.stacksync.com/integrations/demandbase-and-infobip) - [Infobip and Eloqua](https://www.stacksync.com/integrations/eloqua-and-infobip) - [Infobip and Iterable](https://www.stacksync.com/integrations/infobip-and-iterable) - [Infobip and Marketo](https://www.stacksync.com/integrations/infobip-and-marketo) - [Infobip and RollWorks](https://www.stacksync.com/integrations/infobip-and-rollworks) - [Infobip and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/infobip-and-salesforce-marketing-cloud) - [Infobip and Twitter Ads](https://www.stacksync.com/integrations/infobip-and-twitter-ads) ### Security and identity · 6 - [Infobip and Active Directory](https://www.stacksync.com/integrations/active-directory-and-infobip) - [Infobip and Auth0](https://www.stacksync.com/integrations/auth0-and-infobip) - [Infobip and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-infobip) - [Infobip and JumpCloud](https://www.stacksync.com/integrations/infobip-and-jumpcloud) - [Infobip and Okta](https://www.stacksync.com/integrations/infobip-and-okta) - [Infobip and OneLogin](https://www.stacksync.com/integrations/infobip-and-onelogin) ### Storage · 4 - [Infobip and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-infobip) - [Infobip and Box](https://www.stacksync.com/integrations/box-and-infobip) - [Infobip and Egnyte](https://www.stacksync.com/integrations/egnyte-and-infobip) - [Infobip and SharePoint](https://www.stacksync.com/integrations/infobip-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/)