How to integrate Workday MCP with LangChain

This guide walks you through connecting Workday to LangChain 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 LangChain 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.

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 LangChain 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 LangChain 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

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Workday project to Composio
  • Create a Tool Router MCP session for Workday
  • Initialize an MCP client and retrieve Workday tools
  • Build a LangChain agent that can interact with Workday
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
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

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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 your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Workday functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Workday tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['workday']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Workday tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Workday tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "workday-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Workday MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Workday tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Workday related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['workday']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "workday-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Workday related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Workday through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
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.

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. LangChain 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