Building a flow visually with the node editor palette
The visual node editor lets you build a flow by drawing a graph instead of filling in a form. Its palette is modeled on n8n's node library, so it groups nodes into familiar categories.
The palette groups
The palette offers Triggers, Logic, Data, I/O, an Agents group, and a Human-in-loop Approval gate. You drag nodes onto the canvas and connect them with edges to define the order of work.
How a drawn graph becomes a flow
When you compile the graph into a runnable flow, the editor maps your nodes onto real flow steps:
- Agent nodes become role sub-agent steps.
- Connected MCP-tool nodes become MCP integration steps that call a Composio tool by slug.
- Edges become
dependsOnrelationships between steps. - Trigger, output, and control nodes are structural — they shape the graph but are skipped at execution time.
Picking an agent role
When you configure an Agent node, the role dropdown offers exactly the six real roles: research, reasoning, design, document, patent, and manufacturing. Some cosmetic labels in the palette (for example a "PCB Engineer" or "Validation" tile) are display conveniences that map onto these real roles under the hood — they are not separate agents.
Tips
Because a flow is a DAG, draw your dependencies forward — earlier steps feed their output to the ones they connect to. Add a Human-in-loop Approval gate where you want a person to review before the flow continues. Once compiled, the flow runs the same way as any other flow you create.