How to integrate Workday MCP with CrewAI

This guide walks you through connecting Workday to CrewAI using the Composio tool router. By the end, you'll have a working Workday agent that can request vacation days for next week, check your current absence balance, find all open job postings i manage through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Workday account through Composio's Workday MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Workday logoWorkday
Oauth2

Workday is a cloud-based ERP platform for HR, finance, and workforce analytics. It streamlines employee management, payroll, and business operations in a single system.

84 Tools13 Triggers

Introduction

This guide walks you through connecting Workday to CrewAI using the Composio tool router. By the end, you'll have a working Workday agent that can request vacation days for next week, check your current absence balance, find all open job postings i manage through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Workday account through Composio's Workday MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Workday with

ChatGPTOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndex

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Workday connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Workday
  • Build a conversational loop where your agent can execute Workday operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

What is the Workday MCP server, and what's possible with it?

The Workday MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Workday account. It provides structured and secure access to your HR, payroll, and recruiting data, so your agent can perform actions like managing time off, retrieving employee details, tracking job postings, and analyzing interview feedback on your behalf.

  • Automated time off management: Easily create new time off requests or check absence balances for yourself or others, making leave management effortless.
  • Employee data and profile retrieval: Have your agent fetch profile details for the current user or any specified worker to simplify onboarding and HR processes.
  • Comprehensive job posting insights: Instantly retrieve information about job postings, including descriptions and screening questionnaires, to aid recruiters and hiring managers.
  • Interview feedback analysis: Let your agent pull and summarize interview feedback entries to streamline debriefs and improve hiring decisions.
  • Access to holiday and leave events: Quickly get holiday schedules and leave status values for better workforce planning and scheduling.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Workday connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Workday via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Workday MCP URL
6

Create a Composio Tool Router session for Workday

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["workday"])

url = session.mcp.url
What's happening:
  • You create a Workday only session through Composio
  • Composio returns an MCP HTTP URL that exposes Workday tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Workday and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["workday"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Workday through Composio's Tool Router. The agent can perform Workday operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Workday action and event your agent gets out of the box.

Create Business Title Change

Creates a business title change instance for a worker with the specified data.

Create Job Change

Tool to create a job change instance for a worker in Workday.

Create Payroll Inputs

Tool to create payroll inputs in Workday.

Create Time Off Request

Creates a time off request for the specified worker and initiates the business process.

Get Absence Balance

Retrieves balance information for a specific worker's absence plan.

Get Assignment Change Group Cost Centers

Retrieves cost center instances for organization assignment changes.

Get Assignment Change Group Jobs

Retrieves job instances for organization assignment changes.

Get Assignment Types

Retrieves assignment type values for job changes in Workday.

Get Business Title Change

Retrieves a business title change instance by ID.

Get Business Title Change For Worker

Tool to retrieve a business title change instance for a specific worker.

Get Candidate Availability Template

Tool to retrieve the candidate availability template version for a specific job posting.

Get Collection of Jobs

Tool to retrieve a paginated collection of jobs from Workday Staffing system.

Get Collection of Payroll

Tool to retrieve a collection of payroll inputs from Workday.

Get Company Insider Types

Retrieves company insider types from Workday Staffing API.

Get Contingent Worker Types

Tool to retrieve contingent worker types from Workday staffing API.

Get Country Info

Retrieves detailed information about a specific country from Workday.

Get Currencies

Retrieves currency instances for job changes in Workday.

Get Current User

Retrieves the current authenticated worker's profile information from Workday.

Get Grants

Retrieves grant instances for organization assignment changes.

Get Headcount Options

Retrieves headcount option instances that can be used as values for other endpoint parameters.

Get History Instance for Worker

Tool to retrieve a specific history instance for a worker.

Get History Items for Worker

Tool to retrieve a collection of history items for a specific worker.

Get Holiday Events

Returns the holiday events for the specified workers and time period.

Get Interview

Tool to retrieve detailed information about a specific interview from Workday Recruiting.

Get Interview Feedback

Retrieves interview feedback for the specified interview ID from Workday Recruiting API.

Get Job By ID

Tool to retrieve detailed information about a single job instance by its ID.

Get Job Change Frequencies

Retrieves frequency instances for job changes in Workday.

Get Job Change Location Info

Tool to retrieve location information for a specific job change in Workday.

Get Job Change Position

Retrieves position details for a specific job change in Workday Staffing API.

Get Job Change Reason Instance

Retrieves a job change reason instance from Workday.

Get Job Change Reasons

Retrieves a collection of job change reasons from Workday.

Get Job Change Reason Values

Retrieves job change reason instances that can be used as values for other staffing endpoint parameters.

Get Job Changes Group Templates

Retrieves job changes group template instances in Workday.

Get Job Changes Job Values

Retrieves job instances that can be used as values for job changes parameters.

Get Job Changes Worker Values

Retrieves worker instances that can be used as values for job changes parameters.

Get Job Classifications

Retrieves job classification instances for job changes in Workday.

Get Job Posting

Retrieves detailed information about a specific job posting including job description.

Get Job Posting Questionnaire

Retrieves screening questions and questionnaires associated with a specific job posting.

Get Job Profiles Values

Retrieves job profile instances from Workday Staffing API.

Get Job Requisition Values

Retrieves job requisition instances that can be used as values for other endpoint parameters.

Get Job Workspace

Tool to retrieve a single workspace instance for a specific job.

Get Job Workspaces

Tool to retrieve a collection of workspaces for a specified job ID.

Get Leave Status Values

Get all available leave status values from Workday.

Get My Job Postings

Retrieves job postings assigned to the authenticated user (current recruiter).

Get Organization Assignment Business Units

Retrieves business unit instances for organization assignment changes.

Get Organization Assignment Customs

Retrieves custom organization assignment instances.

Get Organization Assignment Funds

Retrieves fund instances for organization assignment changes.

Get Organization Assignment Regions

Retrieves region instances for organization assignment changes.

Get Organization Assignment Workers

Retrieves worker instances for organization assignment changes.

Get Pay Group by Job ID

Retrieves the pay group for a specified job ID.

Get Payroll Input Instance

Retrieves detailed information for a single payroll input instance by ID.

Get Pay Slip Instance for Worker

Retrieves a specific pay slip instance for a worker.

Get Pay Slips for Worker

Retrieves a collection of pay slips for a specific worker.

Get Proposed Position Values

Retrieves proposed position instances that can be used as values for job changes parameters.

Get Prospect

Retrieves a single prospect instance for talent matching and best-fit analysis.

Get Prospect Educations

Retrieves the educational background of a prospect from Workday Recruiting API for talent matching and best-fit analysis.

Get Prospect Experiences

Retrieves the work experience of a prospect for talent matching and best-fit analysis.

Get Prospect Resume Attachments

Retrieves resume attachments for a specific prospect to help prepare for upcoming interviews.

Get Prospect Skills

Retrieves the skills of a prospect from Workday Recruiting API for talent matching and best-fit analysis.

Get Supervisory Organization Values

Retrieves supervisory organization instances that can be used as values for job changes parameters.

Get Time Off Entries for Worker

Retrieves a collection of time off entries for a specific worker.

Get Time Off Plans For Worker

Retrieves a collection of time off plans for a specific worker.

Get Time Off Status Values

Retrieves available time off status values from Workday.

Get Time Types

Retrieves time type values for job changes in Workday.

Get Worker Business Title Changes

Retrieves business title changes for a specific worker.

Get Worker Eligible Absence Types

Retrieves a collection of eligible absence types for the specified worker.

Get Worker Info

Retrieves detailed worker information including staffing data.

Get Worker Leaves of Absence

Retrieves the Leaves Of Absence for the specified worker using the working absenceManagement v1 API.

Get Workers Collection Staffing

Tool to retrieve workers and current staffing information from Workday.

Get Worker Service Dates

Tool to retrieve service dates for a specified worker from Workday Staffing API v6.

Get Worker Staffing Information

Tool to retrieve a worker's current staffing information from Workday.

Get Worker Time Off Details

Retrieves a collection of time off details for the specified worker.

Get Worker Types

Retrieves worker type instances that can be used as values for job changes parameters.

Get Worker Valid Time Off Dates

Retrieves valid time off dates for a worker, indicating when they are eligible to take time off.

Get Workspace Instances

Tool to retrieve workspace instances that can be used as prompt values for other Workday API parameters.

Get Work Study Awards

Retrieves work study award instances for job changes in Workday.

List Countries

Retrieves country values from Workday Recruiting API.

List Interviews

Retrieves a list of interviews with job requisition and recruiter assignment details.

List Job Postings

Retrieves a paginated list of job postings from Workday Recruiting system.

List Jobs

Retrieves a collection of jobs from Workday Staffing system.

Retrieve Worker Leave of Absence

Retrieves the leave of absence details for a specified worker.

Update An Existing Payroll

Tool to partially update an existing payroll input instance in Workday.

Update Job Change Business Title

Partially updates the business title for a specific job change.

Update Message Template By ID

Tool to update a message template in Workday by its ID.

FRAMEWORKS

How to build Workday MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Workday MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Workday MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Workday MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Workday MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Workday MCP with Claude Cowork

Codex logo

Codex

Use Workday MCP with Codex

Cursor logo

Cursor

Use Workday MCP with Cursor

OpenClaw logo

OpenClaw

Use Workday MCP with OpenClaw

Hermes logo

Hermes

Use Workday MCP with Hermes

CLI logo

CLI

Use Workday MCP with CLI

Google ADK logo

Google ADK

Use Workday MCP with Google ADK

LangChain logo

LangChain

Use Workday MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Workday MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Workday MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Workday MCP with LlamaIndex

OpenCode logo

OpenCode

Use Workday MCP with OpenCode

VS Code logo

VS Code

Use Workday MCP with VS Code

FAQ

Frequently asked questions

With a standalone Workday MCP server, the agents and LLMs can only access a fixed set of Workday tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Workday and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Workday tools.

Yes, absolutely. You can configure which Workday scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Workday data and credentials are handled as safely as possible.

Start with Workday.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Workday tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies
Workday MCP Integration with CrewAI | Composio