--- title: "eClinicalWorks connector | Stacksync" description: "eClinicalWorks integration guide: plan Documents, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/eclinicalworks last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # eClinicalWorks 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 eClinicalWorks workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Documents. 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. - **Patients** - **Appointments** - **Encounters** **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=eclinicalworks) ## 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 ## eClinicalWorks records to discuss. These eClinicalWorks record examples help scope a technical review. They are not a list of verified Stacksync operations. Patients Identify this record type and the operation you need to review with Stacksync. Appointments Identify this record type and the operation you need to review with Stacksync. Encounters Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Practitioners Identify this record type and the operation you need to review with Stacksync. Observations Identify this record type and the operation you need to review with Stacksync. Medications Identify this record type and the operation you need to review with Stacksync. Connection setup ## eClinicalWorks connection requirements. Review eClinicalWorks 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 eClinicalWorks account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for eClinicalWorks, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your eClinicalWorks integration. Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks eClinicalWorks **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 file/object ID, container, and version. A path can change and a filename can repeat. Load related records in the right order Resolve folder/container and parent-record references before attaching metadata. ### Mapping checks by record type #### Documents Confirm object support with Stacksync Identity Keep file/object ID, container, and version. A path can change and a filename can repeat. Fields to consider Source file ID · Container reference · Version · Metadata · Access classification Related records to resolve first Resolve folder/container and parent-record references before attaching metadata. Test before going live Test a renamed file, a new version, a moved folder, and an access-restricted document. [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 eClinicalWorks integration in four steps. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### View the four setup tests and expected results 1. ### Confirm the intended eClinicalWorks 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 Documents Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a renamed file, a new version, a moved folder, and an access-restricted document. **Expected result:** An update reaches the intended record, preserves its relationships, and performs each approved side effect once. 3. ### Test the operation your workflow needs Review one eClinicalWorks 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 eClinicalWorks integration. ### Diagnose record matching, delayed changes, and rejected operations A eClinicalWorks record appears under the wrong destination record Keep file/object ID, container, and version. A path can change and a filename can repeat. Resolve folder/container and parent-record references before attaching metadata. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected eClinicalWorks implementation’s change-detection method for Documents. 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 eClinicalWorks 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 eClinicalWorks workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=eclinicalworks) ## eClinicalWorks 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) - [article Bring Patient Records Into Zoho Without Moving What Should Stay](https://www.stacksync.com/blog/sync-zoho-crm-and-eclinicalworks) FAQ ## eClinicalWorks connector FAQ ### How should I plan an integration with eClinicalWorks? Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. 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 eClinicalWorks connector write changes back? Write-back support is not established for this connection. Review the eClinicalWorks records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for eClinicalWorks data? Keep file/object ID, container, and version. A path can change and a filename can repeat. ### Which related records should I load first for eClinicalWorks? Resolve folder/container and parent-record references before attaching metadata. ### How do I validate eClinicalWorks changes after the initial load? Test a renamed file, a new version, a moved folder, and an access-restricted document. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What will we cover in a eClinicalWorks integration demo? Start with one workflow and a sample record from Documents. 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 eClinicalWorks 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 eClinicalWorks and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use eClinicalWorks. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a eClinicalWorks record changes.” - “Create a Genie that answers questions about our eClinicalWorks 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 eClinicalWorks 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 - [eClinicalWorks and Microsoft 365](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-365) - [eClinicalWorks and Zoho CRM](https://www.stacksync.com/integrations/eclinicalworks-and-zoho-crm) - [eClinicalWorks and Stripe](https://www.stacksync.com/integrations/eclinicalworks-and-stripe) - [eClinicalWorks and Salesforce](https://www.stacksync.com/integrations/eclinicalworks-and-salesforce) - [eClinicalWorks and TimescaleDB](https://www.stacksync.com/integrations/eclinicalworks-and-timescaledb) - [eClinicalWorks and QuickBooks](https://www.stacksync.com/integrations/eclinicalworks-and-quickbooks) - [eClinicalWorks and Okta](https://www.stacksync.com/integrations/eclinicalworks-and-okta) - [eClinicalWorks and HubSpot](https://www.stacksync.com/integrations/eclinicalworks-and-hubspot) ### CRM · 19 - [eClinicalWorks and Chorusai](https://www.stacksync.com/integrations/chorusai-and-eclinicalworks) - [eClinicalWorks and Clari](https://www.stacksync.com/integrations/clari-and-eclinicalworks) - [eClinicalWorks and Close](https://www.stacksync.com/integrations/close-and-eclinicalworks) - [eClinicalWorks and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-eclinicalworks) - [eClinicalWorks and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-eclinicalworks) - [eClinicalWorks and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-eclinicalworks) - [eClinicalWorks and Freshsales](https://www.stacksync.com/integrations/eclinicalworks-and-freshsales) - [eClinicalWorks and Gladly](https://www.stacksync.com/integrations/eclinicalworks-and-gladly) - [eClinicalWorks and Gong](https://www.stacksync.com/integrations/eclinicalworks-and-gong) - [eClinicalWorks and Gorgias](https://www.stacksync.com/integrations/eclinicalworks-and-gorgias) - [eClinicalWorks and HubSpot](https://www.stacksync.com/integrations/eclinicalworks-and-hubspot) - [eClinicalWorks and Infor CRM](https://www.stacksync.com/integrations/eclinicalworks-and-infor-crm) - [eClinicalWorks and Intercom](https://www.stacksync.com/integrations/eclinicalworks-and-intercom) - [eClinicalWorks and Kustomer](https://www.stacksync.com/integrations/eclinicalworks-and-kustomer) - [eClinicalWorks and Salesforce](https://www.stacksync.com/integrations/eclinicalworks-and-salesforce) - [eClinicalWorks and Seismic](https://www.stacksync.com/integrations/eclinicalworks-and-seismic) - [eClinicalWorks and Xactly](https://www.stacksync.com/integrations/eclinicalworks-and-xactly) - [eClinicalWorks and Zoho CRM](https://www.stacksync.com/integrations/eclinicalworks-and-zoho-crm) - [eClinicalWorks and Zoho SalesIQ](https://www.stacksync.com/integrations/eclinicalworks-and-zoho-salesiq) ### ERP · 6 - [eClinicalWorks and Deposco](https://www.stacksync.com/integrations/deposco-and-eclinicalworks) - [eClinicalWorks and NetSuite](https://www.stacksync.com/integrations/eclinicalworks-and-netsuite) - [eClinicalWorks and Oracle Fusion ERP](https://www.stacksync.com/integrations/eclinicalworks-and-oracle-fusion-erp) - [eClinicalWorks and SAP](https://www.stacksync.com/integrations/eclinicalworks-and-sap) - [eClinicalWorks and SAP Business ByDesign](https://www.stacksync.com/integrations/eclinicalworks-and-sap-business-bydesign) - [eClinicalWorks and SAP Business One](https://www.stacksync.com/integrations/eclinicalworks-and-sap-business-one) ### Database · 50 - [eClinicalWorks and Airtable](https://www.stacksync.com/integrations/airtable-and-eclinicalworks) - [eClinicalWorks and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-eclinicalworks) - [eClinicalWorks and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-eclinicalworks) - [eClinicalWorks and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-eclinicalworks) - [eClinicalWorks and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-eclinicalworks) - [eClinicalWorks and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-eclinicalworks) - [eClinicalWorks and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-eclinicalworks) - [eClinicalWorks and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-eclinicalworks) - [eClinicalWorks and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-eclinicalworks) - [eClinicalWorks and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-eclinicalworks) - [eClinicalWorks and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-eclinicalworks) - [eClinicalWorks and Citus](https://www.stacksync.com/integrations/citus-and-eclinicalworks) - [eClinicalWorks and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-eclinicalworks) - [eClinicalWorks and Couchbase](https://www.stacksync.com/integrations/couchbase-and-eclinicalworks) - [eClinicalWorks and DuckDB](https://www.stacksync.com/integrations/duckdb-and-eclinicalworks) - [eClinicalWorks and Elasticsearch](https://www.stacksync.com/integrations/eclinicalworks-and-elasticsearch) - [eClinicalWorks and Firebase](https://www.stacksync.com/integrations/eclinicalworks-and-firebase) - [eClinicalWorks and Google AlloyDB](https://www.stacksync.com/integrations/eclinicalworks-and-google-alloydb) - [eClinicalWorks and Google Cloud Spanner](https://www.stacksync.com/integrations/eclinicalworks-and-google-cloud-spanner) - [eClinicalWorks and Google Cloud SQL](https://www.stacksync.com/integrations/eclinicalworks-and-google-cloud-sql) - [eClinicalWorks and IBM AS/400](https://www.stacksync.com/integrations/eclinicalworks-and-ibm-as400) - [eClinicalWorks and IBM Db2](https://www.stacksync.com/integrations/eclinicalworks-and-ibm-db2) - [eClinicalWorks and IBM Informix](https://www.stacksync.com/integrations/eclinicalworks-and-ibm-informix) - [eClinicalWorks and InfluxDB](https://www.stacksync.com/integrations/eclinicalworks-and-influxdb) - [eClinicalWorks and InterSystems IRIS](https://www.stacksync.com/integrations/eclinicalworks-and-intersystems-iris) - [eClinicalWorks and JDBC](https://www.stacksync.com/integrations/eclinicalworks-and-jdbc) - [eClinicalWorks and MariaDB](https://www.stacksync.com/integrations/eclinicalworks-and-mariadb) - [eClinicalWorks and MarkLogic](https://www.stacksync.com/integrations/eclinicalworks-and-marklogic) - [eClinicalWorks and MongoDB](https://www.stacksync.com/integrations/eclinicalworks-and-mongodb) - [eClinicalWorks and MySQL](https://www.stacksync.com/integrations/eclinicalworks-and-mysql) - [eClinicalWorks and Neo4j](https://www.stacksync.com/integrations/eclinicalworks-and-neo4j) - [eClinicalWorks and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/eclinicalworks-and-oci-database) - [eClinicalWorks and OpenSearch](https://www.stacksync.com/integrations/eclinicalworks-and-opensearch) - [eClinicalWorks and Oracle DB](https://www.stacksync.com/integrations/eclinicalworks-and-oracle-db) - [eClinicalWorks and Postgres Heroku](https://www.stacksync.com/integrations/eclinicalworks-and-postgres-heroku) - [eClinicalWorks and PostgreSQL](https://www.stacksync.com/integrations/eclinicalworks-and-postgresql) - [eClinicalWorks and RavenDB](https://www.stacksync.com/integrations/eclinicalworks-and-ravendb) - [eClinicalWorks and Redis Enterprise](https://www.stacksync.com/integrations/eclinicalworks-and-redis-enterprise) - [eClinicalWorks and Reltio](https://www.stacksync.com/integrations/eclinicalworks-and-reltio) - [eClinicalWorks and Render Postgres](https://www.stacksync.com/integrations/eclinicalworks-and-render-postgres) - [eClinicalWorks and SAP ASE (Sybase)](https://www.stacksync.com/integrations/eclinicalworks-and-sap-ase-sybase) - [eClinicalWorks and SAP HANA](https://www.stacksync.com/integrations/eclinicalworks-and-sap-hana) - [eClinicalWorks and Scaleway Postgres](https://www.stacksync.com/integrations/eclinicalworks-and-scaleway-postgres) - [eClinicalWorks and SingleStore](https://www.stacksync.com/integrations/eclinicalworks-and-singlestore) - [eClinicalWorks and SQL Server](https://www.stacksync.com/integrations/eclinicalworks-and-sql-server) - [eClinicalWorks and Supabase](https://www.stacksync.com/integrations/eclinicalworks-and-supabase) - [eClinicalWorks and TiDB](https://www.stacksync.com/integrations/eclinicalworks-and-tidb) - [eClinicalWorks and TimescaleDB](https://www.stacksync.com/integrations/eclinicalworks-and-timescaledb) - [eClinicalWorks and VoltDB](https://www.stacksync.com/integrations/eclinicalworks-and-voltdb) - [eClinicalWorks and YugabyteDB](https://www.stacksync.com/integrations/eclinicalworks-and-yugabytedb) ### Data warehouse · 29 - [eClinicalWorks and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-eclinicalworks) - [eClinicalWorks and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-eclinicalworks) - [eClinicalWorks and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-eclinicalworks) - [eClinicalWorks and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-eclinicalworks) - [eClinicalWorks and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-eclinicalworks) - [eClinicalWorks and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-eclinicalworks) - [eClinicalWorks and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-eclinicalworks) - [eClinicalWorks and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-eclinicalworks) - [eClinicalWorks and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-eclinicalworks) - [eClinicalWorks and BigQuery](https://www.stacksync.com/integrations/bigquery-and-eclinicalworks) - [eClinicalWorks and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-eclinicalworks) - [eClinicalWorks and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-eclinicalworks) - [eClinicalWorks and Databricks](https://www.stacksync.com/integrations/databricks-and-eclinicalworks) - [eClinicalWorks and Dremio](https://www.stacksync.com/integrations/dremio-and-eclinicalworks) - [eClinicalWorks and Exasol](https://www.stacksync.com/integrations/eclinicalworks-and-exasol) - [eClinicalWorks and Firebolt](https://www.stacksync.com/integrations/eclinicalworks-and-firebolt) - [eClinicalWorks and Google Cloud Platform](https://www.stacksync.com/integrations/eclinicalworks-and-google-cloud-platform) - [eClinicalWorks and Greenplum](https://www.stacksync.com/integrations/eclinicalworks-and-greenplum) - [eClinicalWorks and IBM Netezza](https://www.stacksync.com/integrations/eclinicalworks-and-ibm-netezza) - [eClinicalWorks and Materialize](https://www.stacksync.com/integrations/eclinicalworks-and-materialize) - [eClinicalWorks and MotherDuck](https://www.stacksync.com/integrations/eclinicalworks-and-motherduck) - [eClinicalWorks and Rockset](https://www.stacksync.com/integrations/eclinicalworks-and-rockset) - [eClinicalWorks and Snowflake](https://www.stacksync.com/integrations/eclinicalworks-and-snowflake) - [eClinicalWorks and Starburst Enterprise](https://www.stacksync.com/integrations/eclinicalworks-and-starburst-enterprise) - [eClinicalWorks and StarRocks](https://www.stacksync.com/integrations/eclinicalworks-and-starrocks) - [eClinicalWorks and Teradata Vantage](https://www.stacksync.com/integrations/eclinicalworks-and-teradata-vantage) - [eClinicalWorks and Tinybird](https://www.stacksync.com/integrations/eclinicalworks-and-tinybird) - [eClinicalWorks and Vertica](https://www.stacksync.com/integrations/eclinicalworks-and-vertica) - [eClinicalWorks and Yellowbrick](https://www.stacksync.com/integrations/eclinicalworks-and-yellowbrick) ### Business productivity · 28 - [eClinicalWorks and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-eclinicalworks) - [eClinicalWorks and Agiloft](https://www.stacksync.com/integrations/agiloft-and-eclinicalworks) - [eClinicalWorks and Asana](https://www.stacksync.com/integrations/asana-and-eclinicalworks) - [eClinicalWorks and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-eclinicalworks) - [eClinicalWorks and Docusign](https://www.stacksync.com/integrations/docusign-and-eclinicalworks) - [eClinicalWorks and Front](https://www.stacksync.com/integrations/eclinicalworks-and-front) - [eClinicalWorks and Gainsight](https://www.stacksync.com/integrations/eclinicalworks-and-gainsight) - [eClinicalWorks and Gatekeeper](https://www.stacksync.com/integrations/eclinicalworks-and-gatekeeper) - [eClinicalWorks and GitHub](https://www.stacksync.com/integrations/eclinicalworks-and-github) - [eClinicalWorks and Google Sheets](https://www.stacksync.com/integrations/eclinicalworks-and-google-sheets) - [eClinicalWorks and Ironclad](https://www.stacksync.com/integrations/eclinicalworks-and-ironclad) - [eClinicalWorks and Lemlist](https://www.stacksync.com/integrations/eclinicalworks-and-lemlist) - [eClinicalWorks and Microsoft 365](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-365) - [eClinicalWorks and Microsoft Teams](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-teams) - [eClinicalWorks and Monday](https://www.stacksync.com/integrations/eclinicalworks-and-monday) - [eClinicalWorks and NextGen Healthcare](https://www.stacksync.com/integrations/eclinicalworks-and-nextgen-healthcare) - [eClinicalWorks and Notion](https://www.stacksync.com/integrations/eclinicalworks-and-notion) - [eClinicalWorks and Orderful](https://www.stacksync.com/integrations/eclinicalworks-and-orderful) - [eClinicalWorks and Quip](https://www.stacksync.com/integrations/eclinicalworks-and-quip) - [eClinicalWorks and SendGrid](https://www.stacksync.com/integrations/eclinicalworks-and-sendgrid) - [eClinicalWorks and ServiceMax](https://www.stacksync.com/integrations/eclinicalworks-and-servicemax) - [eClinicalWorks and ServiceNow](https://www.stacksync.com/integrations/eclinicalworks-and-servicenow) - [eClinicalWorks and Slack](https://www.stacksync.com/integrations/eclinicalworks-and-slack) - [eClinicalWorks and Smartsheet](https://www.stacksync.com/integrations/eclinicalworks-and-smartsheet) - [eClinicalWorks and SysAid](https://www.stacksync.com/integrations/eclinicalworks-and-sysaid) - [eClinicalWorks and Twilio](https://www.stacksync.com/integrations/eclinicalworks-and-twilio) - [eClinicalWorks and Wrike](https://www.stacksync.com/integrations/eclinicalworks-and-wrike) - [eClinicalWorks and Zendesk](https://www.stacksync.com/integrations/eclinicalworks-and-zendesk) ### Accounting and finance · 16 - [eClinicalWorks and Adyen](https://www.stacksync.com/integrations/adyen-and-eclinicalworks) - [eClinicalWorks and BILL](https://www.stacksync.com/integrations/bill-and-eclinicalworks) - [eClinicalWorks and Braintree](https://www.stacksync.com/integrations/braintree-and-eclinicalworks) - [eClinicalWorks and Chargebee](https://www.stacksync.com/integrations/chargebee-and-eclinicalworks) - [eClinicalWorks and Coupa](https://www.stacksync.com/integrations/coupa-and-eclinicalworks) - [eClinicalWorks and Hyperline](https://www.stacksync.com/integrations/eclinicalworks-and-hyperline) - [eClinicalWorks and LogiSense](https://www.stacksync.com/integrations/eclinicalworks-and-logisense) - [eClinicalWorks and Navan](https://www.stacksync.com/integrations/eclinicalworks-and-navan) - [eClinicalWorks and Pigment](https://www.stacksync.com/integrations/eclinicalworks-and-pigment) - [eClinicalWorks and QuickBooks](https://www.stacksync.com/integrations/eclinicalworks-and-quickbooks) - [eClinicalWorks and Ramp](https://www.stacksync.com/integrations/eclinicalworks-and-ramp) - [eClinicalWorks and Recurly](https://www.stacksync.com/integrations/eclinicalworks-and-recurly) - [eClinicalWorks and Rillet](https://www.stacksync.com/integrations/eclinicalworks-and-rillet) - [eClinicalWorks and Stripe](https://www.stacksync.com/integrations/eclinicalworks-and-stripe) - [eClinicalWorks and Workday](https://www.stacksync.com/integrations/eclinicalworks-and-workday) - [eClinicalWorks and Zuora](https://www.stacksync.com/integrations/eclinicalworks-and-zuora) ### AI · 5 - [eClinicalWorks and Anthropic](https://www.stacksync.com/integrations/anthropic-and-eclinicalworks) - [eClinicalWorks and Autopilot](https://www.stacksync.com/integrations/autopilot-and-eclinicalworks) - [eClinicalWorks and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-eclinicalworks) - [eClinicalWorks and OpenAI](https://www.stacksync.com/integrations/eclinicalworks-and-openai) - [eClinicalWorks and Pinecone](https://www.stacksync.com/integrations/eclinicalworks-and-pinecone) ### Developer tools · 11 - [eClinicalWorks and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-eclinicalworks) - [eClinicalWorks and Datadog](https://www.stacksync.com/integrations/datadog-and-eclinicalworks) - [eClinicalWorks and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/eclinicalworks-and-google-pubsub) - [eClinicalWorks and Jira](https://www.stacksync.com/integrations/eclinicalworks-and-jira) - [eClinicalWorks and JMS](https://www.stacksync.com/integrations/eclinicalworks-and-jms) - [eClinicalWorks and LDAP](https://www.stacksync.com/integrations/eclinicalworks-and-ldap) - [eClinicalWorks and Microsoft Graph](https://www.stacksync.com/integrations/eclinicalworks-and-microsoft-graph) - [eClinicalWorks and New Relic](https://www.stacksync.com/integrations/eclinicalworks-and-newrelic) - [eClinicalWorks and Opsgenie](https://www.stacksync.com/integrations/eclinicalworks-and-opsgenie) - [eClinicalWorks and PagerDuty](https://www.stacksync.com/integrations/eclinicalworks-and-pagerduty) - [eClinicalWorks and RabbitMQ](https://www.stacksync.com/integrations/eclinicalworks-and-rabbitmq) ### Human resources · 13 - [eClinicalWorks and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-eclinicalworks) - [eClinicalWorks and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-eclinicalworks) - [eClinicalWorks and Greenhouse](https://www.stacksync.com/integrations/eclinicalworks-and-greenhouse) - [eClinicalWorks and Hibob](https://www.stacksync.com/integrations/eclinicalworks-and-hibob) - [eClinicalWorks and Jobvite](https://www.stacksync.com/integrations/eclinicalworks-and-jobvite) - [eClinicalWorks and Lever](https://www.stacksync.com/integrations/eclinicalworks-and-lever) - [eClinicalWorks and Namely](https://www.stacksync.com/integrations/eclinicalworks-and-namely) - [eClinicalWorks and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/eclinicalworks-and-oracle-fusion-cloud-hcm) - [eClinicalWorks and Paylocity](https://www.stacksync.com/integrations/eclinicalworks-and-paylocity) - [eClinicalWorks and SmartRecruiters](https://www.stacksync.com/integrations/eclinicalworks-and-smartrecruiters) - [eClinicalWorks and Success Factors](https://www.stacksync.com/integrations/eclinicalworks-and-success-factors) - [eClinicalWorks and UKG Pro](https://www.stacksync.com/integrations/eclinicalworks-and-ukg-pro) - [eClinicalWorks and UKG Ready](https://www.stacksync.com/integrations/eclinicalworks-and-ukg-ready) ### Security and identity · 6 - [eClinicalWorks and Active Directory](https://www.stacksync.com/integrations/active-directory-and-eclinicalworks) - [eClinicalWorks and Auth0](https://www.stacksync.com/integrations/auth0-and-eclinicalworks) - [eClinicalWorks and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-eclinicalworks) - [eClinicalWorks and JumpCloud](https://www.stacksync.com/integrations/eclinicalworks-and-jumpcloud) - [eClinicalWorks and Okta](https://www.stacksync.com/integrations/eclinicalworks-and-okta) - [eClinicalWorks and OneLogin](https://www.stacksync.com/integrations/eclinicalworks-and-onelogin) ### Storage · 4 - [eClinicalWorks and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-eclinicalworks) - [eClinicalWorks and Box](https://www.stacksync.com/integrations/box-and-eclinicalworks) - [eClinicalWorks and Egnyte](https://www.stacksync.com/integrations/eclinicalworks-and-egnyte) - [eClinicalWorks and SharePoint](https://www.stacksync.com/integrations/eclinicalworks-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/)