Workday Connector

Connector download

Download Workday

Versioned ZIP for your CXFabric tenant.

Sign in to download Using connectors

Register the ZIP in your tenant, or add a new version if the connector is already installed.
Create or select a credential if the action requires one.
In a Draft flow, add an available action, choose its version, connect it, and map inputs.
Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version history

v0.2.0.0Latest · 2026-10-04 · Implemented source
Replaces the generic HTTP scaffold with two explicit Staffing v7 reads: job-family and job-profile reference pages.
Full release notes View download
v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical configurable HTTP scaffold; not a vendor-specific implementation.
View download

Included in this version

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

Read one native offset page of selected visible references in tenant/token scope.

Read one native offset page of selected visible references in tenant/token scope.

Vendor API

Implementation considerations

Use an approved traditional tenant host/name and managed OAuth access token with Jobs & Positions scope and the appropriate reference security domains. Token lifecycle remains external.
The implementation uses the Staffing v7 Production Service. The legacy package name is retained for identity compatibility; WCP regional gateway routing and retired Common endpoints are separate contracts.
Missing optional fields remain omitted; exact native IDs, empty text and false inactive flags are preserved. Reference status does not establish staff availability.
Each action reads one page, with page size 1–100 and a declared local nonnegative int32 offset subset. Paging cannot establish a stable snapshot or full-tenant completeness.
Selected metadata excludes workers, personal profiles, payroll, relationship arrays and job changes. HTTP 404 and API errors remain failures.
Strict JSON, media and UTF-8 validation, a 1 MiB response cap and shared 1–8 second request budget are enforced without redirects, proxies or replay. Hosted import, executor support and live tenant/security-domain behavior remain untested.
Traditional tenanted Production Service reference reads require an approved issued OAuth token, scope and security domains. Live tenant behavior and hosted dependencies need validation.