Skip to content

We have been writing about MCP's potential since its earliest days. So when Workday shipped support for third-party agents, we finally got to move from writing to wiring.

We connected Claude Code into a live Workday GMS as a registered agent and had it change a worker's business title end to end:

Proposal → Human approval → Write → Verification

The moment that matters

The agent looks up the worker, drafts the exact change, and then stops:

"Nothing has been written. This is a proposal only, and I'm holding the confirm token."

It will not execute without an explicit yes, and it will not claim success until it re-reads Workday and sees the change with its own eyes.

Claude Code session showing the Workday agent proposing a business title change, holding the confirm token, and after approval reporting the change as submitted but not confirmed, pending Workday approval

The live session: read-only lookup, proposal with the confirm token held, explicit approval, then honest verification. The write landed as a Title Change event, and the agent reports it as submitted but not confirmed because the worker record still shows the old title, pending business process approval.

Four things make that possible

Your business process still governs. Our test change is sitting in an approval queue right now, exactly where it belongs.

What's next

How the token binding works, why the write sat in that approval queue, and the full Workday configuration behind it: that's a longer story. The detailed Claude-Workday build article is coming soon here on Perspectives. Follow along if you're putting agents anywhere near a system of record.

#Workday#Claude#MCP#AIAgents#AgentSystemOfRecord#Maturecloud
← Back to Perspectives