The software decides how you work
Every business has a rule that no template covers: a customer who needs a second approval, a product that ships from one site only. The team keeps that rule in their heads, because the system has no place for it.
WORKFLOW AUTOMATION
Miridia is the supply chain automation platform with a workflow builder inside it. Describe a rule in plain English, such as "alert me when my margin on any product drops below 40%", and Miridia Flows drafts the workflow on a canvas that you can review, test and switch on.
WHAT GOES WRONG
Every business has a rule that no template covers: a customer who needs a second approval, a product that ships from one site only. The team keeps that rule in their heads, because the system has no place for it.
Somebody opens a report every day to look for the low margin, the unpaid order or the late receipt. The check takes 20 minutes, and it stops on the day that person is on leave.
An outside automation tool can read an order, but it does not know your stock, your suppliers or your approvals. Each workflow starts with a week of connecting data.
A rule ran overnight and changed 40 orders. Without a record of each step and its data, the team cannot tell which condition fired, and they switch the workflow off.
WHAT STARTS A WORKFLOW
A workflow starts when something happens in Miridia, at a time that you set, or when another system calls it.
A team that already runs n8n, Power Automate or Zapier connects it to the same Miridia events through the API.
HOW IT RUNS
Type the rule in plain English. Miridia drafts the whole workflow: the schedule, the data that it reads, the filter, and the alert or the action at the end.
Triggers, conditions and actions are nodes that you connect. Change any step, or build the workflow yourself from the building blocks.
Run the whole workflow, or one step at a time, on pinned sample data. Each node shows the data that it received and the data that it produced.
The workflow runs on its trigger. One dashboard shows every workflow, with the status and the data of each run, and each change is a new version.
THE PLATFORM
Miridia drafts the workflow from one sentence. For the margin rule, it sets a daily schedule, reads the price and the cost of each product, filters for margins below 40%, and sends an alert that lists those products.
After a run, each connection shows how many records passed through it. You see where the 200 orders became 12, and why.
If, Filter, Switch, Merge, Split Out, Limit, Edit Fields, Code in JavaScript, and HTTP Request. The Miridia API block reads and writes your orders, stock, products and suppliers.
Purchase order approvals, low stock alerts, order intake from a webhook, and AI-enabled workflows such as reading the line items from a purchase order that a customer emailed.
Each change to a workflow is a new version, with an audit trail of who changed what.
Build the workflow yourself, or ask the Miridia team to build it with you as part of the consulting work.
HONEST FIT
QUESTIONS
No. Describe the rule in plain English and Miridia drafts the workflow, or connect the nodes yourself on the canvas. A Code block in JavaScript is there for a step that needs it.
A Miridia event, such as an order that is created, a stock change or a delivered shipment. A schedule or a webhook from another system can also start one.
Yes. Run the whole workflow, or one step at a time, on pinned sample data before you switch it on.
Both. The Miridia API block reads and writes your orders, stock, products and suppliers, and the HTTP Request block calls another system.
Yes. Connect the engine that you already run to the same Miridia events through the API.
MAKE. MOVE. MEASURE.
Tell us the check that your team does by hand. We build it as a workflow in a demo account and show you each step and its data.