Building Agents on Workday’s Guardrails

In this article we discuss:

• Three Paths, One Set of Guardrails
• Workday’s Commitment to Developers
• Build Agents on Guardrails You Actually Trust

Three paths to build with Workday without giving up speed or safety.

• Path 1 — Host your own agent with Workday Agent-Ready Tools (Early Availability)
• Path 2 — Run agents on the Workday platform, surfaced in the AI of your choice
• Path 3 — Use the full, AI-native solution with Sana from Workday

A lot of what passes for “agentic development” today rests on a fragile idea: cram a policy handbook into an LLM’s context window, hit run, and hope the model doesn’t hallucinate its way into a mess.

That doesn’t work for Workday’s world of people and money. If an agent skips a compliance step or approves pay outside your grid, you’re not dealing with a minor hallucination. You’re dealing with an audit, a regulator, or a lawsuit. That kind of risk demands a different engineering bar. So we’re taking a different approach that’s built for both precision and speed. 

As a developer, you shouldn’t be reverse‑engineering how Workday enforces those rules or trying to bolt on your own guardrails afterward. You should be able to see the rules, call into them, and trust that the platform will stop bad actions before they happen.

That’s what these three paths are about: letting you build your agents while Workday owns the rules, approvals, and audit trail.

Three Paths, One Set of Guardrails

The future of agents in the enterprise is going to be open. Different teams will pick different models, toolchains, and front doors. Different problems will need different reasoning patterns. Giving you three paths means you can pick the one that gets you into production fastest for each use case, without compromising on guardrails.

We’re not trying to lock you into a single stack. Instead, we’re giving you clear choices along two axes:

• Logic: Where does the reasoning happen, on the Workday platform or elsewhere?

• Location: Where does the experience live, in your chosen front door or in a Workday-delivered interface?

By “reasoning,” we mean the agent’s steps and decisions: which tools it calls, in what sequence, under which policies, to fulfill a request.

Whether you want to build your own autonomous agent, pull a Workday-delivered agent into chat, or use a full workspace, you get choice without giving up safety or velocity.

Path 1: Host your own Agent with Workday Agent-Ready Tools (Early Availability)

Workday Agent-Ready Tools are a new class of connectors built for AI agents, not human-written integrations. Instead of having an engineer wire your bot into a mesh of REST and SOAP APIs, you bind Agent-Ready Tools to your agent over the Model Context Protocol (MCP), and the agent calls them directly.

Agent-Ready Tools are different by design:

• Flat and self-describing, so models and orchestrators can infer how to use them without extra glue code

• Optimized for low-latency, conversational use

• Available natively over MCP for Claude, ChatGPT, Gemini, Microsoft Copilot, and custom orchestrators

• Scoped to the end user’s identity, with extra safeguards on sensitive HR and finance actions

Traditional Application APIs still power classic integrations and will keep doing so—but they’re built to synchronize data between systems with a developer in the loop. Agent-Ready Tools flip that: they guide agents with the context they need to make high-quality decisions in real time.  

Workday still owns the business logic, approvals, and audit trail. Your agent decides when to call a tool.

For example: “Request time off next Friday,” your agent must figure out the logic: check the calendar, check budgets, check relevant policies, and check PTO balance. With Agent-Ready Tools, this becomes one tool call over MCP as a secure plugin. Workday handles the heavy lifting of balance enforcement, routing  approvals, and executing the updates. You control the interface and reasoning chain with maximum flexibility and control; Workday enforces the rules at the tooling level.

Agent-Ready Tools are available in Early Availability for MCP-based agent stacks.

Path 2: Run agents on the Workday platform, surfaced in the AI of your choice

Sometimes you don’t want to waste time rebuilding, debugging, and maintaining Workday’s logic in your own agent at all. You just want to ask a question in Gemini or Copilot and have Workday figure it out.

Path 2 does that. Your front door (Copilot, Gemini, or another partner) talks to agents that run on Workday — whether they’re delivered by Workday or custom-built by your developers. The agents run inside Workday, with direct access to rules, data, org structure, and live business processes.

You keep your chosen interface. The reasoning stays on Workday’s guardrails.

For example: Take the same time-off example from Path 1, but make it real. An employee asks, "Can I take the first week of August off?" Answering that well isn't one lookup, it's a chain: do they have the balance, do any of those days fall in a department blackout, is there a company holiday in the middle they shouldn't have to spend PTO on, and is the team already short that week?

Each of those checks is a guarded tool call either way. But knowing which to run, in what order, and what to do when one comes back "no" — that's the reasoning. In Path 1, your agent owns that chain and has to keep it correct as policy changes. In Path 2, you hand the whole question to Workday, it reasons across all of it on the same rules your HR and finance teams already trust, and comes back with an answer the employee can act on.

That's the trade: Path 1 gives you the most control over the agent; Path 2 hands the multi-step reasoning to Workday so you don't have to build or maintain it.

Some of our largest partners are integrating with Workday this way, including:

• Google Gemini Enterprise, giving users access to the Sana Self-Service Agent to answer common questions and execution actions directly inside Google tools.

• Microsoft 365 Copilot, surfacing the Sana Self-Service Agent so employees can pull Workday context, policies, and processes into Teams, Outlook, and the broader Microsoft ecosystem.

And if you'd rather build your own agents that run on Workday alongside ours, Developer Agent does the heavy lifting — describe the use case in plain language, from your preferred development tool over MCP (Claude Code, Cursor, Google Antigravity, Cline), and Developer Agent defines, wires up, and registers the agent for end-to-end governance, 

The conversation stays where your employees work. The reasoning and enforcement stay inside Workday, with consistent rules, approvals, and an audit trail for every action.

Path 3: Use the full, AI-native solution with Sana from Workday

Chat is great—until it isn’t. Some problems are simply too multi‑dimensional for a single prompt.

Sana from Workday gives you a full workspace when you need one. 

For example: You’re thinking of planning an offsite and need to know if the dates and budget line up. In Sana, you see all of that in one place while the Sana Travel Agent handles the rules and actions underneath, so you can quickly decide and move forward.

It can pull in:

• Budgets, policies, and approvals from Workday
• PTO and team availability from Workday
• Key meetings and deadlines from Outlook
• Expense data to eliminate manual reporting

This is an AI‑native workspace built specifically for Workday’s people‑and‑money world, not a generic canvas with a chatbot bolted on.

Choose Sana when the experience itself is the product—when you care about adoption, visual reasoning, speed to decision, and workflow design as much as you care about which model is running.

Sana from Workday and the Sana Self-Service Agent are available to all Workday customers today. 

Workday’s Commitment to Developers

If you’re building on Workday, you’re betting more than a side project on us. So here’s our commitment to you:

We are:

• Publishing open interfaces for open agentic protocols like MCP and A2A, and helping shape them
• Recommending Agent-Ready Tools for new agent work
• Investing heavily in identity, process, audit, and security so you don’t have to rebuild them in every agent
• Accelerating the Workday Agent Partner Network while keeping quality and safety non-negotiable

We’re not:

• Forcing you into one model, harness, or agent stack
• Blocking third‑party agents from talking to Workday
• Walking away from Application APIs—they still power classic integrations

Build Agents on Guardrails You Actually Trust

Enterprise AI is shifting fast: more open stacks, more ambitious agents, and much less tolerance for “it usually does the right thing.”

Workday gives you three ways to build in that world:

• Your own agent, calling Workday safely
• Workday agents behind your chosen front door
• A full AI workspace with Sana from Workday

Three paths, one platform underneath. Every one runs on the same rules and audit trail. Sana adds an experience built for decisions too big for a single prompt. Pick your path and build what's next, without choosing between speed, safety, and experience.