Workday
Read Workday HCM data: workers, jobs, organizations, absence balances and time off, contact information and time totals, and request time off.
About
Workday ships in the w6w first-party pack. It declares 25 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.workday- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Human Resources
Overview
Workday is the system of record for people at a large share of the enterprise, and its REST API is how the rest of the stack reads it. This app covers the read-heavy core of that API: look up workers and their jobs, walk the org chart through direct reports and supervisory organizations, read job profiles and families, and pull a person’s work email, phone and address.
It also covers time off. A workflow can list the absence types a worker is eligible for, validate the dates they want, read their balances, time off entries and leaves of absence, and submit the request itself through Workday’s own Request Time Off business process. Time totals for the current pay period are included for time-tracking reports.
It connects with a Workday API client and its non-expiring refresh token, per tenant: you give it your data-center host and tenant name, and it refreshes its own short-lived access tokens. Everything runs under the security policies of the Integration System User behind the client, so it only sees what that user may see. It does not run job changes or other staffing business processes, payroll, recruiting or the SOAP APIs.
Build with Workday
Three routes to the same 25 actions. The Workflow tab is generated from Workday's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List a worker's absence balances
absence-balance-list The balance of every absence plan and leave type for one worker, optionally as of a date or for a category. Absence Management v5 `GET /balances`; `worker` is required by Workday.
List the absence types a worker is eligible for
eligible-absence-type-list Time off types, absence tables and leave types a worker may request. Step 1 of Workday's request-time-off flow: the `id` here is the `timeOff` ID for valid dates and the `timeOffType` ID for the request. Absence Management v5 `GET /workers/{ID}/eligibleAbsenceTypes`.
List job families
job-family-list Job families with their job family group and job profiles. Active only unless `inactive` is set. Staffing service v7 `GET /jobFamilies`; secured by Job Information.
List jobs
job-list Jobs with job profile, business title, location, worker and supervisory organization. Staffing service v7 `GET /jobs`; secured by Worker Position: View.
List job profiles
job-profile-list Job profiles (`id`, `name`, `inactive`). Active only unless `includeInactive` is set. Staffing service v7 `GET /jobProfiles`; secured by Job Profile: View / Public Job: View.
List a worker's leaves of absence
leave-of-absence-list Leaves of absence for a worker, optionally within a date range or filtered by status and leave type. Absence Management v5 `GET /workers/{ID}/leavesOfAbsence`.
List organizations of a type
organization-list Organizations of one organization type (for example Cost Center or Company). Workday requires an organization type on this call. Common service v1 `GET /organizations`; secured by Reports: Organization.
Get a person
person-get A person: legal and preferred name plus links to every contact-information collection. The ID is the person `id` returned by a worker (`person.id`). Person v4 `GET /people/{ID}`.
List a person's work addresses
person-work-address-list A person's work addresses (address lines, city, postal code, country and usage). Person v4 `GET /people/{ID}/workAddresses`; secured by the matching Person Data / Self-Service domain.
List a person's work email addresses
person-work-email-list A person's work email addresses (emailAddress, usage and comment). Person v4 `GET /people/{ID}/workEmails`; secured by the matching Person Data / Self-Service domain.
List a person's work phone numbers
person-work-phone-list A person's work phone numbers (completePhoneNumber, device type and usage). Person v4 `GET /people/{ID}/workPhones`; secured by the matching Person Data / Self-Service domain.
Get a supervisory organization
supervisory-organization-get One supervisory organization by ID. Staffing service v7 `GET /supervisoryOrganizations/{ID}`.
List supervisory organizations
supervisory-organization-list Supervisory organizations with code, name, managers and active state. Active only unless `includeInactive` is set. Staffing service v7 `GET /supervisoryOrganizations`.
List a worker's time off entries
time-off-detail-list Time off entries for a worker, optionally within a date range or filtered by status and time off type. Absence Management v5 `GET /workers/{ID}/timeOffDetails`.
Request time off
time-off-request Create a time off request for a worker and start the Request Time Off business process. Workday's flow is three calls: list the eligible absence types, validate the dates, then this. By default the event is submitted; turn `submit` off to leave it in the initiator's inbox. Not idempotent — a retry creates a second request. Absence Management v5 `POST /workers/{ID}/requestTimeOff`.
Get a worker's reported hours
time-total-list A summary of reported hours for a worker over the period containing `periodDate` (today by default). Time Tracking v7 `GET /workers/{ID}/timeTotals`; secured by Process: Time Block REST APIs / Time Clock.
Validate time off dates
valid-time-off-date-list For each date asked about, whether the worker may take that type of time off and how many units. Step 2 of Workday's request-time-off flow. Absence Management v5 `GET /workers/{ID}/validTimeOffDates`.
List a worker's direct reports
worker-direct-report-list The workers who report directly to the given manager. Common service v1 `GET /workers/{ID}/directReports`; secured by Reports: Manager, Reports: Matrix Manager or Self-Service: My Team.
Get a worker
worker-get One worker with current staffing information: worker type, primary and additional jobs, prehire ID and the linked person. Staffing service v7 `GET /workers/{ID}`.
List a worker's history
worker-history-list The historical staffing events recorded for a worker. Common service v1 `GET /workers/{ID}/history`; secured by Worker Data: Historical Staffing Information.
List workers
worker-list Workers and their current staffing information (primary job, additional jobs, person). Non-terminated workers only unless `includeTerminated` is set. Staffing service v7 `GET /workers`; needs the Staffing scope and a domain security policy such as Worker Data: Public Worker Reports.
List supervisory organizations a worker manages
worker-managed-organization-list The supervisory organizations the worker is the manager of. Common service v1 `GET /workers/{ID}/supervisoryOrganizationsManaged`; secured by Reports: Organization.
List a worker's organizations
worker-organization-list Every organization a worker belongs to (supervisory, cost center, company and so on). Common service v1 `GET /workers/{ID}/organizations`; secured by Reports: Organization.
Get a worker's service dates
worker-service-dates Hire date and continuous service date for a worker. Staffing service v7 `GET /workers/{ID}/serviceDates`.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Workday's real ids.
{
"manifestVersion": "2",
"name": "workday-example",
"steps": [
{
"id": "absence-balance-list",
"uses": {
"app": "io.w6w.workday",
"action": "absence-balance-list",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"workerId": "<workerId>"
}
}
]
}Here are some of the things you can do
-
List a worker's absence balances
readabsence-balance-list -
List the absence types a worker is eligible for
readeligible-absence-type-list -
List job families
readjob-family-list -
Get a job
readjob-get -
List jobs
readjob-list
+20 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Workday, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Workday. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "absence-balance-list",
payload: {
workerId: "<value>",
// effective: "<value>",
// category: "<value>",
// limit: "<value>",
// offset: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action absence-balance-list --payload '{"workerId":"<value>"}'Give an AI agent Workday — without giving it Workday's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.workday#absence-balance-list",
"input": {
"workerId": "<workerId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Workday connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Workday's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Workday itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Workday declares its own checks, so its health is a property of the app rather than something the host guesses at.