Notion 3.3 adds custom team agents

Notion is making a serious bid to turn the workspace itself into an agent runtime, not just a place where AI helps you write faster. That moves the product closer to an operating layer for knowledge work, but it also makes governance, model choice, and cost controls central to whether teams will trust it.

• –The most important shift is autonomy: agents can run from triggers and schedules instead of waiting for someone to prompt them each time.
• –Notion is aiming at real operational workflows like inbox triage, internal Q&A, ticket routing, and recurring reports, which gives the feature more weight than a generic chatbot layer.
• –MCP support matters because it lets Notion reach beyond its own suite into tools like Linear, Figma, and HubSpot without pretending every workflow lives entirely inside Notion.
• –The company is clearly targeting enterprise adoption with permission controls, run logs, and admin settings, which are table-stakes for agents that can touch team systems.
• –Free trials through May 3 and credit-based pricing starting May 4 suggest Notion expects heavy experimentation first, then a more explicit ROI conversation once usage scales.