Processes that run themselves
What you repeat every month, defined once and done by itself.
- A canvas, no code
- Four ways to start
- Actions on any module
-
Trigger
Overdue invoice
event · time · another app · manual -
Condition
More than 15 days?
on Finance data - Paths Amount?
- Person Waits for approval
- Action Payment reminder
- End No action
-
Action
Task in the CRM
same as your AI -
History
Every step recorded
inputs and outputs
What changes in your day-to-day.
Today
- Every month someone repeats the same steps between programs by hand.
- If something fails, nobody knows which step it stopped at.
- Approvals get lost in email.
With iERP
- You define it once on a canvas and it runs by itself.
- Each run records what it did, step by step, with its result.
- The flow stops where a person has to decide and carries on once they do.
A canvas, no code.
You drag in the trigger, chain conditions and actions and mark where a person has to decide: the flow stops, waits for the approval and carries on where it left off.
A history of every run.
Each run stores what triggered it, how long it took and the result of every step with its inputs and outputs. Secrets are masked.
- Trigger · overdue invoice ✓ 0.2 s
- Condition · more than 15 days ✓ Yes
- Action · task in the CRM ✓ Created
- Approval · collections desk ! Waiting for a person
- Action · payment reminder Pending
Sample data
What Automation does
Five pieces to turn a process that lives in someone’s head into something that runs on its own and leaves a trail.
-
01
Four ways to start
Something that happens in the ERP itself, a time or a recurrence, a signal from another app, or a person launching it by hand when they need to.
-
02
Actions on any module
A step can issue an invoice, open a ticket, move a deal or onboard someone: they are the same tools the assistant uses, on the same data.
-
03
Steps where a person decides
The flow stops, waits for the approval or the answer it is missing and carries on from where it was with whatever it was told.
Without opening iERP
36 Automation actions are available to your own Claude or ChatGPT. Ask for what you would do by hand and get on with your day: it acts with your permissions; depending on its app, it asks for your permission before changing anything, and everything lands in the audit log.
- «Show me the runs that failed this week and which step they stopped at.»
- «Pause the payment reminder flow until Monday.»
Your assistant · connected to iERP
On the 1st of each month, prepare the recurring invoices and warn me before issuing them.
- → draft saved
I have laid it out for you: a trigger on the 1st, a step preparing the recurring invoices in Finance and a stop waiting for your approval before anything is issued. Review it on the canvas and activate it.
Sample data
€15 a month. Plus your users.
Every user costs the same, whatever they use. Prices exclude VAT. With 3 modules or more, 10% off modules. With 5 modules or more, 20% off modules.
Automation does not work alone
Automation is worth exactly what the modules you have active are worth: the more of them, the more it can chain into a single flow, without leaving the workspace database and with no connectors to maintain.
Industries where it fits
Questions about Automation
Do I need to know how to code?
No. Flows are built by dragging blocks onto a canvas: you pick the trigger, chain conditions and actions and mark where a person has to decide. There is no code to maintain.
What can start a flow?
Four things: something that happens in the ERP itself, a time or a recurrence, a signal from another app, or a person launching it by hand. You choose when you create the flow.
What if a flow gets it wrong?
Every run is recorded step by step, with its input, its output and the error if there was one. And steps touching money or people can be marked to stop and wait for approval.
Shall we try it with your data? Half an hour, no strings attached.
We'll show you the module with your real processes and how your own assistant would use it. Or create your account and turn it on today.