Connect Workday to Codex
Give Codex governed access to Workday’s 60 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Workday to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Workday in Runlayer
Add Workday from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Workday’s 60 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Workday
Sign in the way Workday requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Workday from Codex
Workday’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
60 Workday tools in Codex
Runlayer policy decides which of these Codex users can call. 40 read data only and 20 can change or delete data.
Request time off
Submit a time off request for a worker.
Get time off details
Get paginated time off entries for a worker with optional filters.
Get time off entry
Get a specific time off entry by ID.
Get time off balances
Get paginated absence balances for a worker.
Get eligible absence types
Get paginated absence types a worker is eligible to request.
Validate time off dates
Validate one or more requested time off dates for a worker.
Correct time off entry
Submit corrections for entries from one approved time off request.
Get leaves of absence
Get paginated leaves of absence for a worker.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Workday call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more