Routine work prepared for you, approved by your people.
Build automations as When, Only if, Then on a canvas. They notify, generate reports and prepare proposals; anything that would change the records still waits for a person to approve it.
The problem
The same steps come back every week: chase the certificate, build the pack, tell the ERP.
Copy, paste, repeat
Routine steps take hours and depend on who is in the office.
Scripts nobody can read
Integrations written as code hide what they change and when.
Speed without approval
A tool that changes records on its own skips the approval that makes a record worth trusting.
What it does
An automation starts from an event, checks its conditions and prepares the next step. A person approves what changes the records.
When
A message from another system, a lot registered or delivered, a certificate about to expire, a new finding, a recall notice, a number crossing a value, or a schedule.
Only if
Conditions such as the product or the receiver's country, with branches, a step for each lot and calculated values.
Then
Notify, e-mail members, generate a report, send a message to another system, or prepare a proposal.
Reviews and approvals
A review step pauses the run for a person; anything that changes the records is a proposal someone approves.
Your ERP, both ways
An inbound endpoint receives the ERP's messages in its own format; signed webhooks send events back.
- Read the full module
How it works
From a template to a run you can read step by step.
Start from a template
A certificate expiry alert, an EUDR pack on each delivery, holding lots whose certificate was withdrawn, a weekly report.
Test it
In a test run the conditions are evaluated for real and the actions are only simulated.
Switch it on
An owner or administrator reads a summary of what it will do, then turns it on.
Read every run
Each run lists why each step ran or was skipped. Owners and administrators can halt all automations at once.
Who uses it
Automations are drafted by the people who do the work and switched on by the people who answer for it.
Operator
Drafts and tests automations.
Administrator
Connects the ERP and switches automations on.
Owner
Switches automations on, and can halt them all at once.
Approver
Approves the proposals they prepare.
Related features
- Lot rulesChecked before anything moves: allowed receivers, required certificates, expiry.
- Humboldt, the AI analystExplains findings in business words and suggests next steps. People decide.
- Custom agentsYour own agent for one recurring job, briefed like a new colleague. In design.In design
- Reports and the audit packDashboards, reports and a signed audit pack anyone can verify without an account.
Hand the routine to an automation. Keep the approvals.
Tell us which steps your team repeats. We will build them as automations in a sandbox.