What a flow is: a multi-step DAG of agent and integration steps
A flow is HIIE's automation layer — the "Workflow-as-a-Service" part of the platform. It's a multi-step directed acyclic graph (DAG) where each step is run in dependency order, and the output of earlier steps is fed forward as context to later ones.
What a step can be
Every step in a flow is one of two kinds:
- A role sub-agent step (the default): runs one of the six specialist roles — research, reasoning, design, document, patent, or manufacturing — exactly the same way Camelia delegates work via a sub-agent. Research and reasoning steps use live web access.
- An MCP tool step: calls a connected Composio integration by its tool slug, letting a flow read from or write to an external service.
How steps connect
Steps declare dependencies on earlier steps. The runner resolves those dependencies, executes in order, and passes each step its dependencies' outputs as context. Because it's a DAG, there are no loops — work flows forward from triggers to outputs.
Where the work goes
Each step can save an artifact, encrypted, into one of your project folders with a smart label. Every step also logs an Agent-to-Agent (A2A) envelope, so an entire run shows up as a single conversation in the node graphs. When a flow finishes, one run record is persisted into the project's Flows folder.
Why use a flow
Where Camelia chat is conversational, a flow is repeatable structure: define the steps once, then trigger it whenever you need that sequence of research, analysis, design, and integration work to run end to end.