UKG
Connect AI agents and workflows to UKG Pro and UKG Workforce Management: employees, pay statements, timecards, schedules and time-off balances.
Book a demoUKG for AI agents and workflows.
engini lets your AI agents and workflows work in UKG Pro and UKG Pro Workforce Management: read employees, jobs and pay statements, read timecards, schedules and accrual balances, request time off, update employee details, and start a workflow when someone is hired, changes jobs or leaves. Payroll, time and the rest of the business stay in step. 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 UKG. Every tool is one you allow or leave out.
The UKG 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
Read people with their job, pay group, manager and location.
Read what was paid, by pay period.
Read hours worked and shifts planned.
Read time-off balances by type.
Write
Request time off for an employee.
Change an address, phone or emergency contact.
Record a punch or change a shift in Workforce Management.
Any endpoint
Call any UKG Pro or Workforce Management API, with the sign-in added for you.
Triggers
UKG sends the event, or a scheduled check finds it.
A payroll was closed and statements are ready.
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 UKG. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your UKG 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 UKG 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 UKG 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 UKG 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 UKG through engini
{
"mcpServers": {
"engini-ukg": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your UKG 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 UKG tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on UKG. Agents and workflows, across systems.
Payroll in the general ledger
When a payroll closes, earnings and deductions post as a journal entry in NetSuite or Sage Intacct, split by department.
Joiners and leavers handled
A hire or termination in UKG creates or closes accounts in Okta or Entra ID and opens equipment requests in ServiceNow.
Labor against the plan
Hours from timecards land in Snowflake or Power BI next to sales and production, so managers see labor cost by site.
Answers without a ticket
An agent in Teams answers balances, schedules and pay-date questions from UKG. 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 UKG and another system engini connects is available.
You decide what each agent may do in UKG. engini enforces it on every call.
Only the tools you allow
A toolset lists the UKG 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 UKG account and engini acts as that person, with their UKG 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 UKG in three steps. Then decide what each agent may do.
Sign in to UKG
In UKG, create a web service account with only the permissions the workflows need and copy your API key, then add a UKG connection with your tenant address, the account and the key.
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 UKG from Claude, ChatGPT, Cursor or your own code.
UKG and engini. Straight answers.
Can an AI agent write to UKG, or only read?
Both. engini has tools to request time off, update employee details, add punches and change schedules. 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 UKG?
It acts as the UKG web service account behind the connection, with that account's permissions. Every run is recorded under the person who started it.
Can a change in UKG start work?
Yes. Hires, job changes and terminations start a workflow, and a scheduled trigger checks for new pay statements after each payroll. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any UKG API endpoint through the same connection, and give it only to the agents that need it.