Flows And Automation
11 articles
What a flow is: a multi-step DAG of agent and integration steps
A flow is a multi-step DAG where each step is either a specialist role sub-agent or a connected MCP integration, run in dependency order with outputs fed forward.
Three ways to create a flow: form, 'Make it for me', and the node editor
Create a flow three ways: a quick form (name + trigger), 'Make it for me' where Camelia designs it from a description, or the visual node editor for hand-drawn graphs.
Building a flow visually with the node editor palette
The node editor's n8n-style palette lets you draw a flow as a graph; agent nodes become role steps, MCP-tool nodes become integration steps, and edges become dependencies.
Choosing a trigger: Manual, Schedule, or Webhook
A flow's trigger is Manual, Schedule (specific time or recurring interval), or Webhook (a generated URL). Manual streaming runs are the reliable path today.
Running a flow and watching live step-by-step progress
Running a flow streams live, step-by-step progress in dependency order; steps save labeled artifacts and the completed run is recorded in the project's Flows folder.
Reading run history and expanding a run to per-step outputs
The Runs table reads persisted run records newest-first with running flows pinned on top; expand any run to see per-step outputs and the labeled artifacts it saved.
How flow steps save labeled artifacts into your project folders
Flow steps save encrypted, smart-labeled artifacts into your project folders — Research/Analysis/Design/Spec/Legal/Manufacturing for role steps, Integration for MCP steps.
The built-in flow templates and what each one does
Built-in runnable flow templates include how-to-begin, design-and-manufacture (flagship 5-step), expand-idea, find-competitors, feasibility, business-model, and generate-design.
Understanding the flow runner's step cap and dependency order
The flow runner is a flat DAG capped at 16 steps (extras skipped), executes in dependency order feeding outputs forward, and stops cleanly on unmet dependencies or cycles.
Adding an MCP integration step to a flow
An MCP step runs a connected Composio tool by slug inside a flow; connect the integration first, and write actions raise an approval gate before they run.
How node-editor agent nodes map to the six real roles
Node-editor agent nodes map to exactly six real roles — research, reasoning, design, document, patent, manufacturing; cosmetic palette labels resolve to these under the hood.