ERP.net with AI Agents
What ERP.net access adds to agents and Digital Entities
Agents in Operator are useful without ERP.net. With an ERP.net instance connected, they stop being assistants that talk about your business and become assistants that work in it.
Built-in agents that use ERP.net
Several built-in agents are ERP.net-aware out of the box — they discover the model, run queries, and (where allowed) make changes. You can use them as they are, or take them as the starting point for your own.
Giving your own agent ERP.net access
When you build an agent, ERP.net access is a set of capabilities you switch on:
| Capability area | What the agent can do |
|---|---|
| Data discovery | Search the entity model, inspect entities and their custom attributes |
| Data & records | Query data; create, update, and delete records |
| Documents | Change document state, void, printouts, enterprise context |
| Files | List, read, and attach files on ERP.net objects |
| Import / export | Bulk moves in and out of entities |
| Instance search | Hybrid search over products, companies, and document types |
Turn on only what the role needs. An agent for the sales team probably needs discovery, query, documents, and instance search — and nothing that deletes.
Writing instructions that work with ERP.net
- Name the entities you care about. "Work with
Crm.Sales.SalesOrdersandCrm.Sales.Customers" beats "work with orders." - Let the model discover, don't dictate field names. Your instance has custom fields; discovery finds them, hardcoded guesses go stale.
- Put shared truths in Entity Instructions, not in each agent. Naming conventions and status meanings belong to the entity, so every agent inherits them.
- State the boundaries. "Never change document state without asking" is a useful instruction even though destructive operations already pause.
Example agent — Order Desk Capabilities: discovery, query, create/update records, documents, instance search. Instructions: "You handle sales order questions and changes for the order desk. Always confirm the customer by searching the instance index before creating anything. Never void a document — escalate instead."
Digital Entities and ERP.net
Digital Entities are always-ON agents. Combined with ERP.net they can watch for things nobody asked about yet:
- Wake up periodically, check for orders stuck in a state past their date, and raise them with you.
- Remember that a particular customer's deliveries keep slipping, and mention it the next time that customer comes up.
- Keep a todo list of follow-ups that came out of ERP.net data, not out of your messages.
Because entities run on their own schedule, they use the same identity and the same permission layers as you do in chat — an entity cannot see data its owner cannot see.
Voice and phone
ERP.net-backed agents work over voice too. "What's the balance on account 4011 for Acme?" is a valid phone question when the agent has query capabilities. See Speech Setup.