--- title: "VoltDB connector: setup and compatibility | Stacksync" description: "VoltDB integration planning: Partitioned Tables, Replicated Tables and Stored Procedures. Compatibility, identity, dependencies, and validation." canonical: https://www.stacksync.com/connectors/voltdb last_modified: 2026-09-15 --- Database · Two-way sync platform # VoltDB 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 VoltDB workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Partitioned Tables, Replicated Tables and Stored Procedures. 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. - **Partitioned Tables** - **Replicated Tables** - **Stored Procedures** **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=voltdb) ## 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 ## VoltDB records to discuss. These VoltDB record examples help scope a technical review. They are not a list of verified Stacksync operations. Partitioned Tables Identify this record type and the operation you need to review with Stacksync. Replicated Tables Identify this record type and the operation you need to review with Stacksync. Stored Procedures Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Materialized Views Identify this record type and the operation you need to review with Stacksync. Streams Identify this record type and the operation you need to review with Stacksync. Export Targets and Topics Identify this record type and the operation you need to review with Stacksync. Connection setup ## VoltDB connection requirements. Review VoltDB 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 VoltDB account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for VoltDB, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your VoltDB 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 VoltDB **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 #### Partitioned Tables, Replicated Tables and Stored Procedures 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 VoltDB 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 VoltDB 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 Partitioned Tables, Replicated Tables and Stored Procedures 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 VoltDB 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 VoltDB integration. ### Diagnose record matching, delayed changes, and rejected operations A VoltDB 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 VoltDB implementation’s change-detection method for Partitioned Tables, Replicated Tables and Stored Procedures. 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 VoltDB 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 VoltDB workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=voltdb) ## VoltDB 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 ## VoltDB connector FAQ ### How should I plan an integration with VoltDB? 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 VoltDB connector write changes back? Write-back support is not established for this connection. Review the VoltDB records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for VoltDB 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 VoltDB? 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 VoltDB 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 VoltDB integration demo? Start with one workflow and a sample record from Partitioned Tables, Replicated Tables and Stored Procedures. 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 VoltDB 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 VoltDB and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use VoltDB. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a VoltDB record changes.” - “Create a Genie that answers questions about our VoltDB 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 VoltDB 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 - [Rockset and VoltDB](https://www.stacksync.com/integrations/rockset-and-voltdb) - [Twenty CRM and VoltDB](https://www.stacksync.com/integrations/twenty-crm-and-voltdb) - [Okta and VoltDB](https://www.stacksync.com/integrations/okta-and-voltdb) - [SugarCRM and VoltDB](https://www.stacksync.com/integrations/sugarcrm-and-voltdb) - [Sage X3 and VoltDB](https://www.stacksync.com/integrations/sage-x3-and-voltdb) - [InfluxDB and VoltDB](https://www.stacksync.com/integrations/influxdb-and-voltdb) - [Elasticsearch and VoltDB](https://www.stacksync.com/integrations/elasticsearch-and-voltdb) - [GitHub and VoltDB](https://www.stacksync.com/integrations/github-and-voltdb) ### CRM · 32 - [VoltDB and 6sense](https://www.stacksync.com/integrations/6sense-and-voltdb) - [VoltDB and Affinity](https://www.stacksync.com/integrations/affinity-and-voltdb) - [VoltDB and Attio](https://www.stacksync.com/integrations/attio-and-voltdb) - [VoltDB and Chorusai](https://www.stacksync.com/integrations/chorusai-and-voltdb) - [VoltDB and Close](https://www.stacksync.com/integrations/close-and-voltdb) - [VoltDB and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-voltdb) - [VoltDB and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-voltdb) - [VoltDB and Freshsales](https://www.stacksync.com/integrations/freshsales-and-voltdb) - [VoltDB and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-voltdb) - [VoltDB and Gong](https://www.stacksync.com/integrations/gong-and-voltdb) - [VoltDB and Gorgias](https://www.stacksync.com/integrations/gorgias-and-voltdb) - [VoltDB and HubSpot](https://www.stacksync.com/integrations/hubspot-and-voltdb) - [VoltDB and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-voltdb) - [VoltDB and Insightly](https://www.stacksync.com/integrations/insightly-and-voltdb) - [VoltDB and Intercom](https://www.stacksync.com/integrations/intercom-and-voltdb) - [VoltDB and Kommo](https://www.stacksync.com/integrations/kommo-and-voltdb) - [VoltDB and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/microsoft-dynamics-365-sales-and-voltdb) - [VoltDB and Outreach](https://www.stacksync.com/integrations/outreach-and-voltdb) - [VoltDB and Pipedrive](https://www.stacksync.com/integrations/pipedrive-and-voltdb) - [VoltDB and Salesforce](https://www.stacksync.com/integrations/salesforce-and-voltdb) - [VoltDB and Salesloft](https://www.stacksync.com/integrations/salesloft-and-voltdb) - [VoltDB and SAP Sales Cloud](https://www.stacksync.com/integrations/sap-sales-cloud-and-voltdb) - [VoltDB and Seismic](https://www.stacksync.com/integrations/seismic-and-voltdb) - [VoltDB and Shopify](https://www.stacksync.com/integrations/shopify-and-voltdb) - [VoltDB and SugarCRM](https://www.stacksync.com/integrations/sugarcrm-and-voltdb) - [VoltDB and Twenty CRM](https://www.stacksync.com/integrations/twenty-crm-and-voltdb) - [VoltDB and Veeva CRM](https://www.stacksync.com/integrations/veeva-crm-and-voltdb) - [VoltDB and Vtiger CRM](https://www.stacksync.com/integrations/voltdb-and-vtiger-crm) - [VoltDB and Xactly](https://www.stacksync.com/integrations/voltdb-and-xactly) - [VoltDB and Zoho CRM](https://www.stacksync.com/integrations/voltdb-and-zoho-crm) - [VoltDB and Zoho SalesIQ](https://www.stacksync.com/integrations/voltdb-and-zoho-salesiq) - [VoltDB and ZoomInfo](https://www.stacksync.com/integrations/voltdb-and-zoominfo) ### ERP · 27 - [VoltDB and Acumatica](https://www.stacksync.com/integrations/acumatica-and-voltdb) - [VoltDB and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-voltdb) - [VoltDB and Cin7](https://www.stacksync.com/integrations/cin7-and-voltdb) - [VoltDB and Deposco](https://www.stacksync.com/integrations/deposco-and-voltdb) - [VoltDB and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-voltdb) - [VoltDB and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-voltdb) - [VoltDB and Fishbowl Manufacturing](https://www.stacksync.com/integrations/fishbowl-manufacturing-and-voltdb) - [VoltDB and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-voltdb) - [VoltDB and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-voltdb) - [VoltDB and Linnworks](https://www.stacksync.com/integrations/linnworks-and-voltdb) - [VoltDB and Macola ERP](https://www.stacksync.com/integrations/macola-erp-and-voltdb) - [VoltDB and Microsoft Dynamics GP](https://www.stacksync.com/integrations/microsoft-dynamics-gp-and-voltdb) - [VoltDB and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/microsoft-dynamics-nav-and-voltdb) - [VoltDB and NetSuite](https://www.stacksync.com/integrations/netsuite-and-voltdb) - [VoltDB and Odoo](https://www.stacksync.com/integrations/odoo-and-voltdb) - [VoltDB and Plex ERP](https://www.stacksync.com/integrations/plex-erp-and-voltdb) - [VoltDB and QAD ERP](https://www.stacksync.com/integrations/qad-erp-and-voltdb) - [VoltDB and Sage 100](https://www.stacksync.com/integrations/sage-100-and-voltdb) - [VoltDB and Sage 300](https://www.stacksync.com/integrations/sage-300-and-voltdb) - [VoltDB and Sage Intacct](https://www.stacksync.com/integrations/sage-intacct-and-voltdb) - [VoltDB and Sage X3](https://www.stacksync.com/integrations/sage-x3-and-voltdb) - [VoltDB and SAP](https://www.stacksync.com/integrations/sap-and-voltdb) - [VoltDB and SAP Business ByDesign](https://www.stacksync.com/integrations/sap-business-bydesign-and-voltdb) - [VoltDB and SAP Business One](https://www.stacksync.com/integrations/sap-business-one-and-voltdb) - [VoltDB and SAP S/4HANA](https://www.stacksync.com/integrations/sap-s4hana-and-voltdb) - [VoltDB and Syspro](https://www.stacksync.com/integrations/syspro-and-voltdb) - [VoltDB and TikTok Shop](https://www.stacksync.com/integrations/tiktok-and-voltdb) ### Database · 21 - [VoltDB and Airtable](https://www.stacksync.com/integrations/airtable-and-voltdb) - [VoltDB and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-voltdb) - [VoltDB and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-voltdb) - [VoltDB and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-voltdb) - [VoltDB and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-voltdb) - [VoltDB and Citus](https://www.stacksync.com/integrations/citus-and-voltdb) - [VoltDB and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-voltdb) - [VoltDB and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-voltdb) - [VoltDB and Firebase](https://www.stacksync.com/integrations/firebase-and-voltdb) - [VoltDB and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-voltdb) - [VoltDB and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-voltdb) - [VoltDB and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-voltdb) - [VoltDB and MongoDB](https://www.stacksync.com/integrations/mongodb-and-voltdb) - [VoltDB and MySQL](https://www.stacksync.com/integrations/mysql-and-voltdb) - [VoltDB and Neo4j](https://www.stacksync.com/integrations/neo4j-and-voltdb) - [VoltDB and PostgreSQL](https://www.stacksync.com/integrations/postgresql-and-voltdb) - [VoltDB and Redis Enterprise](https://www.stacksync.com/integrations/redis-enterprise-and-voltdb) - [VoltDB and SAP HANA](https://www.stacksync.com/integrations/sap-hana-and-voltdb) - [VoltDB and SingleStore](https://www.stacksync.com/integrations/singlestore-and-voltdb) - [VoltDB and SQL Server](https://www.stacksync.com/integrations/sql-server-and-voltdb) - [VoltDB and Supabase](https://www.stacksync.com/integrations/supabase-and-voltdb) ### Data warehouse · 13 - [VoltDB and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-voltdb) - [VoltDB and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-voltdb) - [VoltDB and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-voltdb) - [VoltDB and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-voltdb) - [VoltDB and BigQuery](https://www.stacksync.com/integrations/bigquery-and-voltdb) - [VoltDB and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-voltdb) - [VoltDB and Databricks](https://www.stacksync.com/integrations/databricks-and-voltdb) - [VoltDB and Firebolt](https://www.stacksync.com/integrations/firebolt-and-voltdb) - [VoltDB and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-voltdb) - [VoltDB and Greenplum](https://www.stacksync.com/integrations/greenplum-and-voltdb) - [VoltDB and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-voltdb) - [VoltDB and Rockset](https://www.stacksync.com/integrations/rockset-and-voltdb) - [VoltDB and Snowflake](https://www.stacksync.com/integrations/snowflake-and-voltdb) ### Business productivity · 28 - [VoltDB and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-voltdb) - [VoltDB and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-voltdb) - [VoltDB and Asana](https://www.stacksync.com/integrations/asana-and-voltdb) - [VoltDB and Atlassian](https://www.stacksync.com/integrations/atlassian-and-voltdb) - [VoltDB and Braze](https://www.stacksync.com/integrations/braze-and-voltdb) - [VoltDB and Campfire](https://www.stacksync.com/integrations/campfire-and-voltdb) - [VoltDB and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-voltdb) - [VoltDB and Docusign](https://www.stacksync.com/integrations/docusign-and-voltdb) - [VoltDB and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-voltdb) - [VoltDB and Front](https://www.stacksync.com/integrations/front-and-voltdb) - [VoltDB and Gainsight](https://www.stacksync.com/integrations/gainsight-and-voltdb) - [VoltDB and GitHub](https://www.stacksync.com/integrations/github-and-voltdb) - [VoltDB and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-voltdb) - [VoltDB and Ironclad](https://www.stacksync.com/integrations/ironclad-and-voltdb) - [VoltDB and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-voltdb) - [VoltDB and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-voltdb) - [VoltDB and Monday](https://www.stacksync.com/integrations/monday-and-voltdb) - [VoltDB and Notion](https://www.stacksync.com/integrations/notion-and-voltdb) - [VoltDB and Quip](https://www.stacksync.com/integrations/quip-and-voltdb) - [VoltDB and SendGrid](https://www.stacksync.com/integrations/sendgrid-and-voltdb) - [VoltDB and ServiceMax](https://www.stacksync.com/integrations/servicemax-and-voltdb) - [VoltDB and ServiceNow](https://www.stacksync.com/integrations/servicenow-and-voltdb) - [VoltDB and Slack](https://www.stacksync.com/integrations/slack-and-voltdb) - [VoltDB and Smartsheet](https://www.stacksync.com/integrations/smartsheet-and-voltdb) - [VoltDB and SysAid](https://www.stacksync.com/integrations/sysaid-and-voltdb) - [VoltDB and Twilio](https://www.stacksync.com/integrations/twilio-and-voltdb) - [VoltDB and Wrike](https://www.stacksync.com/integrations/voltdb-and-wrike) - [VoltDB and Zendesk](https://www.stacksync.com/integrations/voltdb-and-zendesk) ### Accounting and finance · 12 - [VoltDB and Adyen](https://www.stacksync.com/integrations/adyen-and-voltdb) - [VoltDB and BILL](https://www.stacksync.com/integrations/bill-and-voltdb) - [VoltDB and Braintree](https://www.stacksync.com/integrations/braintree-and-voltdb) - [VoltDB and Chargebee](https://www.stacksync.com/integrations/chargebee-and-voltdb) - [VoltDB and Coupa](https://www.stacksync.com/integrations/coupa-and-voltdb) - [VoltDB and Navan](https://www.stacksync.com/integrations/navan-and-voltdb) - [VoltDB and QuickBooks](https://www.stacksync.com/integrations/quickbooks-and-voltdb) - [VoltDB and Ramp](https://www.stacksync.com/integrations/ramp-and-voltdb) - [VoltDB and Recurly](https://www.stacksync.com/integrations/recurly-and-voltdb) - [VoltDB and Stripe](https://www.stacksync.com/integrations/stripe-and-voltdb) - [VoltDB and Workday](https://www.stacksync.com/integrations/voltdb-and-workday) - [VoltDB and Zuora](https://www.stacksync.com/integrations/voltdb-and-zuora) ### AI · 4 - [VoltDB and Autopilot](https://www.stacksync.com/integrations/autopilot-and-voltdb) - [VoltDB and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-voltdb) - [VoltDB and OpenAI](https://www.stacksync.com/integrations/openai-and-voltdb) - [VoltDB and Pinecone](https://www.stacksync.com/integrations/pinecone-and-voltdb) ### Analytics · 6 - [VoltDB and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-voltdb) - [VoltDB and Microsoft Power BI](https://www.stacksync.com/integrations/microsoft-power-bi-and-voltdb) - [VoltDB and Mixpanel](https://www.stacksync.com/integrations/mixpanel-and-voltdb) - [VoltDB and Pendo](https://www.stacksync.com/integrations/pendo-and-voltdb) - [VoltDB and Splunk](https://www.stacksync.com/integrations/splunk-and-voltdb) - [VoltDB and Tableau](https://www.stacksync.com/integrations/tableau-and-voltdb) ### Communications · 5 - [VoltDB and Aircall](https://www.stacksync.com/integrations/aircall-and-voltdb) - [VoltDB and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-voltdb) - [VoltDB and Infobip](https://www.stacksync.com/integrations/infobip-and-voltdb) - [VoltDB and RingCentral](https://www.stacksync.com/integrations/ringcentral-and-voltdb) - [VoltDB and Zoom](https://www.stacksync.com/integrations/voltdb-and-zoom) ### Developer tools · 9 - [VoltDB and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-voltdb) - [VoltDB and Datadog](https://www.stacksync.com/integrations/datadog-and-voltdb) - [VoltDB and Jira](https://www.stacksync.com/integrations/jira-and-voltdb) - [VoltDB and JMS](https://www.stacksync.com/integrations/jms-and-voltdb) - [VoltDB and LDAP](https://www.stacksync.com/integrations/ldap-and-voltdb) - [VoltDB and New Relic](https://www.stacksync.com/integrations/newrelic-and-voltdb) - [VoltDB and Opsgenie](https://www.stacksync.com/integrations/opsgenie-and-voltdb) - [VoltDB and PagerDuty](https://www.stacksync.com/integrations/pagerduty-and-voltdb) - [VoltDB and RabbitMQ](https://www.stacksync.com/integrations/rabbitmq-and-voltdb) ### E-commerce · 6 - [VoltDB and Akeneo](https://www.stacksync.com/integrations/akeneo-and-voltdb) - [VoltDB and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-voltdb) - [VoltDB and EasyPost](https://www.stacksync.com/integrations/easypost-and-voltdb) - [VoltDB and Magento](https://www.stacksync.com/integrations/magento-and-voltdb) - [VoltDB and Shipwire](https://www.stacksync.com/integrations/shipwire-and-voltdb) - [VoltDB and Shopware](https://www.stacksync.com/integrations/shopware-and-voltdb) ### Human resources · 12 - [VoltDB and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-voltdb) - [VoltDB and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-voltdb) - [VoltDB and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-voltdb) - [VoltDB and Hibob](https://www.stacksync.com/integrations/hibob-and-voltdb) - [VoltDB and Jobvite](https://www.stacksync.com/integrations/jobvite-and-voltdb) - [VoltDB and Lever](https://www.stacksync.com/integrations/lever-and-voltdb) - [VoltDB and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-voltdb) - [VoltDB and Paylocity](https://www.stacksync.com/integrations/paylocity-and-voltdb) - [VoltDB and SmartRecruiters](https://www.stacksync.com/integrations/smartrecruiters-and-voltdb) - [VoltDB and Success Factors](https://www.stacksync.com/integrations/success-factors-and-voltdb) - [VoltDB and UKG Pro](https://www.stacksync.com/integrations/ukg-pro-and-voltdb) - [VoltDB and UKG Ready](https://www.stacksync.com/integrations/ukg-ready-and-voltdb) ### Marketing · 8 - [VoltDB and Bingads](https://www.stacksync.com/integrations/bingads-and-voltdb) - [VoltDB and Cvent](https://www.stacksync.com/integrations/cvent-and-voltdb) - [VoltDB and Demandbase](https://www.stacksync.com/integrations/demandbase-and-voltdb) - [VoltDB and Eloqua](https://www.stacksync.com/integrations/eloqua-and-voltdb) - [VoltDB and Iterable](https://www.stacksync.com/integrations/iterable-and-voltdb) - [VoltDB and Marketo](https://www.stacksync.com/integrations/marketo-and-voltdb) - [VoltDB and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/salesforce-marketing-cloud-and-voltdb) - [VoltDB and Twitter Ads](https://www.stacksync.com/integrations/twitter-ads-and-voltdb) ### Security and identity · 6 - [VoltDB and Active Directory](https://www.stacksync.com/integrations/active-directory-and-voltdb) - [VoltDB and Auth0](https://www.stacksync.com/integrations/auth0-and-voltdb) - [VoltDB and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-voltdb) - [VoltDB and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-voltdb) - [VoltDB and Okta](https://www.stacksync.com/integrations/okta-and-voltdb) - [VoltDB and OneLogin](https://www.stacksync.com/integrations/onelogin-and-voltdb) ### Storage · 4 - [VoltDB and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-voltdb) - [VoltDB and Box](https://www.stacksync.com/integrations/box-and-voltdb) - [VoltDB and Egnyte](https://www.stacksync.com/integrations/egnyte-and-voltdb) - [VoltDB and SharePoint](https://www.stacksync.com/integrations/sharepoint-and-voltdb) 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/)