Skip to content
Database ⇄ Accounting and finance

Azure Cosmos DB to Workday integration — real-time, two-way sync

Keep Azure Cosmos DB and Workday in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure Cosmos DB and Workday

Work with Workday's financial data straight from Azure Cosmos DB: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Time Off and Absence, Payroll Results, Suppliers, Customers and Invoices from Workday into Containers, Items (JSON documents), Partition keys, Change feed entries in Azure Cosmos DB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Azure Cosmos DB, and rows your code writes or updates flow back into Workday with validation, so the finance system stays the system of record.

Common use cases

  • 01 Push completed payroll results into a finance system or data warehouse each pay cycle.
  • 02 Import journal entries from external billing or expense systems into Workday Financials.
  • 03 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 04 Consolidate documents from multiple containers into a single reporting store.

Common sync patterns

Write back safely

Updates written to the synced tables in Azure Cosmos DB propagate into Workday, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Workday appear in Azure Cosmos DB as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Workday live in Azure Cosmos DB as regular tables or collections your team can join, index, and query.

What you can sync between Azure Cosmos DB and Workday

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Azure Cosmos DB objects Workday objects How this pairing syncs
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. Partition keys is specific to Azure Cosmos DB and Customers and Invoices to Workday — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Journal Entries Accounting entries imported from external subledgers into Workday Financials. Change feed entries is specific to Azure Cosmos DB and Journal Entries to Workday — each maps to any object or custom field on the other side.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Custom Reports (RaaS) Tenant-defined reports exposed as web service endpoints, often the practical read surface for syncs. Stored procedures and triggers is specific to Azure Cosmos DB and Custom Reports (RaaS) to Workday — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Workers The central HCM record covering employment, job, and personal data; the anchor of most syncs. Databases is specific to Azure Cosmos DB and Workers to Workday — each maps to any object or custom field on the other side.
Containers The unit of partitioning and throughput; each container maps to a synced collection. Organizations Supervisory and company hierarchies read to drive routing and reporting in other systems. Containers is specific to Azure Cosmos DB and Organizations to Workday — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Positions Job seats synced with recruiting and planning tools. Items (JSON documents) is specific to Azure Cosmos DB and Positions to Workday — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB and Workday

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Azure Cosmos DB Workday Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

DeliveryEach detected change is written to Workday through its API, with automatic retries and rate-limit backoff.

Workday Azure Cosmos DB Interval-based propagation

DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.

DeliveryEach detected change is applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.

What ships with Azure Cosmos DB ⇄ Workday

Connect Azure Cosmos DB and Workday for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Workday connection.

Real-time

Two-way sync

Changes in Azure Cosmos DB or Workday instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Cosmos DB or Workday data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Azure Cosmos DB or Workday record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Workday sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Workday.

How the Azure Cosmos DB and Workday connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

Workday

Integration surface
SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
Authentication
OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
Change detection
Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
Capabilities
read · write
How it works

How to connect Azure Cosmos DB to Workday — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Azure Cosmos DB and Workday with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Cosmos DB connected
    Workday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Cosmos DB and Workday objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Cosmos DB ⇄ Workday
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Cosmos DB Workday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure Cosmos DB and Workday integration FAQ

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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 427 integrations available for Azure Cosmos DB and Workday.

Popular · 7 of 427
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.