A canvas, no code
You drag in the trigger, chain conditions, loops and actions, and save. Every save leaves a version of the flow you can go back to.
In production
Agentic module
Automation
What you repeat by hand every month: define it once on a canvas and let it run itself, stopping wherever someone has to decide.
Automation is the flow engine of iERP: a canvas chaining a trigger, conditions, actions on any contracted module and steps that wait for a person. It is not an integration between separate apps; the steps operate on the same workspace database, with the permissions of whoever launched the flow, and every run is recorded step by step.
What it does
What Automation does
Six pieces that turn a process living in someone's head into something that runs itself and leaves a trail.
Four ways to start
A business event from the ERP itself, a time or a recurrence, an external call over webhook, or a person launching it by hand when they need to.
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.
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.
Voice agents
A voice agent is a bot of this very module: it answers or calls, follows the flow's script and acts with the permissions of the person it stands for. Each call is one more run.
A history of every run
Every run stores what triggered it, how long it took and the outcome of each step with its inputs and outputs, and secrets come out masked.
How the AI runs it
How the AI runs it
Describe the process the way you would to a colleague and the agent leaves it laid out on the canvas for you to review.
The agent proposes and waits for your confirmation before writing, and the flow is born as a draft: activating it stays with you. After that, every run is recorded step by step.
379 published actions an agent can execute in iERP.
On the 1st of each month, prepare the recurring invoices and warn me before issuing them.
automatizacion.crear_flujo 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.
- Show me the runs that failed this week and which step they stopped at.
- Pause the payment reminder flow until Monday.
Works with
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.
AI
In production
Ask-AI, voice, MCP tools, traceability and cost per conversation.
View module
Finance
In production
Invoicing with your own series, partial payments, treasury forecasting and a chained invoice register.
View module
Human resources
In production
Headcount, contracts, absences, clock-in, recruitment, development and the employee portal.
View module
Questions about Automation
What people ask before deciding.
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 would you automate first?
Half an hour, your most repetitive process, no strings attached.
Available in: Professional