Notion Custom Agents can delegate work to sub-agents
TL;DR
Notion 3.7, released September 15, 2026, lets a Custom Agent call other Custom Agents as sub-agents. Each can have its own instructions, context, access, and model, while the primary agent uses their responses to finish the task.
- Status
- Live
- Released
- Plans
- Not specified
- Source
- Notion 3.7 release notes
What changed
A Custom Agent can hand part of a task to another Custom Agent and use the result in its own work. Notion announced this alongside Agent Skills in Notion 3.7.
The primary agent chooses when to delegate. Sub-agents can have different models and access, so a focused reporting agent can work separately from an agent handling customer feedback.
Why it matters
Delegation gives a team a way to separate responsibilities inside a recurring workflow. A useful starting design is one agent that gathers evidence, one that checks it, and a primary agent that prepares the result for review.
That is a workflow recommendation, not a guarantee of better output. Give each agent a clear job and define what it must return before adding more handoffs.
What to set up first
Add the agents the primary agent can call in its Tools and access settings. Write down when each should be called and what a complete response contains. Test a small workflow before expanding it.
Frequently asked questions
Can a sub-agent use a different model?
Yes. Notion supports a separate model for each Custom Agent in the workflow.
Does delegation give every agent the same access?
No. Each agent has its own access configuration. Check the resources each needs instead of assuming a handoff transfers permissions.
Who finishes the original request?
The primary agent uses the sub-agents' responses to finish the original work.