Real-time
Two-way sync
Changes in Treasuredata or Workday instantly reflect in both systems. No stale data, no manual imports.
Analytics ⇄ Accounting and finance
Treasuredata to Workday integration — real-time, two-way sync
Keep Treasuredata 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 Treasuredata and Workday
Feed the customers, invoices, and revenue records in Workday into Treasuredata in real time, so dashboards and reports run on current numbers instead of last night's export.
Workday holds the financial truth: who the customers are, what they were invoiced, what they paid, and what revenue landed. Treasuredata is where that data is turned into dashboards, reports, and metrics, but it only reflects the world as of its last load. When the connection between them is a scheduled extract or a hand-built pipeline, analysis runs a step behind the books, and the numbers on a chart rarely match the numbers in the finance system.
Stacksync keeps Workers, Organizations, Positions, Compensation in Workday in sync with Query Jobs, Databases, Tables, Master (Parent) Segments in Treasuredata, field by field and in real time. A customer, invoice, or amount created or corrected in Workday shows up in Treasuredata within seconds, mapped to the right record. Where Treasuredata keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Treasuredata already tracks.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning's reporting running on yesterday's figures.
Common use cases
- 01 Sync worker records from Workday into IT and identity systems so hires, transfers, and terminations provision access automatically.
- 02 Replicate worker, organization, and compensation data into a secured database for people analytics without giving analysts tenant access.
- 03 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
- 04 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
Common sync patterns
Revenue alongside the rest of the data
The amounts Workday records sit next to product, usage, or operational data in Treasuredata, so a single view combines what was billed with what actually happened.
Reports refresh as the books change
Instead of waiting for a scheduled load, Treasuredata updates the moment a figure moves in Workday, so a dashboard opened at any point in the day is current.
Where Treasuredata keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Workday attaches to the matching account or user in Treasuredata, so segments and cohorts can be cut by real financial standing.
What you can sync between Treasuredata 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.
| Treasuredata objects | Workday objects | How this pairing syncs | |
|---|---|---|---|
| Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. | Suppliers Workday Financials vendor records aligned with procurement tools. | Tables is specific to Treasuredata and Suppliers to Workday — each maps to any object or custom field on the other side. | |
| Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. | Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. | Master (Parent) Segments is specific to Treasuredata and Customers and Invoices to Workday — each maps to any object or custom field on the other side. | |
| Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. | Journal Entries Accounting entries imported from external subledgers into Workday Financials. | Segments is specific to Treasuredata and Journal Entries to Workday — each maps to any object or custom field on the other side. | |
| Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. | Custom Reports (RaaS) Tenant-defined reports exposed as web service endpoints, often the practical read surface for syncs. | Journeys is specific to Treasuredata and Custom Reports (RaaS) to Workday — each maps to any object or custom field on the other side. | |
| Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. | Workers The central HCM record covering employment, job, and personal data; the anchor of most syncs. | Predictive Segments is specific to Treasuredata and Workers to Workday — each maps to any object or custom field on the other side. | |
| Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. | Organizations Supervisory and company hierarchies read to drive routing and reporting in other systems. | Scheduled Queries is specific to Treasuredata and Organizations to Workday — each maps to any object or custom field on the other side. |
How changes propagate between Treasuredata 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.
Treasuredata Workday Interval-based propagation
DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.
DeliveryEach detected change is written to Workday through its API, with automatic retries and rate-limit backoff.
Workday Treasuredata 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 written to Treasuredata through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Treasuredata ⇄ Workday
Connect Treasuredata and Workday for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Treasuredata–Workday connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Treasuredata 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 Treasuredata or Workday record.
Observability
Monitoring
Track your Treasuredata ⇄ Workday sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Treasuredata and Workday.
How the Treasuredata and Workday connectors work
Treasuredata
- Integration surface
- TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
- Authentication
- API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
- Change detection
- Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
- Capabilities
- read · write
- Rate limits
- TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
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 Treasuredata 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.
- 01
Connect your apps
Authenticate Treasuredata 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.
Treasuredata
connected
Workday
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Treasuredata 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.
objects · Treasuredata ⇄ WorkdayCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Treasuredata WorkdayCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Treasuredata and Workday integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Treasuredata and Workday: authenticate both systems, choose the objects to sync (such as Treasuredata's Tables and Master (Parent) Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Treasuredata: TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys. Authentication: API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints). Workday: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Workday: SOAP operations such as Get_Workers accept transaction-log criteria, letting integrations request only objects changed since the last run. Treasuredata: The Audience (CDP) API and the core TD API v3 are separate surfaces — segments and journeys live behind the Audience API while databases, tables, and jobs live behind TD API v3, both authenticated with the same TD1 API key. Stacksync's field mapping accounts for these differences between Treasuredata and Workday without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Treasuredata and Workday records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Treasuredata and Workday connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Treasuredata–Workday integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Treasuredata and Workday. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 369 integrations available for Treasuredata and Workday.
Popular · 4 of 369
No integrations match .
