04 · ACT
AI Workflow Automation
Flow Engine
Orchestrating triggers, models, knowledge, tools, approvals and business systems into a process that keeps running.
What this is
The difficulty in automation is not making it run once but keeping it running: how exceptions are handled, how failures retry, who approves, and whether a bad run can be rolled back. Flow Engine writes those into the process definition from day one.
The problem
Script-style automation tends to stop dead at the first exception and offers no approval or audit path; fully manual process is limited by speed and consistency. What organisations need sits between the two: automatic where it can be, interruptible by a person, and traceable end to end.
Core capabilities
- 01
Triggers and orchestration
Started by event, schedule or a person, chaining model, knowledge and tool nodes.
- 02
Approval steps
Critical steps pause and wait for a person to confirm.
- 03
Exceptions and retries
Failure paths, retry policy and human fallback are defined, rather than simply halting.
- 04
Cross-system coordination
Moves and transforms data across multiple business systems while holding consistency.
- 05
Execution log
The input, decision and output of every run can be reviewed afterwards.
How it works
- 01
Trigger
An event, schedule or person starts the run.
- 02
Interpret
The model reads the input and plans the steps required.
- 03
Retrieve
Gathers context from the knowledge base and business systems.
- 04
Approve
High-risk actions stop at a human confirmation point.
- 05
Execute
Calls tools and writes to systems, logging throughout.
- 06
Feed back
Results and exceptions return to refine the process.
Where it sits across the capability domains
- 01 · SENSESense & InteractNot directly involved
- 02 · UNDERSTANDKnowledge & JudgementNot directly involved
- 03 · CREATEContent & GenerationNot directly involved
- 04 · ACTAutomation & ExecutionPrimary domain
- 05 · ORCHESTRATEEnterprise OrchestrationAlso touches
Use cases
- 01
Documents and approvals
Parses documents, validates fields and advances the approval chain.
- 02
Cross-system sync
Keeps order, inventory and finance systems consistent.
- 03
Customer follow-up
Advances follow-up by rule and escalates to a person on exception.
Enterprise system connections
- OA / approval systems
- ERP and order systems
- CRM
- Finance and invoicing
- Messaging and notification channels
Data, permission and deployment
Each node declares the permissions it needs and cannot act beyond that declaration. Every write is logged and traceable, and high-risk nodes require human confirmation. Private deployment is supported.
What is open today
In private preview for invited organisations, where process scope and data boundary are defined together. There is no self-service sign-up.
Apply for access
Want to know what this does in your own context?
Tell us the scenario and the systems already in place. We will start by judging whether it is worth doing at all, then talk about how.
Open to invited customers only; scenarios and data scope are defined together.