Unit4
Connect AI agents and workflows to Unit4 ERP: suppliers, customers, projects, timesheets, expenses, purchase orders, supplier invoices and journals.
Book a demoUnit4 for AI agents and workflows.
engini lets your AI agents and workflows work in Unit4 ERP, built for professional services, public sector, nonprofits and universities: read suppliers, customers, projects and general ledger transactions, enter timesheets, expenses and supplier invoices, raise purchase orders, post journals, and start a workflow when records change. People-centric organizations keep Unit4 and the systems around it 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 Unit4. Every tool is one you allow or leave out.
The Unit4 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 business partners and their terms.
Read projects, budgets and actuals.
Read time and expenses by person and project.
Read the ledger by period and dimension.
Write
Enter time and expenses.
Order and enter invoices for payment.
Post a general ledger journal with dimensions.
Keep master data current.
Any endpoint
Call any Unit4 ERP API, with the sign-in added for you.
Triggers
Projects, timesheets, invoices or suppliers added or 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 Unit4. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Unit4 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 Unit4 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 Unit4 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 Unit4 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 Unit4 through engini
{
"mcpServers": {
"engini-unit4": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Unit4 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 Unit4 tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Unit4. Agents and workflows, across systems.
Projects that start from the win
A deal won in Salesforce creates the Unit4 project with its budget and manager.
Supplier invoices from the inbox
A supplier invoice from email is read by an agent, matched to the purchase order and entered in Unit4.
People and payroll in step
New hires and payroll from Workday or ADP flow into Unit4 as resources and journals.
Project and budget answers
An agent in Teams answers project, budget and spend questions from Unit4. 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 Unit4 and another system engini connects is available.
You decide what each agent may do in Unit4. engini enforces it on every call.
Only the tools you allow
A toolset lists the Unit4 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 Unit4 account and engini acts as that person, with their Unit4 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 Unit4 in three steps. Then decide what each agent may do.
Sign in to Unit4
In Unit4 Identity Services, register engini as a client and give its user a role with only what the workflows need, then add a Unit4 connection with your tenant and the client.
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 Unit4 from Claude, ChatGPT, Cursor or your own code.
Unit4 and engini. Straight answers.
Can an AI agent write to Unit4, or only read?
Both. engini has tools to enter timesheets, expenses, purchase orders and supplier invoices, post journals, and create and update suppliers and projects. 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 Unit4?
It acts as the Unit4 user behind the connection, with that user's role. Every run is recorded under the person who started it.
Can a change in Unit4 start work?
Yes. Scheduled triggers check Unit4 for new or changed projects, timesheets, invoices and suppliers. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Unit4 API endpoint through the same connection, and give it only to the agents that need it.