Connected through your ERP's API
AI Employees for Dynamics 365, Epicor and other ERPs
If your ERP publishes an OpenAPI specification, we can build AI Employees on it. We generate the connection from the specification, keep only the operations the job needs and test each one with your team. Microsoft Dynamics 365 and Epicor are examples of ERPs we scope this way.
Contact usCustom pricing, scoped with your team.
How the connection works
We start from your ERP's OpenAPI specification
An OpenAPI specification describes what an ERP's API can read and change. Where your ERP publishes one, we generate the connection from it instead of writing it by hand.
We keep only what the job needs
An ERP API exposes hundreds of operations. An AI Employee is given the few its role requires, and you decide which of them need approval.
We roll out with approvals
Reading first, then actions held for approval, then a wider scope when the results earn it.
What an AI Employee can do here
- Read the customers, items, orders and invoices the API exposes
- Create or update records where the API allows it and you approve it
- Answer questions from live ERP records instead of exports
- Run on a schedule and report what needs a decision
Examples. The records and actions for your AI Employees are agreed during scoping.
What we need from you
- The OpenAPI specification or API documentation for your ERP version
- An administrator who can issue API credentials with the right scope
- A process owner and a set of real cases to test against
Questions
Which ERPs can be connected this way?
Any ERP that publishes an OpenAPI specification for its API is a candidate, including Microsoft Dynamics 365 and Epicor. What is possible depends on your version, your edition and the operations its API exposes, so we confirm feasibility during scoping, before we quote.
What is an OpenAPI specification?
It is a machine-readable description of an API: which records it can read or change and what each call needs. Because it is machine-readable, we can generate the tools an AI Employee uses from it instead of building each one by hand.
What if our ERP has no OpenAPI specification?
Then we look at what it does offer: a REST API without a specification, an MCP server, or a workflow that reaches the system another way. If none of those is a sound basis, we tell you plainly.
Is this a connector we can switch on ourselves?
No. The connection is delivered by our team as part of an engagement. We set it up, scope it to your process and test it with you.
How is it priced?
Pricing is custom. For this ERP the quote includes building and testing the connection as well as the AI Employees themselves.
Start with one process your team knows well
Tell us where work slows down, which records the team uses and who signs off. We will scope a custom AI Employee around it.
Contact us