Workday AI Agents: APIs, Use Cases and Governance
Understand Workday's native AI agents and how Major coordinates HR handoffs through custom API connections, stateful review apps, and approval-gated workflows.

Workday AI agents include Workday's own agents and agents on Major that coordinate work around Workday records. This guide covers native capabilities, the custom API connection to Major, verified endpoints, and practical HR automations with state, approvals, and audit history.
Major's agents build deterministic apps for repeatable work, keeping the database and review queue outside the model while reserving judgment for the agent.
What Workday is and who relies on it
Workday holds employee and organizational records that HR operations, HRIS administrators, payroll teams, and people managers rely on. Its Staffing reference covers workers, jobs, job profiles, supervisory organizations, check-ins, and job changes. Those objects connect an employee's identity to the role and organization that downstream processes need.
An onboarding specialist needs to know whether a recruiting handoff became the right worker record. An HRIS administrator needs to distinguish a requested transfer from one that finished its business process. A workforce planner needs current staffing context before interpreting a scheduling gap.
These jobs cross system boundaries. Recruiting evidence may live in Greenhouse, shift information in UKG, and a request for clarification in Slack. Copying the same information between screens creates another reconciliation job.
Major adds a governed operational layer around those handoffs. An app stores source IDs, reconciliation results, and approvals. An agent interprets ambiguous evidence, such as two departments with similar names. A workflow retrieves records, runs checks, and routes the result. Workday remains authoritative for its employee records and configured business processes.
Workday AI agents and the tool's built-in AI
Workday has its own substantial AI offering. Its current AI agents page describes Sana as the experience that anticipates actions, advises users, and orchestrates agents grounded in business data and rules. The page names Payroll Agent, Talent Acquisition Agent, Workforce Management Agent, and Organizational Development Agent.
For Payroll Agent, Workday describes catching payroll issues before payday and supporting proactive oversight. These native capabilities deserve consideration when the job is already covered by your Workday products and policies. Confirm availability, licensing, and enabled functionality with your Workday administrator rather than assuming every named agent is available in every tenant.
Major adds value when the surrounding process needs its own durable software: a Greenhouse handoff ledger, a UKG staffing exception queue, or a restricted review screen spanning several systems. An agent can build the app that stores those cases, then use it on later runs instead of reconstructing their history from chat.
The boundary is organizational, not a claim that Workday lacks AI or cross-system capabilities. Choose a specific process owner and control surface. Avoid running two independent agents that can initiate the same employee change without shared ownership and reconciliation.
How Workday connects to Major
Workday has no native or Pipedream connector in the catalog: it connects as a custom API connector, with base URL and auth configured once by IT. A catalog label alone is not proof of an available packaged connection.
Workday's REST fundamentals distinguish two URL patterns. External integrations use https://{tenantHostname}/api/{serviceName}/{version}/{tenant}. Extend and Orchestrate use a regional API Gateway; the documented US Staffing example is https://api.us.wcp.workday.com/staffing/v7. IT must choose the pattern appropriate to the integration, tenant, and region rather than copying an example hostname.
Set up the connection in this order:
- Have the Workday administrator approve the identity, API client, service versions, and security policies.
- Configure the custom connector with the approved base URL and OAuth arrangement.
- Store credentials centrally in Major's connector vault, never in code or prompts.
- Give the app, agent, and workflow only the read or action permissions their jobs require.
- Test visibility and denial cases before enabling production writes.
SSO, RBAC, and audit logs cover the Major app, agent, and workflow. Workday's authorization still applies independently. Major orchestrates Workday; it never replaces it.
Workday API guide for apps, agents, and workflows
Start with the REST overview, then select a production service version. The six operations below are relative paths from Staffing v7, not universal tenant URLs.
Authentication and permissions
Workday documents OAuth in its authentication guide. Its authorization flows distinguish authorization code, authorization code with PKCE, and client credentials for the external Extend context. Do not assume that a grant supported in one context automatically authorizes another tenant integration.
The worker retrieval reference names the functional scope Staffing. Under REST security policies, scopes do not replace domain and business process permissions. REST requires Report/Task permissions, including for an Integration System User: View for reads and Modify for writes. SOAP Integration Permissions are not interchangeable with these permissions.
Pagination, limits, events, and testing
REST fundamentals document limit and offset pagination, with a default limit of 20 and maximum of 100. Persist progress only after successfully recording each page. The worker collection also documents an option to include terminated workers; verify that setting when reconciling departures.
A universal numeric REST rate limit and quota response headers are not documented publicly in the pages reviewed. The headers guide documents external request correlation headers, but no general quota header contract. Monitor response status, latency, and error volume; obtain tenant-specific limits before choosing polling concurrency.
Business process events are created when a UI task or supported POST initiates a process. These are not automatically outbound webhooks. A generic worker-change webhook payload, signing header, verification algorithm, and delivery retry schedule are not documented publicly in the reviewed REST pages. Use scheduled reconciliation unless IT provisions and documents an authenticated event integration.
For testing, Workday documents validate-only mode, using x-validate-only: 1 to check mutation requests without persisting data. It is not a substitute for an administrator-provisioned nonproduction environment or end-to-end testing. No anonymous public sandbox is documented in these pages.
GET /workers
Retrieves a worker collection with current staffing information.
- App: Hold a restricted reconciliation view keyed by Workday identity, not display name.
- Agent: Compare authorized staffing context with a UKG exception and explain the likely mismatch.
- Workflow: Page through a scheduled read and checkpoint successful results before advancing.
GET /workers/{ID}
Retrieves worker-specific staffing information for an authorized identity.
- App: Display the latest verified worker snapshot beside a handoff record.
- Agent: Assess whether conflicting recruiting and worker evidence warrants HR review.
- Workflow: Refresh the record before a consequential action instead of trusting yesterday's snapshot.
GET /workers/{ID}/serviceDates
Retrieves service dates for the specified worker.
- App: Show relevant service dates and the time they were checked.
- Agent: Explain why a recruiting start date and recorded employment history may indicate a rehire or stale handoff.
- Workflow: Retrieve dates for flagged records and attach the evidence to the review case.
GET /workers/{ID}/checkIns
Retrieves a collection of check-ins for a worker, subject to authorization.
- App: Present an access-controlled review workspace without exporting personnel notes broadly.
- Agent: Draft a summary of authorized check-in context for the permitted reviewer.
- Workflow: Run the requested read and deliver the draft to that reviewer, not a public channel.
POST /workers/{ID}/jobChanges
Initiates a job change request and returns a job change ID for subsequent operations.
- App: Store the approved proposal, returned ID, and request outcome.
- Agent: Evaluate inconsistent role descriptions and recommend a mapping with reasons.
- Workflow: Require approval, initiate the authorized request, and reconcile its progress without treating initiation as completion.
POST /workers/{ID}/organizationAssignmentChanges
Initiates an organization assignment change and returns the change event's ID.
- App: Preserve the proposed assignment, approval evidence, and returned identifier.
- Agent: Interpret an ambiguous department request against approved organizational context.
- Workflow: Submit only the approved request, then track the resulting business process separately.
Workday automation use cases on Major
Greenhouse and Workday onboarding readiness
Offer acceptance can begin preparation, but it is not proof that a hire was processed. Keep the actual hire handoff and worker verification separate.
- App: Store the recruiting reference, mapped organization, exceptions, and eventual Workday identity.
- Agent: Resolve ambiguous mappings and flag possible rehires without inventing a worker-creation operation.
- Workflow: Route exceptions to HR and verify the resulting worker through GET /workers/{ID} and GET /workers/{ID}/serviceDates. Hire execution uses the organization's approved handoff mechanism.
Workday and UKG staffing discrepancy review
A current employee roster does not establish shift eligibility or coverage by itself. The agent needs authorized schedule context and should explain uncertainty.
- App: Keep worker-to-scheduling identity mappings and discrepancy history.
- Agent: Assess whether a gap reflects stale staffing data, a mapping problem, or a scheduling question.
- Workflow: Reconcile GET /workers with authorized UKG records and route proposed schedule adjustments to workforce planning. It does not silently change shifts.
Workday and Slack transfer review
A team transfer can require interpretation before any assignment changes. Slack can carry a restricted notification linking to the review app rather than exposing the employee's full record.
- App: Show the old snapshot, proposed assignment, reviewer, and approval status.
- Agent: Explain the requested transfer and flag conflicting department evidence.
- Workflow: Refresh with GET /workers/{ID}. After approval, use POST /workers/{ID}/organizationAssignmentChanges only where IT has enabled that process.
These are design patterns, not claims that every associated API or write permission comes preconfigured. Start read-only, validate identities across systems, and add one approved action at a time. Compensation notifications require separately verified compensation access; staffing reads alone do not establish salary changes.
How to build the Workday architecture on Major

Workday architecture: scoped context, agent judgment, and a durable app
Build the review app first. Its managed database should hold source identities, observed record versions, exceptions, proposed actions, approvals, and execution receipts. The UI exposes those records to the appropriate role. It does not decide whether an employee should transfer.
The workflow owns the trigger and orchestration: scheduled reads, deterministic validation, connector calls, retries, and approval routing. The agent receives only cases that need interpretation, such as an unfamiliar department label or conflicting employment dates.
Use the app as the execution ledger. A successful read, a draft recommendation, a human approval, and a confirmed write are different states. Keeping those states separate lets another authorized operator resume a case without rerunning the agent or repeating an action.
Once an approved mapping becomes a repeatable rule, implement it in the app's deterministic validation logic. The agent can build and reuse that software while continuing to judge novel exceptions. This is Major's reason once, run forever model applied to HR operations, with Workday security remaining a separate boundary.
A worked example with numbers
For example, suppose HR operations reviews 200 cross-system staffing exceptions each month. This is an illustrative planning scenario, not a customer result or a performance promise.
Before the build, assume each item takes 12 minutes: six minutes locating evidence, four minutes interpreting the discrepancy, and two minutes recording the outcome. That is 200 × 12 = 2,400 minutes, or 40 hours monthly.
After introducing the review app, assume 150 routine cases need four minutes each because the evidence and approved mappings are already assembled. The remaining 50 ambiguous cases still need 12 minutes each. Human review totals 150 × 4 + 50 × 12 = 1,200 minutes, or 20 hours.
Allow another four hours monthly for maintaining mappings and reviewing failures. The illustrative operating total becomes 24 hours, a difference of 16 hours from the original 40. This excludes implementation effort, platform usage, and Workday administration.
Follow one ambiguous case through the system: the workflow records the snapshot, the agent explains a department mismatch, HR approves a corrected mapping, and the app retains the evidence and receipt. Measure actual handling time, reopened cases, and false matches before adopting the assumptions in a business case.
Governance and failure handling

Approval routing: record observations automatically, gate consequential actions
An agent must not approve its own employment, compensation, or sensitive disclosure decisions. Require an authorized person to review the exact proposed change, its evidence, and its destination. An approval should expire when the underlying record changes.
Keep read-only execution separate from mutation permissions. A summary agent does not need job-change initiation rights. A scheduling reviewer does not automatically need access to private check-in content.
For failures, use bounded retries with increasing delays and jitter for transient responses. Reduce concurrency after throttling. Stop and escalate permission failures rather than repeatedly submitting the same denied request.
After a write timeout, reconcile the recorded request and any returned event identifier before retrying. A missing response is not proof that Workday rejected the action. Deduplicate incoming signals in the app using source identity and event or record version, and retain failed cases for review.
Audit records should identify the requesting user, connector identity, source snapshot, agent recommendation, approver, execution attempt, and final receipt. Keep sensitive payloads out of broad logs. Apply retention rules to copied HR context, not just the source system.
Workday AI Apps, Agents and Workflow Automations
Every published Major use case that works with Workday, newest first. Each one names the Workday API objects involved and shows the app, agent and workflow split.
- Citizen Developers in the AI Era: Business Teams Build, IT Governs: AI gives business teams new power to build apps and workflows. A citizen development program makes that speed safe: clear ownership, risk tiers, reusable controls, and IT oversight built into the platform.
- Automate Greenhouse-to-Workday New-Hire Handoffs: Turn a Greenhouse hire into a verified Workday handoff. Design the field checks, approval gate, and durable audit trail that keep HR onboarding from re-keying the same data twice.
Frequently asked questions
What are Workday AI agents?
Workday AI agents are Workday's native agents for business tasks, with Sana coordinating the experience. Agents on Major are separate: they interpret authorized context and use stateful apps and workflows to coordinate a defined process around Workday.
Does Major have a native Workday connector?
No. Workday connects to Major through a custom API connector, with the base URL and authentication configured once by IT. Credentials stay in the central connector vault, while Workday security policies and Major permissions control access.
Can an agent create a Workday worker through the collection endpoint?
Do not assume that worker retrieval implies worker creation. The documented staffing operations in this guide retrieve workers or initiate specific changes. New-hire execution must use your organization's approved hire mechanism and its verified documentation.
How do Workday API permissions work?
OAuth access is constrained by Workday's security model. REST calls require applicable domain and business process access, including Report/Task permissions. A functional scope such as Staffing does not grant unrestricted employee access or bypass approval requirements.
Can Workday send a webhook for every worker change?
A universal worker-change webhook contract is not documented in the REST pages reviewed here. Do not invent a signature header or retry schedule. Begin with scheduled reconciliation, or have IT document the specific event integration, authentication, and replay behavior.
How should we test Workday automations?
Start read-only and use an administrator-approved nonproduction environment. Workday documents validate-only requests for checking mutations without persisting data. Test denied permissions, duplicate signals, stale approvals, and write timeouts as well as the successful path.
Sources
The official pages below were reviewed for the API and product boundaries described here. Endpoint links open the operation within Workday's interactive reference. The version, authorization context, and tenant configuration still need verification during implementation; public documentation does not establish permission to execute a business process.
- Workday REST APIs overview, the REST service model.
- REST API fundamentals, URL patterns, versions, and pagination.
- REST authentication, authentication contexts.
- Authorization flows, external Extend OAuth options.
- REST security, domain and business process policies.
- REST headers, documented header categories.
- Validate-only mode, validation without persistence.
- Business Process REST APIs, initiation, events, and steps.
- Workday AI overview and Workday AI agents, current native product descriptions.
- Worker collection and worker detail, staffing retrieval.
- Service dates and check-ins, worker subresources.
- Job changes and organization assignment changes, specific process initiation operations.
Start building on Major
Build a Workday reconciliation app with a durable exception queue, an agent for ambiguous cases, and workflows that require approval before consequential actions.
About the author
Ritvij Gautam is Head of Growth at Major.
Last reviewed November 19, 2026 by Ritvij Gautam.
Frequently asked questions
- What are Workday AI agents?
- Workday AI agents are Workday's native agents for business tasks, with Sana coordinating the experience. Agents on Major are separate: they interpret authorized context and use stateful apps and workflows to coordinate a defined process around Workday.
- Does Major have a native Workday connector?
- No. Workday connects to Major through a custom API connector, with the base URL and authentication configured once by IT. Credentials stay in the central connector vault, while Workday security policies and Major permissions control access.
- Can an agent create a Workday worker through the collection endpoint?
- Do not assume that worker retrieval implies worker creation. The documented staffing operations in this guide retrieve workers or initiate specific changes. New-hire execution must use your organization's approved hire mechanism and its verified documentation.
- How do Workday API permissions work?
- OAuth access is constrained by Workday's security model. REST calls require applicable domain and business process access, including Report/Task permissions. A functional scope such as Staffing does not grant unrestricted employee access or bypass approval requirements.
- Can Workday send a webhook for every worker change?
- A universal worker-change webhook contract is not documented in the REST pages reviewed here. Do not invent a signature header or retry schedule. Begin with scheduled reconciliation, or have IT document the specific event integration, authentication, and replay behavior.
- How should we test Workday automations?
- Start read-only and use an administrator-approved nonproduction environment. Workday documents validate-only requests for checking mutations without persisting data. Test denied permissions, duplicate signals, stale approvals, and write timeouts as well as the successful path.