--- title: "Cvent connector: setup and compatibility | Stacksync" description: "Cvent integration guide: plan Events and Contacts, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/cvent last_modified: 2026-09-15 --- Marketing · Two-way sync platform # Cvent 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 Cvent workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Events and Contacts. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Events** - **Contacts** - **Attendees and Registrations** **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=cvent) ## 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 ## Cvent records to discuss. These Cvent record examples help scope a technical review. They are not a list of verified Stacksync operations. Events Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. 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. Attendees and Registrations Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Sessions Identify this record type and the operation you need to review with Stacksync. Speakers Identify this record type and the operation you need to review with Stacksync. Exhibitors Identify this record type and the operation you need to review with Stacksync. Connection setup ## Cvent connection requirements. Review Cvent 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 Cvent account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Cvent, including read/write support, authentication, and initial-load limits. [Open the Cvent vendor API reference](https://developers.cvent.com/docs/rest-api/overview) ### Cvent API reference - [Cvent vendor API documentation](https://developers.cvent.com/docs/rest-api/overview) Integration design ## Match records and fields for your Cvent integration. Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Cvent **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 Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Load related records in the right order Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. ### Mapping checks by record type #### Events Confirm object support with Stacksync Identity Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Fields to consider Source event ID · Event type · Occurred-at time · Related record ID · Payload version Related records to resolve first Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Test before going live Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. #### Contacts Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Cvent integration in four steps. An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window. ### View the four setup tests and expected results 1. ### Confirm the intended Cvent 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 Events Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. **Expected result:** An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window. 3. ### Test the operation your workflow needs Review one Cvent 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 Cvent integration. ### Diagnose record matching, delayed changes, and rejected operations A Cvent record appears under the wrong destination record Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Cvent implementation’s change-detection method for Events and Contacts. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Cvent 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 Cvent workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=cvent) ## Cvent 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 ## Cvent connector FAQ ### How should I plan an integration with Cvent? Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination. 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 Cvent connector write changes back? Write-back support is not established for this connection. Review the Cvent records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Cvent data? Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. ### Which related records should I load first for Cvent? Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. ### How do I validate Cvent changes after the initial load? Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window. ### What will we cover in a Cvent integration demo? Start with one workflow and a sample record from Events and Contacts. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Cvent 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 Cvent and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Cvent. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Cvent record changes.” - “Create a Genie that answers questions about our Cvent 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 Cvent 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 - [Cvent and Salesforce](https://www.stacksync.com/integrations/cvent-and-salesforce) - [Cvent and Stripe](https://www.stacksync.com/integrations/cvent-and-stripe) - [Cvent and HubSpot](https://www.stacksync.com/integrations/cvent-and-hubspot) - [Cvent and Marketo](https://www.stacksync.com/integrations/cvent-and-marketo) - [Cvent and Eloqua](https://www.stacksync.com/integrations/cvent-and-eloqua) - [Cvent and Zoom](https://www.stacksync.com/integrations/cvent-and-zoom) - [Cvent and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/cvent-and-salesforce-marketing-cloud) - [Cvent and SAP S/4HANA](https://www.stacksync.com/integrations/cvent-and-sap-s4hana) ### CRM · 46 - [Cvent and 6sense](https://www.stacksync.com/integrations/6sense-and-cvent) - [Cvent and Affinity](https://www.stacksync.com/integrations/affinity-and-cvent) - [Cvent and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-cvent) - [Cvent and Attio](https://www.stacksync.com/integrations/attio-and-cvent) - [Cvent and Chorusai](https://www.stacksync.com/integrations/chorusai-and-cvent) - [Cvent and Clari](https://www.stacksync.com/integrations/clari-and-cvent) - [Cvent and Clearbit](https://www.stacksync.com/integrations/clearbit-and-cvent) - [Cvent and Close](https://www.stacksync.com/integrations/close-and-cvent) - [Cvent and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-cvent) - [Cvent and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-cvent) - [Cvent and Crustdata](https://www.stacksync.com/integrations/crustdata-and-cvent) - [Cvent and DealCloud](https://www.stacksync.com/integrations/cvent-and-dealcloud) - [Cvent and Dun & Bradstreet](https://www.stacksync.com/integrations/cvent-and-dun-bradstreet) - [Cvent and Folk CRM](https://www.stacksync.com/integrations/cvent-and-folk-crm) - [Cvent and Freshsales](https://www.stacksync.com/integrations/cvent-and-freshsales) - [Cvent and Freshworks CRM](https://www.stacksync.com/integrations/cvent-and-freshworks-crm) - [Cvent and Gladly](https://www.stacksync.com/integrations/cvent-and-gladly) - [Cvent and Gong](https://www.stacksync.com/integrations/cvent-and-gong) - [Cvent and Gorgias](https://www.stacksync.com/integrations/cvent-and-gorgias) - [Cvent and HubSpot](https://www.stacksync.com/integrations/cvent-and-hubspot) - [Cvent and Infor CRM](https://www.stacksync.com/integrations/cvent-and-infor-crm) - [Cvent and Insightly](https://www.stacksync.com/integrations/cvent-and-insightly) - [Cvent and Intercom](https://www.stacksync.com/integrations/cvent-and-intercom) - [Cvent and Kommo](https://www.stacksync.com/integrations/cvent-and-kommo) - [Cvent and Kustomer](https://www.stacksync.com/integrations/cvent-and-kustomer) - [Cvent and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/cvent-and-microsoft-dynamics-365-sales) - [Cvent and Nimble](https://www.stacksync.com/integrations/cvent-and-nimble) - [Cvent and Nutshell](https://www.stacksync.com/integrations/cvent-and-nutshell) - [Cvent and Oracle CX Sales](https://www.stacksync.com/integrations/cvent-and-oracle-cx-sales) - [Cvent and Outreach](https://www.stacksync.com/integrations/cvent-and-outreach) - [Cvent and Pipedrive](https://www.stacksync.com/integrations/cvent-and-pipedrive) - [Cvent and Salesforce](https://www.stacksync.com/integrations/cvent-and-salesforce) - [Cvent and Salesloft](https://www.stacksync.com/integrations/cvent-and-salesloft) - [Cvent and SAP Sales Cloud](https://www.stacksync.com/integrations/cvent-and-sap-sales-cloud) - [Cvent and Seismic](https://www.stacksync.com/integrations/cvent-and-seismic) - [Cvent and Shopify](https://www.stacksync.com/integrations/cvent-and-shopify) - [Cvent and Streak CRM](https://www.stacksync.com/integrations/cvent-and-streak-crm) - [Cvent and SugarCRM](https://www.stacksync.com/integrations/cvent-and-sugarcrm) - [Cvent and Twenty CRM](https://www.stacksync.com/integrations/cvent-and-twenty-crm) - [Cvent and Veeva CRM](https://www.stacksync.com/integrations/cvent-and-veeva-crm) - [Cvent and Vitally](https://www.stacksync.com/integrations/cvent-and-vitally) - [Cvent and Vtiger CRM](https://www.stacksync.com/integrations/cvent-and-vtiger-crm) - [Cvent and Xactly](https://www.stacksync.com/integrations/cvent-and-xactly) - [Cvent and Zoho CRM](https://www.stacksync.com/integrations/cvent-and-zoho-crm) - [Cvent and Zoho SalesIQ](https://www.stacksync.com/integrations/cvent-and-zoho-salesiq) - [Cvent and ZoomInfo](https://www.stacksync.com/integrations/cvent-and-zoominfo) ### ERP · 38 - [Cvent and Acumatica](https://www.stacksync.com/integrations/acumatica-and-cvent) - [Cvent and Blue Yonder WMS](https://www.stacksync.com/integrations/blue-yonder-wms-and-cvent) - [Cvent and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-cvent) - [Cvent and Cin7](https://www.stacksync.com/integrations/cin7-and-cvent) - [Cvent and DEAR Inventory](https://www.stacksync.com/integrations/cvent-and-dear-inventory) - [Cvent and Dynamics 365 Business Central](https://www.stacksync.com/integrations/cvent-and-microsoft-dynamics-365-business-central) - [Cvent and Dynamics 365 F&O](https://www.stacksync.com/integrations/cvent-and-dynamics-365-finance-operations) - [Cvent and Epicor ERP](https://www.stacksync.com/integrations/cvent-and-epicor-erp) - [Cvent and Extensiv (3PL Central)](https://www.stacksync.com/integrations/cvent-and-extensiv-3pl-central) - [Cvent and Fishbowl Manufacturing](https://www.stacksync.com/integrations/cvent-and-fishbowl-manufacturing) - [Cvent and Infor CloudSuite](https://www.stacksync.com/integrations/cvent-and-infor-cloudsuite) - [Cvent and Infor LN](https://www.stacksync.com/integrations/cvent-and-infor-ln) - [Cvent and Infor M3](https://www.stacksync.com/integrations/cvent-and-infor-m3) - [Cvent and Infor WMS](https://www.stacksync.com/integrations/cvent-and-infor-wms) - [Cvent and Linnworks](https://www.stacksync.com/integrations/cvent-and-linnworks) - [Cvent and Logiwa WMS](https://www.stacksync.com/integrations/cvent-and-logiwa-wms) - [Cvent and Macola ERP](https://www.stacksync.com/integrations/cvent-and-macola-erp) - [Cvent and Manhattan Associates WMS](https://www.stacksync.com/integrations/cvent-and-manhattan-associates-wms) - [Cvent and Microsoft Dynamics GP](https://www.stacksync.com/integrations/cvent-and-microsoft-dynamics-gp) - [Cvent and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/cvent-and-microsoft-dynamics-nav) - [Cvent and NetSuite](https://www.stacksync.com/integrations/cvent-and-netsuite) - [Cvent and Odoo](https://www.stacksync.com/integrations/cvent-and-odoo) - [Cvent and Oracle Fusion ERP](https://www.stacksync.com/integrations/cvent-and-oracle-fusion-erp) - [Cvent and Plex ERP](https://www.stacksync.com/integrations/cvent-and-plex-erp) - [Cvent and QAD ERP](https://www.stacksync.com/integrations/cvent-and-qad-erp) - [Cvent and Rootstock ERP](https://www.stacksync.com/integrations/cvent-and-rootstock-erp) - [Cvent and Sage 100](https://www.stacksync.com/integrations/cvent-and-sage-100) - [Cvent and Sage 300](https://www.stacksync.com/integrations/cvent-and-sage-300) - [Cvent and Sage Intacct](https://www.stacksync.com/integrations/cvent-and-sage-intacct) - [Cvent and Sage X3](https://www.stacksync.com/integrations/cvent-and-sage-x3) - [Cvent and SAP](https://www.stacksync.com/integrations/cvent-and-sap) - [Cvent and SAP Business ByDesign](https://www.stacksync.com/integrations/cvent-and-sap-business-bydesign) - [Cvent and SAP Business One](https://www.stacksync.com/integrations/cvent-and-sap-business-one) - [Cvent and SAP S/4HANA](https://www.stacksync.com/integrations/cvent-and-sap-s4hana) - [Cvent and SuiteAnalytics](https://www.stacksync.com/integrations/cvent-and-suite-analytics) - [Cvent and Syspro](https://www.stacksync.com/integrations/cvent-and-syspro) - [Cvent and TikTok Shop](https://www.stacksync.com/integrations/cvent-and-tiktok) - [Cvent and Unleashed Software](https://www.stacksync.com/integrations/cvent-and-unleashed-software) ### Database · 50 - [Cvent and Airtable](https://www.stacksync.com/integrations/airtable-and-cvent) - [Cvent and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-cvent) - [Cvent and Amazon DynamoDB](https://www.stacksync.com/integrations/cvent-and-dynamo-db) - [Cvent and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-cvent) - [Cvent and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-cvent) - [Cvent and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-cvent) - [Cvent and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-cvent) - [Cvent and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-cvent) - [Cvent and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-cvent) - [Cvent and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-cvent) - [Cvent and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-cvent) - [Cvent and Citus](https://www.stacksync.com/integrations/citus-and-cvent) - [Cvent and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-cvent) - [Cvent and Couchbase](https://www.stacksync.com/integrations/couchbase-and-cvent) - [Cvent and DuckDB](https://www.stacksync.com/integrations/cvent-and-duckdb) - [Cvent and Elasticsearch](https://www.stacksync.com/integrations/cvent-and-elasticsearch) - [Cvent and Firebase](https://www.stacksync.com/integrations/cvent-and-firebase) - [Cvent and Google AlloyDB](https://www.stacksync.com/integrations/cvent-and-google-alloydb) - [Cvent and Google Cloud Spanner](https://www.stacksync.com/integrations/cvent-and-google-cloud-spanner) - [Cvent and Google Cloud SQL](https://www.stacksync.com/integrations/cvent-and-google-cloud-sql) - [Cvent and IBM AS/400](https://www.stacksync.com/integrations/cvent-and-ibm-as400) - [Cvent and IBM Db2](https://www.stacksync.com/integrations/cvent-and-ibm-db2) - [Cvent and IBM Informix](https://www.stacksync.com/integrations/cvent-and-ibm-informix) - [Cvent and InfluxDB](https://www.stacksync.com/integrations/cvent-and-influxdb) - [Cvent and InterSystems IRIS](https://www.stacksync.com/integrations/cvent-and-intersystems-iris) - [Cvent and JDBC](https://www.stacksync.com/integrations/cvent-and-jdbc) - [Cvent and MariaDB](https://www.stacksync.com/integrations/cvent-and-mariadb) - [Cvent and MarkLogic](https://www.stacksync.com/integrations/cvent-and-marklogic) - [Cvent and MongoDB](https://www.stacksync.com/integrations/cvent-and-mongodb) - [Cvent and MySQL](https://www.stacksync.com/integrations/cvent-and-mysql) - [Cvent and Neo4j](https://www.stacksync.com/integrations/cvent-and-neo4j) - [Cvent and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/cvent-and-oci-database) - [Cvent and OpenSearch](https://www.stacksync.com/integrations/cvent-and-opensearch) - [Cvent and Oracle DB](https://www.stacksync.com/integrations/cvent-and-oracle-db) - [Cvent and Postgres Heroku](https://www.stacksync.com/integrations/cvent-and-postgres-heroku) - [Cvent and PostgreSQL](https://www.stacksync.com/integrations/cvent-and-postgresql) - [Cvent and RavenDB](https://www.stacksync.com/integrations/cvent-and-ravendb) - [Cvent and Redis Enterprise](https://www.stacksync.com/integrations/cvent-and-redis-enterprise) - [Cvent and Reltio](https://www.stacksync.com/integrations/cvent-and-reltio) - [Cvent and Render Postgres](https://www.stacksync.com/integrations/cvent-and-render-postgres) - [Cvent and SAP ASE (Sybase)](https://www.stacksync.com/integrations/cvent-and-sap-ase-sybase) - [Cvent and SAP HANA](https://www.stacksync.com/integrations/cvent-and-sap-hana) - [Cvent and Scaleway Postgres](https://www.stacksync.com/integrations/cvent-and-scaleway-postgres) - [Cvent and SingleStore](https://www.stacksync.com/integrations/cvent-and-singlestore) - [Cvent and SQL Server](https://www.stacksync.com/integrations/cvent-and-sql-server) - [Cvent and Supabase](https://www.stacksync.com/integrations/cvent-and-supabase) - [Cvent and TiDB](https://www.stacksync.com/integrations/cvent-and-tidb) - [Cvent and TimescaleDB](https://www.stacksync.com/integrations/cvent-and-timescaledb) - [Cvent and VoltDB](https://www.stacksync.com/integrations/cvent-and-voltdb) - [Cvent and YugabyteDB](https://www.stacksync.com/integrations/cvent-and-yugabytedb) ### Data warehouse · 29 - [Cvent and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-cvent) - [Cvent and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-cvent) - [Cvent and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-cvent) - [Cvent and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-cvent) - [Cvent and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-cvent) - [Cvent and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-cvent) - [Cvent and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-cvent) - [Cvent and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-cvent) - [Cvent and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-cvent) - [Cvent and BigQuery](https://www.stacksync.com/integrations/bigquery-and-cvent) - [Cvent and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-cvent) - [Cvent and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-cvent) - [Cvent and Databricks](https://www.stacksync.com/integrations/cvent-and-databricks) - [Cvent and Dremio](https://www.stacksync.com/integrations/cvent-and-dremio) - [Cvent and Exasol](https://www.stacksync.com/integrations/cvent-and-exasol) - [Cvent and Firebolt](https://www.stacksync.com/integrations/cvent-and-firebolt) - [Cvent and Google Cloud Platform](https://www.stacksync.com/integrations/cvent-and-google-cloud-platform) - [Cvent and Greenplum](https://www.stacksync.com/integrations/cvent-and-greenplum) - [Cvent and IBM Netezza](https://www.stacksync.com/integrations/cvent-and-ibm-netezza) - [Cvent and Materialize](https://www.stacksync.com/integrations/cvent-and-materialize) - [Cvent and MotherDuck](https://www.stacksync.com/integrations/cvent-and-motherduck) - [Cvent and Rockset](https://www.stacksync.com/integrations/cvent-and-rockset) - [Cvent and Snowflake](https://www.stacksync.com/integrations/cvent-and-snowflake) - [Cvent and Starburst Enterprise](https://www.stacksync.com/integrations/cvent-and-starburst-enterprise) - [Cvent and StarRocks](https://www.stacksync.com/integrations/cvent-and-starrocks) - [Cvent and Teradata Vantage](https://www.stacksync.com/integrations/cvent-and-teradata-vantage) - [Cvent and Tinybird](https://www.stacksync.com/integrations/cvent-and-tinybird) - [Cvent and Vertica](https://www.stacksync.com/integrations/cvent-and-vertica) - [Cvent and Yellowbrick](https://www.stacksync.com/integrations/cvent-and-yellowbrick) ### Accounting and finance · 17 - [Cvent and Adyen](https://www.stacksync.com/integrations/adyen-and-cvent) - [Cvent and Anaplan](https://www.stacksync.com/integrations/anaplan-and-cvent) - [Cvent and BILL](https://www.stacksync.com/integrations/bill-and-cvent) - [Cvent and Braintree](https://www.stacksync.com/integrations/braintree-and-cvent) - [Cvent and Chargebee](https://www.stacksync.com/integrations/chargebee-and-cvent) - [Cvent and Coupa](https://www.stacksync.com/integrations/coupa-and-cvent) - [Cvent and Hyperline](https://www.stacksync.com/integrations/cvent-and-hyperline) - [Cvent and LogiSense](https://www.stacksync.com/integrations/cvent-and-logisense) - [Cvent and Navan](https://www.stacksync.com/integrations/cvent-and-navan) - [Cvent and Pigment](https://www.stacksync.com/integrations/cvent-and-pigment) - [Cvent and QuickBooks](https://www.stacksync.com/integrations/cvent-and-quickbooks) - [Cvent and Ramp](https://www.stacksync.com/integrations/cvent-and-ramp) - [Cvent and Recurly](https://www.stacksync.com/integrations/cvent-and-recurly) - [Cvent and Rillet](https://www.stacksync.com/integrations/cvent-and-rillet) - [Cvent and Stripe](https://www.stacksync.com/integrations/cvent-and-stripe) - [Cvent and Workday](https://www.stacksync.com/integrations/cvent-and-workday) - [Cvent and Zuora](https://www.stacksync.com/integrations/cvent-and-zuora) ### AI · 5 - [Cvent and Anthropic](https://www.stacksync.com/integrations/anthropic-and-cvent) - [Cvent and Autopilot](https://www.stacksync.com/integrations/autopilot-and-cvent) - [Cvent and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-cvent) - [Cvent and OpenAI](https://www.stacksync.com/integrations/cvent-and-openai) - [Cvent and Pinecone](https://www.stacksync.com/integrations/cvent-and-pinecone) ### Analytics · 7 - [Cvent and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-cvent) - [Cvent and Microsoft Power BI](https://www.stacksync.com/integrations/cvent-and-microsoft-power-bi) - [Cvent and Mixpanel](https://www.stacksync.com/integrations/cvent-and-mixpanel) - [Cvent and Pendo](https://www.stacksync.com/integrations/cvent-and-pendo) - [Cvent and Splunk](https://www.stacksync.com/integrations/cvent-and-splunk) - [Cvent and Tableau](https://www.stacksync.com/integrations/cvent-and-tableau) - [Cvent and Treasure Data](https://www.stacksync.com/integrations/cvent-and-treasuredata) ### Communications · 6 - [Cvent and Aircall](https://www.stacksync.com/integrations/aircall-and-cvent) - [Cvent and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-cvent) - [Cvent and Gmail](https://www.stacksync.com/integrations/cvent-and-gmail) - [Cvent and Infobip](https://www.stacksync.com/integrations/cvent-and-infobip) - [Cvent and RingCentral](https://www.stacksync.com/integrations/cvent-and-ringcentral) - [Cvent and Zoom](https://www.stacksync.com/integrations/cvent-and-zoom) ### E-commerce · 8 - [Cvent and Akeneo](https://www.stacksync.com/integrations/akeneo-and-cvent) - [Cvent and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-cvent) - [Cvent and ChannelEngine](https://www.stacksync.com/integrations/channelengine-and-cvent) - [Cvent and EasyPost](https://www.stacksync.com/integrations/cvent-and-easypost) - [Cvent and Magento](https://www.stacksync.com/integrations/cvent-and-magento) - [Cvent and NuORDER](https://www.stacksync.com/integrations/cvent-and-nuorder) - [Cvent and Shipwire](https://www.stacksync.com/integrations/cvent-and-shipwire) - [Cvent and Shopware](https://www.stacksync.com/integrations/cvent-and-shopware) ### Marketing · 8 - [Cvent and Bingads](https://www.stacksync.com/integrations/bingads-and-cvent) - [Cvent and Demandbase](https://www.stacksync.com/integrations/cvent-and-demandbase) - [Cvent and Eloqua](https://www.stacksync.com/integrations/cvent-and-eloqua) - [Cvent and Iterable](https://www.stacksync.com/integrations/cvent-and-iterable) - [Cvent and Marketo](https://www.stacksync.com/integrations/cvent-and-marketo) - [Cvent and RollWorks](https://www.stacksync.com/integrations/cvent-and-rollworks) - [Cvent and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/cvent-and-salesforce-marketing-cloud) - [Cvent and Twitter Ads](https://www.stacksync.com/integrations/cvent-and-twitter-ads) 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/)