Notion as Agent Infrastructure

This is Notion trying to turn its workspace into the place where a companys agents live, not just the place where humans write things down. Workers let developers run code on Notions own infrastructure to sync outside systems, trigger webhooks, and build tools for Custom Agents, while External Agents and the Agent SDK let those agents show up as teammates inside Notion or inside other apps. That creates a flywheel where more agent activity makes Notion more useful as the shared layer for work, context, and approvals.1 2 3 4

• The strongest network effect is workflow reuse, not social virality. One teammate can build a Salesforce Worker once, then share it so other teams connect it to their own agents. As more Workers, prompts, and agent skills accumulate, the next automation gets easier to build inside Notion than outside it.2 3
• This is broader than a classic integration marketplace. External Agents can be assigned work from shared boards, mentioned like coworkers, and audited inside enterprise controls. That means Notion is trying to own the execution surface where people, internal agents, and third party agents coordinate the same task.1 2 4
• The closest historical analog is Airtable’s push to become a builder platform, but with agents reducing the need to learn a complex schema by hand. Airtable showed how builder made workflows can spread across teams, while ClickUp is making the same argument that AI works best when docs, tasks, and other primitives sit in one system of record.5 6

If this works, Notion stops being judged mainly against docs and wiki tools and starts being judged as agent infrastructure for the enterprise. The winning product will be the one that keeps the most work context, the most reusable automations, and the most daily agent traffic in one place, because that is where future workflows will be built first.1 2 4 6