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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
© 2025 Askel.ai. All rights reserved.