Watch and act
Agents that run without you and change something
An agent does not have to wait for you to type. It can wake up on a schedule, react to an incoming email, respond to an event in your instance, or be called by another system — and then do something about what it finds.
What can wake an agent up
| Trigger | Typical use |
|---|---|
| Schedule | Every morning at 07:00, every Monday, first of the month. |
| Incoming email | An agent follows a mailbox and reacts to what arrives. |
| Event in your instance | A document changes state, a record is created. |
| Webhook | Another system calls Operator when something happens there. |
| Always-ON | A Digital Entity wakes itself when something needs attention — including when an expected reply never arrives. |
See Automations for the mechanics and Activation for setting triggers on an agent.
What an agent may change
Records in your instance
Requires a connected instance · Destructive — Create, update and delete records: customers, orders, products, and any other entity. Deleting and other destructive operations pause for your confirmation before they run.
Documents
Requires a connected instance — Search document types, change document states, void documents, produce printouts, and manage the enterprise company context a document operation runs in.
Files and attachments
Requires a connected instance — List, retrieve and attach files to any ERP.net object, and organise objects in folders.
Calendar
Requires a connected instance — View, create, update and cancel appointments and meetings.
An agent can send and reply to email. Every message an AI agent sends identifies itself as AI — see AI Disclosure in Email.
Watching the instance itself
Requires a connected instance — Agents can monitor performance metrics, active sessions, system messages, running procedures and configuration parameters, and read license keys, subscription plans and subscription status. This is what makes an unattended "watch my system overnight" agent possible.
Internal — Employees additionally get customer subscription lookups by UIN or name, and hosting infrastructure queries across instances, app servers and database servers.
Staying in control
- Destructive actions wait for approval unless you explicitly allow them.
- Permission policies limit what an agent may read and change, per instance, independently of ERP.net rights.
- Every unattended run is recorded — you can open it and see exactly what the agent did and why.
What it takes
| You want | You need |
|---|---|
| An agent that runs on a schedule | An agent with an activation trigger, Power User or above |
| An agent that reads your mailbox | A connected mailbox on the agent |
| An agent that changes ERP data | A connected instance and the matching permissions |