Our Take
Notion is admitting that a purpose-built email client loses to agents that run on top of existing inboxes—a sign that email as a separate product category is eroding.
Why it matters
Email clients have been a standalone category for 25 years. If Notion's own users prefer agents to native mail, the shift from email-first to agent-first workflows is no longer theoretical. This matters to anyone building or buying email infrastructure.
Do this week
Notion Mail users: export auto-label rules and drafts before September 21 so you can migrate to agents or alternative mail clients without rebuilding configuration.
Notion Mail shuts down in September
Notion is discontinuing Notion Mail, its AI-centric email client built on Skiff's infrastructure, by September 21, 2026. The company confirmed the shutdown via X post and support documentation, instructing users to export drafts, scheduled emails, and auto-labeling rules before the cutoff date.
Users with auto-label configurations can migrate those rules to Notion's custom agents without rebuilding them. Notion Mail connections for existing agents will continue to function. However, organizations requiring HIPAA compliance must transition off Notion Mail by June 30, 2026—three months earlier than the general deadline.
Notion acquired Skiff in 2023, a privacy-focused email provider that reported 2 million users. Skiff's core infrastructure and former executives shaped Notion Mail, but the product never gained the traction Notion expected. Unlike Skiff's end-to-end encryption model, Notion Mail functioned as a Gmail client without native privacy features, relying instead on AI agents to automate inbox management.
Why agents won: email as a separate product is losing
Notion's pivot exposes a structural change in how users expect to work with email. Rather than consolidating mail into a single client, practitioners prefer agents that operate on top of existing inboxes (Gmail, Outlook) and handle filtering, labeling, and triage autonomously.
This is not nostalgia for Gmail. This is users voting that email management (the problem) no longer requires email clients (the solution). Agents that connect to your existing mail backend, extract context, and execute rules outcompete purpose-built mail UIs. The inbox becomes an API surface, not a primary interface.
Notion's decision to "go all in on using agents to run your inbox" reflects actual product adoption data. If Notion Mail users preferred a dedicated mail experience, Notion would not be sunsetting it. Instead, Notion is folding email into its agents platform, treating mail as one of many data sources an agent might access, not as a core product.
This matters beyond Notion. Email clients (Superhuman, Newton, Spark) have competed on speed and UX for years. If agents prove sufficient for the core use case—automated triage, smart replies, rule-based actions—then email as a standalone category shrinks to niche users who prize encryption or offline capability.
What to do before the September deadline
Notion Mail users have five months to transition. The company is preserving auto-label rules via custom agents, which reduces friction for users with heavy configuration. For those without auto-labels, migration is simpler: export drafts and scheduled messages to Gmail or another provider.
Teams reliant on Notion Mail for workflow automation should audit which rules map to agent capabilities in Notion's platform and which require a standalone mail client. If your use case is pure inbox automation (labels, filters, triage), agents may suffice. If you rely on encryption, offline mail, or compliance features Skiff once provided, you will need to migrate to ProtonMail, Tutanota, or a corporate email provider.
Notion's continued investment in Skiff's calendar and storage infrastructure suggests the company is extracting value from the acquisition—just not in the email-as-a-product direction. Organizations that integrated Notion Mail into compliance workflows should plan migration well ahead of the June 30 HIPAA deadline.