Once the basic flows run in Voltrus, the next gain comes from letting the system do the repetitive parts: sending the reorder list every morning, drafting a purchase order when stock runs thin, telling the maintenance team's other tool that a job is overdue. This article covers the five tools for that: automations, scheduled reports, custom fields, webhooks, and AI agents. All of them work inside the same rules as people: they are audited, and anything risky can be routed through approval.
Automations: when this happens, do that
An automation is a rule with a trigger, optional conditions and an action. You build them on Automations.
| Part | Options |
|---|---|
| Trigger | Record created, record changed, status transition, system event (for example stock below reorder point, maintenance overdue), daily schedule |
| Condition | Compare any field: equals, not equals, greater or less than, in a list, contains, exists |
| Action | Update record fields, create record, run status transition, create governed proposal, emit webhook event |
Three ready-made recipes show the pattern:
- Auto-draft PO when stock runs thin: when stock drops below the reorder point, raise a draft purchase-order proposal for approval.
- Escalate overdue maintenance: when maintenance goes overdue, emit an event to external systems.
- Default reorder point for new items: fill in a reorder point when an item is created without one.
Every run is logged as ok, skipped or error, and appears in the audit timeline as automation:<name>. An automation that triggers another one is cut off after two levels, so a badly written rule cannot loop forever.
Good first automations
- When a purchase order changes status to approved, emit a webhook event so your team chat hears about it.
- When an item falls below its reorder point, draft a PO proposal (the recipe above).
- When a new customer is created without payment terms, set them to your standard terms.
- Every day, emit an event for maintenance that is overdue, so it reaches the team's chat through a webhook.
Scheduled reports
Report delivery emails a report on a schedule, daily or weekly, to up to ten addresses, as an HTML table with a CSV attachment. The available reports are:
| Report | Who reads it |
|---|---|
| MRP buy list | Purchasing, every morning |
| Maintenance due | Maintenance supervisor |
| Stock below reorder point | Warehouse and purchasing |
| Finance journal (month-to-date) | Finance, or your external accountant |
Report schedules need an admin to set up. Run now sends one immediately, which is useful to check the recipients before relying on the schedule.
For everything else, every list in Voltrus exports to CSV or Excel with the filters and columns you have on screen, and the Finance page exports the financial statements. Most "reports" a spreadsheet company builds by hand are simply a filtered list.
Custom fields
Every company tracks a few things the standard record does not have: a customer's sales region, an item's colour, a PO's internal project code. Custom fields add them to records without any change to the system. Types are text, number, date, yes/no and choice (a fixed list of values).
Custom fields appear in the record drawer alongside the standard fields. A field's key, type and record type cannot change after it is created, so pick them carefully. Stock movements cannot carry custom fields: the stock ledger is kept lean on purpose.
Webhooks: telling other systems
A webhook sends a message to another system's URL when something happens in Voltrus: a proposal decided, stock below reorder, a record changed, maintenance overdue or escalated, a work order released. You register endpoints on Webhooks, choose the events, and send a test.
Each message is signed (HMAC-SHA256 in the X-Voltrus-Signature header, with a timestamp) so the receiver can verify it came from Voltrus. Failed deliveries retry after 5 minutes, 30 minutes, 2 hours and 24 hours; the delivery log shows each attempt. The same mechanism drives the bridge to a manufacturing execution system (MES): releasing a work order sends it to the shop floor, and the MES reports completion back.
AI agents
Voltrus is built so that AI agents can work in it as safely as people. An agent connects through MCP (Model Context Protocol) with an agent token issued on Users & tokens or from Onboarding. It can read and search the company's records, and every change it wants to make becomes a proposal with its reasoning attached. A person approves or rejects it.
What this is good for, in practice:
- "Draft purchase orders for everything on today's MRP buy list, grouped by supplier."
- "Find customers with invoices more than 60 days overdue and add a follow-up activity on each."
- "Fill in the missing NPWP numbers on these suppliers from this list."
Admins can let specific low-risk operations run without approval in Settings → Access & integrations → What agents may do without asking. Those runs are still audited with the agent and model that made them.
Separately from agents, Voltrus runs recommendations every night with fixed rules, not a language model: shortages, work orders at risk of delay, reorder points that look too low, and deviations. They appear on Recommendations; acting on one creates a proposal like any other.
Checklist
- Set up the morning MRP buy list and the stock-below-reorder report for purchasing.
- Turn on the auto-draft PO recipe once reorder points are reliable.
- Add at most three custom fields in the first month, each with a clear owner.
- Connect one AI agent with its own agent token and review its proposals for two weeks before letting any operation run without asking.