Workday logo

Workday

ERP & FinanceService accountLive

Workday is the dominant enterprise platform for HCM and finance. Large customers run mission-critical payroll, benefits, recruiting, and general ledger entirely inside it, making a reliable integration a prerequisite for any product that touches workforce or financial data.

What you can do

Read worker records in real time

Pull active and terminated workers by Worker ID, including hire date, job profile, cost center, and manager chain. Askel handles pagination and the Workday-specific effective-date model so your product always sees current data.

Sync organizational structure

Read supervisory organizations, cost centers, and company hierarchies. Askel normalizes Workday's tree-structured org data into a flat list your product can consume without understanding Workday's org-type taxonomy.

Pull position and headcount data

Read open and filled positions with headcount budgets, job requisitions, and position restrictions. Useful for workforce-planning tools that need to show capacity against actuals.

Access compensation and pay component data

Read compensation grades, salary plans, and individual pay components for workers. Askel respects the ISU role's data-access restrictions, so only the pay data the customer explicitly grants is returned.

Run RaaS reports on a schedule

Customers often encode complex business logic in Workday custom reports exposed as RaaS endpoints. Askel can call a RaaS report by its URL slug (e.g. /CCX/service/customreport2/acme/...) on a schedule and page through the JSON output.

Write back to Workday via integration events

For supported business processes, Askel can submit inbound integration events (such as worker data changes or absence requests) back to the customer's Workday tenant using the configured ISU's write permissions.

Sample use case

Keeping a workforce-analytics product in sync with a customer's Workday HCM

Crestline Partners sells a headcount-analytics product to mid-enterprise HR teams. A new customer, Talvera Manufacturing, runs all 4,200 workers in Workday. Every night, Talvera's HR ops team expects active worker records, current positions, and updated compensation bands to land in Crestline's platform so managers can build headcount plans against live data.

  1. 1

    Provision the ISU

    Talvera's Workday admin creates an Integration System User (ISU) named INT_CRESTLINE_SVC, assigns it a security group with read access to Worker Data, Position Data, and Compensation, and creates an API client in Workday's OAuth 2.0 setup. The admin notes the client ID, client secret, and tenant alias (talvera).

  2. 2

    Paste credentials into Askel

    Talvera's admin enters the client ID, client secret, and tenant alias into the Askel setup screen inside Crestline's product. Askel constructs the base URL (https://wd2.myworkday.com/talvera) and confirms connectivity by fetching the worker count.

  3. 3

    Schema discovery

    Askel reads Talvera's Workday metadata: available custom fields on the Worker object (such as custom_field_costcenter_override), the supervisory org tree, and any RaaS reports the ISU can access. Crestline's CS team sees a mapping draft within minutes.

  4. 4

    Map and validate

    Two custom compensation fields do not auto-map. A Crestline CS rep reviews Askel's suggestions, confirms the correct field names with Talvera's HR ops lead, and runs a dry-run against 100 real worker records to verify the output matches expectations.

  5. 5

    Go live

    The nightly sync is enabled. Askel fetches all active workers, positions, and compensation records from Talvera's Workday tenant and writes them into Crestline's platform. Terminated workers are flagged, not deleted, so historical headcount data is preserved.

Authentication

Service account

Customer's Workday admin registers an Integration System User and an API client, then pastes the client credentials and tenant alias into Askel. Askel mints short-lived OAuth tokens per request via refresh-token grant; no user passwords are stored.

Data flow

How Askel sits between your product and the customer's system

Data flow between Customer's Workday tenant, Askel, and Your productCustomer's Workday tenantAPI endpointAskelauth · mapping · driftYour productyour backend
WorkersPositionsOrganizationsCompensationPay componentsTime off

FAQ for Workday

Which Workday tenant types are supported?+
Production, Implementation (sandbox), and GovCloud tenants are all supported. Askel uses the tenant alias you provide to construct the correct base URL, so the same setup flow works regardless of environment. We recommend testing against a sandbox tenant before connecting production.
What is the difference between using RaaS reports and the Workday REST API?+
Workday REST (and the older SOAP WWS) gives direct access to objects like Worker and Position with fine-grained field selection. RaaS reports are custom reports that a customer's Workday admin has already built and published as a web service; they often encode complex filtering logic that is hard to reproduce via raw API calls. Askel supports both: it calls REST endpoints for standard objects and can call RaaS URLs for customer-built reports.
What permissions does the Integration System User need?+
The minimum required security group depends on what data your product reads. For HCM data, the ISU needs the Worker Data domain and, if reading compensation, the Compensation domain. For finance data it needs access to Financial Accounting. Askel generates a permissions checklist during setup that you can hand to the customer's Workday admin.
Does this work in Workday sandbox tenants?+
Yes. Workday sandbox (Implementation) tenants have the same API surface as production and are the recommended place to test a new integration. Point Askel at the sandbox tenant alias, complete the setup, and validate the data before switching to the production tenant alias. The two are independent connections in Askel, so you can run both in parallel during rollout.
Ready to ship integrations faster?customers faster?implementations faster?
Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.
Security & Compliance
ISO 27001 Certified
GDPR Compliant

© 2025 Askel.ai. All rights reserved.