Try it
Click any node to open it. On a phone, drag the canvas sideways.
Four nodes, three wires, one direction. The wire doesn't just say "go next" — it hands over the data.
Six things to click through — ports, sub-nodes, expressions and the wiring that turns one n8n canvas into a manager and two specialists. Everything here recalculates live.
Read it left to right. Every box is a node that does one job, and every wire carries actual data to the next one. The first box is special: it's the trigger, and without it nothing ever starts.
Click any node to open it. On a phone, drag the canvas sideways.
An AI Agent node has the usual input on the left and output on the right — plus a row of ports underneath. The Chat Model port is required; Memory and Tool are not. Flip the switches and watch what the same agent can and can't do. Anything hanging off those bottom ports is a sub-node.
An agent's system prompt is its job description, typed into the node. Drag the slider and keep adding jobs to a single agent — then watch what a specialist agent would have done instead.
Attach an agent to another agent's Tool port and the parent stops treating it as a chat partner — it calls it like a function. What decides whether it gets called at all is the tool description. Pick one and run "Analyze Infosys".
Data travels as a list of items — each one a JSON object. A node runs once per item, and an expression is how the next node reaches into it. Click along the line and inspect what's really there.
Click a node to inspect the item arriving at it.
The Code node turns the agent's plain text into styled HTML and returns it as items. Then Gmail has one setting that ruins everything — Message Type. Flip the three switches and watch the inbox.
Educational build. Everything shown here is workflow engineering, not financial advice.