How Notion built a Custom Agent workflow to keep Academy content current

Summary

Notion built a Custom Agent workflow in Notion to keep Academy content current as product changes ship. The system uses two databases: an Academy library mapping the curriculum and a maintenance-tasks database tracking work from each product change. Two Custom Agents handle the work: the Academy Drift Agent compares launch docs against the library and flags affected lessons, while the Academy Drafting Agent drafts approved updates using editorial guidance. MCP connects the workflow to Parta, the e-learning platform, so approved content moves into final QA without manual hand-off. The loop includes human review checkpoints before scope approval and before content moves into Parta, reducing content drift and giving the team hours back each week.

Takeaways

1. 1

   Content drift is the gap between a changing product and the content that explains it; Notion Academy organizes lessons around learner goals, so a single product change can affect multiple lessons in different ways.

2. 2

   The workflow uses two Custom Agents: the Academy Drift Agent identifies affected lessons and creates scoped tasks, while the Academy Drafting Agent drafts approved updates using editorial guidance and stages them for publishing.

3. 3

   Human review is built in at two checkpoints—before scope approval and before final copy moves into Parta—so mistakes are caught where they would be hardest to undo.

FAQ