One question.
A team of
AI agents.
One report in your inbox — built in n8n, with one Code node.
Nodes on a
canvas
A node does one job and hands its data to the next. Every run is an execution, and n8n saves all of them.
Exactly one
trigger
The Chat Trigger is where a workflow starts. It catches the question and hands it down the line.
The ports
underneath
Input left, output right — plus a row of sub-node ports below. That row is the whole trick.
Three ports.
One is required.
news + charts + verdict + emailone short job description eachOne prompt,
four jobs
A jack of all trades goes deep on none of them — and one bad line poisons the whole answer.
Promote one
to manager
The Orchestrator Agent delegates and merges. It never researches anything itself, and the two specialists never meet.
An agent can
be a tool
Hang a second agent off the Tool port and it stops being a chat partner. It becomes a function you call.
"Analysis tool.""Company fundamentals: news, results, sentiment."The description
does the calling
The orchestrator chooses tools by reading their descriptions. Write a fuzzy one and yours is ignored.
What to buy.
When to buy.
One specialist reads the business, the other reads the chart. The manager merges both into one summary.
The last
mile
The Code node styles the report; Gmail sends it. Set Message Type to HTML or tags arrive raw.
Build the line
first.
Trigger → agent → Code → Gmail. Get those four talking, then hang the sub-nodes underneath. Tomorrow: the system prompts that make the merge readable.