Workday Adaptive Planning
Connect AI agents and workflows to Workday Adaptive Planning: load actuals, export plans and versions, and read levels, accounts and dimensions.
Book a demo
Workday Adaptive Planning for AI agents and workflows.
engini lets your AI agents and workflows work in Workday Adaptive Planning: load actuals from the ERP into standard and cube sheets, export plan and forecast data by version, read levels, accounts and dimensions, and start a workflow when new data is ready. Budgets and forecasts stay current without spreadsheets in between. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
What your agent can do in Workday Adaptive Planning. Every tool is one you allow or leave out.
The Workday Adaptive Planning tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Export plan, forecast or actuals data by version, account and level.
Read versions and the organization structure.
Read the chart of accounts and dimension values.
Write
Load actuals into a standard sheet.
Load data into a cube sheet.
Add or change dimension values.
Any endpoint
Call any Adaptive Planning API method, with the sign-in added for you.
Triggers
A plan or forecast version changed.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Workday Adaptive Planning. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Workday Adaptive Planning connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Workday Adaptive Planning tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Workday Adaptive Planning and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Workday Adaptive Planning tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Workday Adaptive Planning through engini
{
"mcpServers": {
"engini-workday-adaptive-planning": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Workday Adaptive Planning connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Workday Adaptive Planning tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Workday Adaptive Planning. Agents and workflows, across systems.
Actuals every night
Actuals from NetSuite, Sage Intacct or Workday Financial Management load into Adaptive every night.
Headcount in the plan
Employees and open roles from Workday or Greenhouse reach the workforce plan.
Budget against actuals
Budgets exported from Adaptive land in Snowflake or Power BI next to actuals.
Plan questions answered
An agent in Claude answers budget, forecast and variance questions. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Workday Adaptive Planning and another system engini connects is available.
You decide what each agent may do in Workday Adaptive Planning. engini enforces it on every call.
Only the tools you allow
A toolset lists the Workday Adaptive Planning tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Workday Adaptive Planning account and engini acts as that person, with their Workday Adaptive Planning permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Workday Adaptive Planning in three steps. Then decide what each agent may do.
Sign in to Workday Adaptive Planning
Create an Adaptive Planning user for the API with access only to the levels and sheets the workflows need, then add an Adaptive Planning connection with your instance and that user.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Workday Adaptive Planning from Claude, ChatGPT, Cursor or your own code.
Workday Adaptive Planning and engini. Straight answers.
Can an AI agent write to Workday Adaptive Planning, or only read?
Both. engini has tools to import standard and cube data and update dimension values. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in Workday Adaptive Planning?
It acts as the Adaptive Planning user behind the connection, with that user's level access. Every run is recorded under the person who started it.
Can a change in Workday Adaptive Planning start work?
Yes. A scheduled trigger checks for plan and forecast versions that changed. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Workday Adaptive Planning API endpoint through the same connection, and give it only to the agents that need it.