ERP.net Integration
Operator's deepest native business-platform integration
Operator.net is an independent agentic platform. It builds AI agents, Digital Entities, and apps, and it can connect to many systems — through MCP servers, webhooks, mail providers, and plain web requests.
ERP.net is different. It is the one business platform Operator integrates with natively: Operator understands the ERP.net data model, speaks its Domain API, respects its security, and ships ready-made tools for reading, writing, and moving business documents through their lifecycle. No connector to configure, no schema to describe, no field mapping to maintain.
This section explains what that native integration gives you, and where its limits are.
What "native" means here
| Generic integration (MCP, webhook, HTTP) | Native ERP.net integration |
|---|---|
| You describe the endpoints and payloads | Operator already knows the entity model and searches it semantically |
| Auth is configured per connector | You sign in to your ERP.net instance with your own account; Operator uses your identity |
| Tools are whatever the remote server exposes | Purpose-built tools: query, create, update, delete, documents, files, import/export |
| Permissions live in the remote system only | ERP.net security plus Operator-side Permission Policies |
| Apps must handle credentials themselves | Apps call the Domain API through Operator; the token never reaches the app |
What you can do with it
- Ask questions in plain language — "show me overdue sales orders for Acme this quarter" — and get answers grounded in live data, with links back into the ERP.net Web Client.
- Change data safely — create and update records, release or void documents, with confirmation prompts before anything destructive.
- Work with documents — move them through their state lifecycle, generate printouts, attach and read files.
- Build apps on your own data model — App Builder apps query the Domain API directly, with your ERP.net identity.
- Run work autonomously — schedules, webhooks, mail, and Digital Entity wakeups can all touch ERP.net data without you being present.
What it is not
- Operator does not replace or mirror ERP.net. There is no copy of your database; every read and write goes to your instance in real time.
- Operator is not ERP.net-only. Everything in the platform works without an ERP.net instance connected — you simply lose the tools described in this section.
- ERP.net does not push events into Operator out of the box. Autonomous work is Operator-initiated (schedules, wakeups) or driven by webhooks your instance calls. See Autonomous Work with ERP.net.
Read next
- How Operator Understands ERP.net — the model, discovery, and instance-specific context
- Working with Data and Business Objects — queries, writes, documents, files
- Security, Identity, and Permissions — who Operator acts as, and what limits it
- ERP.net with AI Agents
- ERP.net with Operator Apps
- Autonomous Work with ERP.net
- Technical Reference