---
title: "Citus connector: setup and compatibility | Stacksync"
description: "Citus integration planning: Distributed tables, Reference tables and Local tables. Compatibility, identity, dependencies, and validation."
canonical: https://www.stacksync.com/connectors/citus
last_modified: 2026-09-15
---

Database · Two-way sync platform

# Citus 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 Citus workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Distributed tables, Reference tables and Local tables.

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.

- **Distributed tables**
- **Reference tables**
- **Local tables**

**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=citus)

## 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

## Citus records to discuss.

These Citus record examples help scope a technical review. They are not a list of verified Stacksync operations.

Distributed tables

Identify this record type and the operation you need to review with Stacksync.

Reference tables

Identify this record type and the operation you need to review with Stacksync.

Local tables

Identify this record type and the operation you need to review with Stacksync.

### See 3 more record examples

Schemas

Identify this record type and the operation you need to review with Stacksync.

Views

Identify this record type and the operation you need to review with Stacksync.

Sequences

Identify this record type and the operation you need to review with Stacksync.

Connection setup

## Citus connection requirements.

Review Citus 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 Citus account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Citus, including read/write support, authentication, and initial-load limits.

Integration design

## Match records and fields for your Citus integration.

Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system.

Use these design questions to prepare a representative record and the business rules your integration must preserve.

### Explore record matching and field-mapping checks

Citus **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

Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema.

Load related records in the right order

List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label.

### Mapping checks by record type

#### Distributed tables, Reference tables and Local tables

Confirm object support with Stacksync

Identity

Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema.

Fields to consider

Local record key · External application ID · Required business fields · Parent record references

Related records to resolve first

List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label.

Test before going live

Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record.

[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 Citus integration in four steps.

Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure.

### View the four setup tests and expected results

1. ### Verify Citus connectivity and database privileges

   After confirming an implementation path, validate the selected access method from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture.

   **Expected result:** The approved role can access the selected data and capture later changes without depending on an administrator’s personal session.
2. ### Test record matching for Distributed tables, Reference tables and Local tables

   Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record.

   **Expected result:** Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure.
3. ### Test the operation your workflow needs

   Review one Citus 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 Citus integration.

### Diagnose record matching, delayed changes, and rejected operations

A Citus record appears under the wrong destination record

Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema. List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Repair the ID relationship before repeating the operation.

The first load looks correct but later results differ

Confirm the selected Citus implementation’s change-detection method for Distributed tables, Reference tables and Local tables. 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 Citus 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 Citus workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=citus)

## Citus 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

## Citus connector FAQ

### How should I plan an integration with Citus?

Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. 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 Citus connector write changes back?

Write-back support is not established for this connection. Review the Citus records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

### Which identifiers should I preserve for Citus data?

Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema.

### Which related records should I load first for Citus?

List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label.

### How do I validate Citus changes after the initial load?

Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure.

### What will we cover in a Citus integration demo?

Start with one workflow and a sample record from Distributed tables, Reference tables and Local tables. 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 Citus 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 Citus and another app or database.

#### Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Citus. The assistant checks what each app supports, for example:

- “Build a workflow that messages our team in Slack when a Citus record changes.”
- “Create a Genie that answers questions about our Citus 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 Citus 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

- [Citus and Mixpanel](https://www.stacksync.com/integrations/citus-and-mixpanel)
- [Citus and SAP Business ByDesign](https://www.stacksync.com/integrations/citus-and-sap-business-bydesign)
- [Citus and GitHub](https://www.stacksync.com/integrations/citus-and-github)
- [Citus and Iterable](https://www.stacksync.com/integrations/citus-and-iterable)
- [BigQuery and Citus](https://www.stacksync.com/integrations/bigquery-and-citus)
- [Citus and UKG Pro](https://www.stacksync.com/integrations/citus-and-ukg-pro)
- [Citus and Snowflake](https://www.stacksync.com/integrations/citus-and-snowflake)
- [Amazon RDS and Citus](https://www.stacksync.com/integrations/amazon-rds-and-citus)

### CRM · 29

- [Citus and 6sense](https://www.stacksync.com/integrations/6sense-and-citus)
- [Citus and Affinity](https://www.stacksync.com/integrations/affinity-and-citus)
- [Citus and Attio](https://www.stacksync.com/integrations/attio-and-citus)
- [Citus and Chorusai](https://www.stacksync.com/integrations/chorusai-and-citus)
- [Citus and Close](https://www.stacksync.com/integrations/citus-and-close)
- [Citus and Copper CRM](https://www.stacksync.com/integrations/citus-and-copper-crm)
- [Citus and Dun & Bradstreet](https://www.stacksync.com/integrations/citus-and-dun-bradstreet)
- [Citus and Freshsales](https://www.stacksync.com/integrations/citus-and-freshsales)
- [Citus and Freshworks CRM](https://www.stacksync.com/integrations/citus-and-freshworks-crm)
- [Citus and Gong](https://www.stacksync.com/integrations/citus-and-gong)
- [Citus and Gorgias](https://www.stacksync.com/integrations/citus-and-gorgias)
- [Citus and HubSpot](https://www.stacksync.com/integrations/citus-and-hubspot)
- [Citus and Infor CRM](https://www.stacksync.com/integrations/citus-and-infor-crm)
- [Citus and Insightly](https://www.stacksync.com/integrations/citus-and-insightly)
- [Citus and Intercom](https://www.stacksync.com/integrations/citus-and-intercom)
- [Citus and Kommo](https://www.stacksync.com/integrations/citus-and-kommo)
- [Citus and Outreach](https://www.stacksync.com/integrations/citus-and-outreach)
- [Citus and Pipedrive](https://www.stacksync.com/integrations/citus-and-pipedrive)
- [Citus and Salesforce](https://www.stacksync.com/integrations/citus-and-salesforce)
- [Citus and Salesloft](https://www.stacksync.com/integrations/citus-and-salesloft)
- [Citus and SAP Sales Cloud](https://www.stacksync.com/integrations/citus-and-sap-sales-cloud)
- [Citus and Seismic](https://www.stacksync.com/integrations/citus-and-seismic)
- [Citus and Shopify](https://www.stacksync.com/integrations/citus-and-shopify)
- [Citus and SugarCRM](https://www.stacksync.com/integrations/citus-and-sugarcrm)
- [Citus and Veeva CRM](https://www.stacksync.com/integrations/citus-and-veeva-crm)
- [Citus and Vtiger CRM](https://www.stacksync.com/integrations/citus-and-vtiger-crm)
- [Citus and Xactly](https://www.stacksync.com/integrations/citus-and-xactly)
- [Citus and Zoho CRM](https://www.stacksync.com/integrations/citus-and-zoho-crm)
- [Citus and Zoho SalesIQ](https://www.stacksync.com/integrations/citus-and-zoho-salesiq)

### ERP · 24

- [Citus and Acumatica](https://www.stacksync.com/integrations/acumatica-and-citus)
- [Citus and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-citus)
- [Citus and Cin7](https://www.stacksync.com/integrations/cin7-and-citus)
- [Citus and Dynamics 365 Business Central](https://www.stacksync.com/integrations/citus-and-microsoft-dynamics-365-business-central)
- [Citus and Epicor ERP](https://www.stacksync.com/integrations/citus-and-epicor-erp)
- [Citus and Infor LN](https://www.stacksync.com/integrations/citus-and-infor-ln)
- [Citus and Infor M3](https://www.stacksync.com/integrations/citus-and-infor-m3)
- [Citus and Linnworks](https://www.stacksync.com/integrations/citus-and-linnworks)
- [Citus and Microsoft Dynamics GP](https://www.stacksync.com/integrations/citus-and-microsoft-dynamics-gp)
- [Citus and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/citus-and-microsoft-dynamics-nav)
- [Citus and NetSuite](https://www.stacksync.com/integrations/citus-and-netsuite)
- [Citus and Odoo](https://www.stacksync.com/integrations/citus-and-odoo)
- [Citus and Plex ERP](https://www.stacksync.com/integrations/citus-and-plex-erp)
- [Citus and QAD ERP](https://www.stacksync.com/integrations/citus-and-qad-erp)
- [Citus and Sage 100](https://www.stacksync.com/integrations/citus-and-sage-100)
- [Citus and Sage 300](https://www.stacksync.com/integrations/citus-and-sage-300)
- [Citus and Sage Intacct](https://www.stacksync.com/integrations/citus-and-sage-intacct)
- [Citus and Sage X3](https://www.stacksync.com/integrations/citus-and-sage-x3)
- [Citus and SAP](https://www.stacksync.com/integrations/citus-and-sap)
- [Citus and SAP Business ByDesign](https://www.stacksync.com/integrations/citus-and-sap-business-bydesign)
- [Citus and SAP Business One](https://www.stacksync.com/integrations/citus-and-sap-business-one)
- [Citus and SAP S/4HANA](https://www.stacksync.com/integrations/citus-and-sap-s4hana)
- [Citus and Syspro](https://www.stacksync.com/integrations/citus-and-syspro)
- [Citus and TikTok Shop](https://www.stacksync.com/integrations/citus-and-tiktok)

### Database · 15

- [Citus and Airtable](https://www.stacksync.com/integrations/airtable-and-citus)
- [Citus and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-citus)
- [Citus and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-citus)
- [Citus and Elasticsearch](https://www.stacksync.com/integrations/citus-and-elasticsearch)
- [Citus and Firebase](https://www.stacksync.com/integrations/citus-and-firebase)
- [Citus and InfluxDB](https://www.stacksync.com/integrations/citus-and-influxdb)
- [Citus and MarkLogic](https://www.stacksync.com/integrations/citus-and-marklogic)
- [Citus and MongoDB](https://www.stacksync.com/integrations/citus-and-mongodb)
- [Citus and MySQL](https://www.stacksync.com/integrations/citus-and-mysql)
- [Citus and Neo4j](https://www.stacksync.com/integrations/citus-and-neo4j)
- [Citus and PostgreSQL](https://www.stacksync.com/integrations/citus-and-postgresql)
- [Citus and SAP HANA](https://www.stacksync.com/integrations/citus-and-sap-hana)
- [Citus and SQL Server](https://www.stacksync.com/integrations/citus-and-sql-server)
- [Citus and Supabase](https://www.stacksync.com/integrations/citus-and-supabase)
- [Citus and VoltDB](https://www.stacksync.com/integrations/citus-and-voltdb)

### Data warehouse · 8

- [Citus and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-citus)
- [Citus and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-citus)
- [Citus and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-citus)
- [Citus and BigQuery](https://www.stacksync.com/integrations/bigquery-and-citus)
- [Citus and ClickHouse](https://www.stacksync.com/integrations/citus-and-clickhouse)
- [Citus and Databricks](https://www.stacksync.com/integrations/citus-and-databricks)
- [Citus and Google Cloud Platform](https://www.stacksync.com/integrations/citus-and-google-cloud-platform)
- [Citus and Snowflake](https://www.stacksync.com/integrations/citus-and-snowflake)

### Business productivity · 30

- [Citus and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-citus)
- [Citus and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-citus)
- [Citus and Asana](https://www.stacksync.com/integrations/asana-and-citus)
- [Citus and Atlassian](https://www.stacksync.com/integrations/atlassian-and-citus)
- [Citus and Braze](https://www.stacksync.com/integrations/braze-and-citus)
- [Citus and Campfire](https://www.stacksync.com/integrations/campfire-and-citus)
- [Citus and ConnectWise](https://www.stacksync.com/integrations/citus-and-connectwise)
- [Citus and Docusign](https://www.stacksync.com/integrations/citus-and-docusign)
- [Citus and eClinicalWorks](https://www.stacksync.com/integrations/citus-and-eclinicalworks)
- [Citus and Front](https://www.stacksync.com/integrations/citus-and-front)
- [Citus and Gainsight](https://www.stacksync.com/integrations/citus-and-gainsight)
- [Citus and GitHub](https://www.stacksync.com/integrations/citus-and-github)
- [Citus and Google Sheets](https://www.stacksync.com/integrations/citus-and-google-sheets)
- [Citus and Ironclad](https://www.stacksync.com/integrations/citus-and-ironclad)
- [Citus and Klaviyo](https://www.stacksync.com/integrations/citus-and-klaviyo)
- [Citus and Microsoft 365](https://www.stacksync.com/integrations/citus-and-microsoft-365)
- [Citus and Microsoft Dynamics 365](https://www.stacksync.com/integrations/citus-and-microsoft-dynamics-365)
- [Citus and Microsoft Teams](https://www.stacksync.com/integrations/citus-and-microsoft-teams)
- [Citus and Monday](https://www.stacksync.com/integrations/citus-and-monday)
- [Citus and Notion](https://www.stacksync.com/integrations/citus-and-notion)
- [Citus and Quip](https://www.stacksync.com/integrations/citus-and-quip)
- [Citus and SendGrid](https://www.stacksync.com/integrations/citus-and-sendgrid)
- [Citus and ServiceMax](https://www.stacksync.com/integrations/citus-and-servicemax)
- [Citus and ServiceNow](https://www.stacksync.com/integrations/citus-and-servicenow)
- [Citus and Slack](https://www.stacksync.com/integrations/citus-and-slack)
- [Citus and Smartsheet](https://www.stacksync.com/integrations/citus-and-smartsheet)
- [Citus and SysAid](https://www.stacksync.com/integrations/citus-and-sysaid)
- [Citus and Twilio](https://www.stacksync.com/integrations/citus-and-twilio)
- [Citus and Wrike](https://www.stacksync.com/integrations/citus-and-wrike)
- [Citus and Zendesk](https://www.stacksync.com/integrations/citus-and-zendesk)

### Accounting and finance · 13

- [Citus and Adyen](https://www.stacksync.com/integrations/adyen-and-citus)
- [Citus and Anaplan](https://www.stacksync.com/integrations/anaplan-and-citus)
- [Citus and BILL](https://www.stacksync.com/integrations/bill-and-citus)
- [Citus and Braintree](https://www.stacksync.com/integrations/braintree-and-citus)
- [Citus and Chargebee](https://www.stacksync.com/integrations/chargebee-and-citus)
- [Citus and Coupa](https://www.stacksync.com/integrations/citus-and-coupa)
- [Citus and Navan](https://www.stacksync.com/integrations/citus-and-navan)
- [Citus and QuickBooks](https://www.stacksync.com/integrations/citus-and-quickbooks)
- [Citus and Ramp](https://www.stacksync.com/integrations/citus-and-ramp)
- [Citus and Recurly](https://www.stacksync.com/integrations/citus-and-recurly)
- [Citus and Stripe](https://www.stacksync.com/integrations/citus-and-stripe)
- [Citus and Workday](https://www.stacksync.com/integrations/citus-and-workday)
- [Citus and Zuora](https://www.stacksync.com/integrations/citus-and-zuora)

### AI · 4

- [Citus and Autopilot](https://www.stacksync.com/integrations/autopilot-and-citus)
- [Citus and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-citus)
- [Citus and OpenAI](https://www.stacksync.com/integrations/citus-and-openai)
- [Citus and Pinecone](https://www.stacksync.com/integrations/citus-and-pinecone)

### Analytics · 6

- [Citus and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-citus)
- [Citus and Microsoft Power BI](https://www.stacksync.com/integrations/citus-and-microsoft-power-bi)
- [Citus and Mixpanel](https://www.stacksync.com/integrations/citus-and-mixpanel)
- [Citus and Pendo](https://www.stacksync.com/integrations/citus-and-pendo)
- [Citus and Splunk](https://www.stacksync.com/integrations/citus-and-splunk)
- [Citus and Tableau](https://www.stacksync.com/integrations/citus-and-tableau)

### Communications · 6

- [Citus and Aircall](https://www.stacksync.com/integrations/aircall-and-citus)
- [Citus and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-citus)
- [Citus and Gmail](https://www.stacksync.com/integrations/citus-and-gmail)
- [Citus and Infobip](https://www.stacksync.com/integrations/citus-and-infobip)
- [Citus and RingCentral](https://www.stacksync.com/integrations/citus-and-ringcentral)
- [Citus and Zoom](https://www.stacksync.com/integrations/citus-and-zoom)

### Developer tools · 9

- [Citus and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-citus)
- [Citus and Datadog](https://www.stacksync.com/integrations/citus-and-datadog)
- [Citus and Jira](https://www.stacksync.com/integrations/citus-and-jira)
- [Citus and JMS](https://www.stacksync.com/integrations/citus-and-jms)
- [Citus and LDAP](https://www.stacksync.com/integrations/citus-and-ldap)
- [Citus and New Relic](https://www.stacksync.com/integrations/citus-and-newrelic)
- [Citus and Opsgenie](https://www.stacksync.com/integrations/citus-and-opsgenie)
- [Citus and PagerDuty](https://www.stacksync.com/integrations/citus-and-pagerduty)
- [Citus and RabbitMQ](https://www.stacksync.com/integrations/citus-and-rabbitmq)

### E-commerce · 6

- [Citus and Akeneo](https://www.stacksync.com/integrations/akeneo-and-citus)
- [Citus and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-citus)
- [Citus and EasyPost](https://www.stacksync.com/integrations/citus-and-easypost)
- [Citus and Magento](https://www.stacksync.com/integrations/citus-and-magento)
- [Citus and Shipwire](https://www.stacksync.com/integrations/citus-and-shipwire)
- [Citus and Shopware](https://www.stacksync.com/integrations/citus-and-shopware)

### Human resources · 12

- [Citus and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-citus)
- [Citus and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-citus)
- [Citus and Greenhouse](https://www.stacksync.com/integrations/citus-and-greenhouse)
- [Citus and Hibob](https://www.stacksync.com/integrations/citus-and-hibob)
- [Citus and Jobvite](https://www.stacksync.com/integrations/citus-and-jobvite)
- [Citus and Lever](https://www.stacksync.com/integrations/citus-and-lever)
- [Citus and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/citus-and-oracle-fusion-cloud-hcm)
- [Citus and Paylocity](https://www.stacksync.com/integrations/citus-and-paylocity)
- [Citus and SmartRecruiters](https://www.stacksync.com/integrations/citus-and-smartrecruiters)
- [Citus and Success Factors](https://www.stacksync.com/integrations/citus-and-success-factors)
- [Citus and UKG Pro](https://www.stacksync.com/integrations/citus-and-ukg-pro)
- [Citus and UKG Ready](https://www.stacksync.com/integrations/citus-and-ukg-ready)

### Marketing · 8

- [Citus and Bingads](https://www.stacksync.com/integrations/bingads-and-citus)
- [Citus and Cvent](https://www.stacksync.com/integrations/citus-and-cvent)
- [Citus and Demandbase](https://www.stacksync.com/integrations/citus-and-demandbase)
- [Citus and Eloqua](https://www.stacksync.com/integrations/citus-and-eloqua)
- [Citus and Iterable](https://www.stacksync.com/integrations/citus-and-iterable)
- [Citus and Marketo](https://www.stacksync.com/integrations/citus-and-marketo)
- [Citus and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/citus-and-salesforce-marketing-cloud)
- [Citus and Twitter Ads](https://www.stacksync.com/integrations/citus-and-twitter-ads)

### Security and identity · 6

- [Citus and Active Directory](https://www.stacksync.com/integrations/active-directory-and-citus)
- [Citus and Auth0](https://www.stacksync.com/integrations/auth0-and-citus)
- [Citus and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-citus)
- [Citus and JumpCloud](https://www.stacksync.com/integrations/citus-and-jumpcloud)
- [Citus and Okta](https://www.stacksync.com/integrations/citus-and-okta)
- [Citus and OneLogin](https://www.stacksync.com/integrations/citus-and-onelogin)

### Storage · 4

- [Citus and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-citus)
- [Citus and Box](https://www.stacksync.com/integrations/box-and-citus)
- [Citus and Egnyte](https://www.stacksync.com/integrations/citus-and-egnyte)
- [Citus and SharePoint](https://www.stacksync.com/integrations/citus-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/)
