Skip to main content
Book a demo

Connect Workday to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to Workday’s 60 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot CLI setup guide

Set up

Add Workday to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.

  1. 1

    Approve Workday in Runlayer

    Add Workday from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Workday’s 60 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 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. 4

    Use Workday from GitHub Copilot CLI

    Workday’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.

Tools

60 Workday tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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.

See all 60 Workday tools

Control

What Runlayer can see and stop in GitHub Copilot CLI

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Workday call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot CLI 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 GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination