Autonomous Work with ERP.net
Scheduled runs, incoming triggers, and always-ON monitoring
Everything an agent can do with ERP.net in a conversation, it can also do without you in the room. What differs is what starts the work.
What can start ERP.net work
| Trigger | Typical ERP.net use |
|---|---|
| Schedule | Every morning: list orders due today and mail the summary. Monthly: export a reconciliation. |
| Incoming webhook | Your ERP.net instance (or an integration around it) calls Operator when something happens, and an agent reacts. |
| A supplier confirmation arrives; the agent finds the matching purchase order and updates it. | |
| Digital Entity wakeup | The entity decides for itself whether anything in ERP.net needs attention right now. |
Schedules, webhooks, and mail triggers are configured per agent — see Automations, Schedules, Webhooks, and Events.
An honest note on ERP.net events
Operator does not subscribe to ERP.net's internal events out of the box. There is no "when a sales order is released, run this agent" switch that works with no setup.
Two supported ways to get close:
- Push — configure your ERP.net installation (or middleware around it) to call an Operator webhook when the event happens. The agent then runs with the payload you sent.
- Poll — give an agent or Digital Entity a schedule and let it query for the condition: documents released since the last run, orders past their promised date, stock below minimum.
Polling is simpler and needs nothing on the ERP.net side; pushing is immediate. Pick per use case.
Identity in autonomous runs
An unattended run still acts as a real ERP.net user — the owner of the connection the automation is bound to. The same permission layers apply: ERP.net security, Permission Policies, and the agent's capabilities.
Two consequences worth planning for:
- Sessions must stay valid. If the underlying connection expires and cannot be renewed silently, ERP.net steps of the run will fail until the owner reconnects.
- Nobody is there to confirm. Destructive operations wait for approval. In an unattended run, that means the work pauses instead of deleting something. Design automations around non-destructive operations, or accept that they will queue for a human.
Digital Entities on ERP.net
Digital Entities wake up periodically and decide what to do. Against ERP.net that is a natural monitoring loop:
- Check for exceptions — stuck documents, overdue deliveries, unusual values.
- Compare against what the entity remembers from previous checks, so it reports changes, not the same list every time.
- Add follow-ups to its todo list and raise the ones that matter with you.