How long does the Workday integration take to ship?
Our standard window is thirty days from signed scope to live Workday adapter in production, plus a one-week monitored stabilization phase. For Bethlehem, Pennsylvania, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Does it work with our existing Workday licenses?
Yes — the adapter rides on top of your existing Workday subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Workday adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the Workday surface.
Is this a packaged Workday connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
Can the Workday adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Workday tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.