目錄
On September 22, 2026, the Notion Mail Inbox will officially shut down. At first glance, the announcement may look like the end of yet another short-lived Email Client. But for users who moved email sorting, frequently used replies, Email-to-Task actions, and project processes into Notion Mail, email was never the only thing that needed to be moved. Most Email remains in Gmail. The real difficulty lies in the sorting rules, Snippets, Custom Views, reminders, and connections between email and other workflows that gradually became part of daily work over the past year or more.
On September 1, a representative request for help appeared on r/Notion. The poster made it clear that what they would truly miss was not AI-generated email, but the workflow that turned an Email into an entry in a Notion Task Database with one click, along with their existing Snippets. They were looking for a free, Web-based alternative but found it difficult to locate exactly the same combination. This case explains the problem better than simply asking which Email App is most similar to Notion Mail, because what is being lost is not the ability to receive mail. It is a way of working that has already become embedded in everyday routines.
Notion's own explanation for the shutdown is also direct: as Notion Agents become more capable, more people are assigning organization, replies, and inbox maintenance directly to an Agent. More than half of Notion Mail users can now handle email without opening the Inbox at all, so the company has decided to focus its resources on “letting Agents manage the Inbox.”
This does not mean the traditional Inbox no longer has value, nor can this figure be used to infer that every user in the other half depends heavily on Notion Mail. Notion has not disclosed the product's total active user count, retention rate, or revenue, so it is currently impossible to determine whether this was a product failure, a resource-allocation issue, or simply a strategic shift. What is clear is that Notion is repositioning Email from a standalone interface into a work source that an Agent can search, sort, use to draft responses, and act upon.
When is Notion Mail shutting down? The full timeline from Skiff to Notion Mail
About 17 months from full launch to shutdown, not 18 months
The history of Notion and Email can be traced back to February 9, 2024. Notion acquired Skiff, a privacy-focused communication and collaboration service. Skiff Mail, Pages, Drive, and Calendar then shut down in August 2024, while Mail Forwarding for some users continued until February 2025.
On October 24, 2024, Notion first revealed the Notion Mail Preview at the Make with Notion event, where it was still labeled coming soon. The full launch took place on April 15, 2025, featuring AI Auto Labels, Custom Views, Snippets, scheduling through Notion Calendar, and AI Email Drafting.
On June 25, 2026, Notion announced that it would discontinue the Notion Mail Inbox and allowed users to export data that existed only in Notion Mail. September 21 is the final deadline for saving that data, and the Web, Desktop, and iOS versions will all stop operating on September 22. The period from the official GA launch in April 2025 to shutdown is about 17 months. Counting from the October 2024 Preview puts it closer to 23 months, so the original description of an “18-month product life cycle” is not precise.
Why is Notion shutting down Mail? The official reason is AI Agents
More than half of users already manage email without opening the Inbox
Notion included an important usage statistic in its shutdown announcement: more than half of Notion Mail users can currently manage Email without opening the Inbox. The scenarios listed by the company include having an Agent identify which messages need attention, reply to messages, and keep the inbox organized. Notion will therefore focus on Agents instead of continuing to maintain a standalone Mail Inbox.
This is consistent with Notion's product direction in the first half of 2026. When it launched the Developer Platform on May 13, Notion said teams had already created more than one million Custom Agents to handle Slack Q&A, weekly reports, task routing, and other work. It then introduced Workers, External Agents, and other developer capabilities intended to give Agents access to more external systems and custom logic.
However, the timing does not mean that “the Developer Platform launched, so Mail inevitably had to be cut.” Notion has not disclosed such an internal decision-making process. A more accurate interpretation is that both announcements reflect the same product direction: Notion is expanding the ability of Agents to read data and perform work directly, while a traditional interface that requires people to remain in the Inbox and organize Email has become less important within that direction.
What data will remain after Notion Mail shuts down?
Received and sent Email will not disappear
Notion Mail has always synchronized with Gmail in both directions, so Email that has already been received or sent already exists in Gmail. After Notion Mail shuts down on September 22, those messages will remain in the original Gmail Inbox. A separate full Mail Export is not required to preserve historical messages.
Mail Blocks already placed in a Notion Page will also remain after the Mail App is discontinued. The Gmail AI Connector will continue to work, allowing Notion AI to search Gmail or help with a Draft Reply. Agent Mail Tools connected through Gmail will likewise be unaffected by the shutdown of the Notion Mail Inbox.
One easy-to-miss exception is Synced Notion Mail Database Views. Email Records already synchronized to Notion and existing Filtered Views will remain, but no new Email will be synchronized after September 22. The View itself will not disappear; its data will simply remain frozen at the shutdown date and stop updating.
Which Notion Mail data must be saved separately before September 21?
Drafts, Scheduled Emails, Snippets, and Auto Label Instructions exist only in Notion Mail
Notion lists four types of data that must be handled before September 21. Drafts must be moved to Gmail, and Scheduled Emails must likewise be migrated to Gmail. The text in Snippets must be exported, while Auto Label Instructions must also be saved separately. If this data still exists only in Notion Mail on September 22, it will be permanently deleted after the shutdown.
It is not advisable to state that “every scheduled time will be transferred automatically and intact, so users only need to check Gmail afterward.” Notion guarantees only that it will provide Migrate scheduled emails to Gmail; it does not say that every scheduling status, time setting, and special condition will be transferred without change. Checking Gmail's Scheduled Folder again after migration is safer, but this is operational advice rather than an official guarantee.
Which Notion Mail settings cannot be moved even after export?
Custom Views, Snippet attachments, and Email Reminders require separate handling
Notion explicitly identifies three types of data that cannot be moved directly to another Email App. The first is the way the Inbox is organized, including Custom Views and Sorting. The second is files attached to Snippets. These attachments are not automatically exported with the Snippet Text and must be downloaded individually from Notion Mail → Settings → Snippets. The third is Reminders set on Email, which currently cannot be transferred to Gmail.
These three types of information are also the hardest parts to have another App take over unchanged after Notion Mail closes. Email itself has standard protocols and Gmail as its underlying data store, but the way Views are arranged, the timing of reminders, and which reply templates include which attachments are all part of Notion Mail's own Product Logic.
The item worth preserving is therefore not just the data, but also the logic. When a Custom View cannot be Exported, its Filters, Sorts, Groups, and purpose can be documented in writing. An Email Reminder that is still relevant can be recreated in a Calendar or Task System. Snippet Attachments should be downloaded before shutdown rather than leaving only the Snippet Text behind.
Why is it so difficult to find an exact Notion Mail replacement?
What is missing is not an Email Client, but an integrated way of working
The September 1 request on r/Notion explains the issue clearly. What the poster truly relied on was One-click Email-to-Task and Snippets that already contained fixed recipients and opening text. AI Drafting was only an additional feature.
When the shutdown was first announced in June, other discussions also specifically mentioned Snippets, Email-to-Notion Task, Ticketing Workflow, and the desire to link Email directly with Notion Context such as a Project, Client, Task, or Meeting.
Finding a free, Web-based tool that can receive Gmail is therefore easy. The difficult part is finding one product that can simultaneously rebuild an Email Client, Task Bridge, Snippet Library, Custom Views, and Notion Database Workflow. These are actually separate problems that happened to be bundled into one Notion Mail interface.
Can a Custom Agent directly replace Auto Labels after Notion Mail shuts down?
It can perform similar work, but the original rules will not migrate automatically
The method described in the official FAQ is to save Auto Label Instructions to a Notion Page, then create a Custom Agent with Gmail Access after September 22 and have it follow those Instructions to run a similar Labeling Workflow. This means Auto Label Logic can continue, but the original Rule cannot be completely moved into an Agent by clicking Import once.
The Custom Agent Mail Connection can currently Search, Archive, Star, Delete, create or remove Labels, Unsubscribe, Block Sender, and Draft or Send Email. From a capabilities perspective, it can rebuild a considerable amount of Inbox Automation.
This approach has two limitations. Custom Agents currently require a Business or Enterprise Plan, and every Run uses Notion Credits. Credit consumption rises as more content is read, more actions are performed, or Triggers run more frequently.
Moving to an Agent is therefore not a frictionless migration path for every Notion Mail user. If Free or Plus users previously used Mail's Views, Snippets, and sorting features at no cost, upgrading to Business to reproduce those behaviors and then paying for Agent Credits creates a completely different cost structure.
Will an existing Notion Email Agent keep running after September 22?
Agent Mail Tools connected to Gmail will remain
Notion's official explanation states that workflows already using Notion Agents to process Email, or those that already connect Gmail or Outlook to Notion, will not all stop simply because the Notion Mail Inbox is discontinued. The Gmail AI Connector, existing Mail Blocks, and Agent Mail Tools connected through Gmail will continue to work.
The data source is the important distinction here. The product being discontinued is the Notion Mail Inbox App, not Notion's entire Email Capability. Email will function more like a Connected Source for Agents and Notion AI than a standalone App that people must keep open.
Regulated industries cannot focus only on September 22: the official HIPAA transition deadline was earlier
Notion specifically warns that a Regulated Environment may need to complete migration before the general Shutdown Date. If an organization depends on Notion Mail's HIPAA Coverage, the official planning date was to complete the Transition before June 30, 2026. As it is now September, that date has already passed.
Healthcare teams and others with explicit Compliance Requirements should not continue to treat September 21 as the only Deadline. Organizations still using Notion Mail should directly confirm how their internal Admin, IT, or Compliance Team has handled existing data and workflows instead of waiting until the day before the App shuts down to start moving.
What should be completed before Notion Mail closes on September 21?
Save the data first instead of rushing to choose a new App
Before selecting a replacement tool, handle the content that is certain to disappear: move Drafts and Scheduled Emails to Gmail; export Snippets and Auto Label Instructions; manually download Snippet Attachments; and recreate active Email Reminders in a Calendar or Task System. Although Custom Views cannot be moved, the Filters, Sorting, purpose, and daily use of each View can still be documented.
If a workflow depends on a Synced Notion Mail Database, the September 22 cutoff should also be clearly marked. Old data will remain visible, but new Email will no longer arrive. Without an additional synchronization workflow, the most likely failure is not that the Database disappears. Instead, the workspace appears normal until someone discovers several days later that no new messages have entered it.
Route one: Stay in Notion and rebuild the workflow with the Gmail Connector and a Custom Agent
This route is suitable for teams that already use Business／Enterprise and ultimately need Email to enter Notion Projects, Tasks, or another Database. Existing Auto Label Instructions can be saved in Notion and converted into Agent Instructions, while a Mail Connection can allow the Agent to Search, Manage Labels, Archive, Draft, or Send.
The advantage is that Email and other Notion Context remain in the same work environment, while Notion is clearly continuing to invest in this product direction. The drawback is that a Custom Agent is not a free replacement. Triggers, Instructions, and Tools & Access must be redesigned, and Credits must be managed.
Users who preferred to organize the Inbox manually must also accept a practical difference: an Agent can rebuild the “rules,” but it will not automatically recreate the original visual interface. Custom Views, Sorting, and the experience of opening Mail to see an already organized workspace are still part of a product experience that is disappearing.
Route two: Return to Gmail and separate Email from the Notion workflow
If the main requirements are reliable Email sending and receiving, Labels, Search, and simple Filters, returning directly to Gmail has the lowest migration cost because historical Email is already there. No additional Mailbox Migration is required.
Existing Auto Label Instructions can serve as specifications for rebuilding Gmail Filters. Frequently used replies can also be recreated as Gmail Templates or stored as separate text snippets, depending on actual needs. Neither is a one-click transfer, however, and Notion Mail's AI Label Instructions may not translate one by one into Gmail's conditional Filters.
The largest gap in this route is the Email-to-Notion Workflow. Gmail will not automatically restore one-click conversion to a Task, writing to a Database, or other Notion relations. If this was the most important original function, a Notion Worker, Automation, Agent, or another Integration will still be required.
Route three: Switch to a third-party Email Client, but identify the layer that actually needs replacing
If the core need is Custom Inbox Views, Keyboard Workflow, Snippets, or rapid Triage, switching to another Email Client is reasonable. More important than comparing product Feature Lists, however, is documenting the actions previously performed in Notion Mail.
For example, Email itself can remain in Gmail while another Client handles only its presentation. Snippets can be managed by a separate Text Expansion Tool, and Email-to-Task can be assigned to an Automation. This may not place everything on one screen as Notion Mail did, but each layer can be replaced independently. The next time one service shuts down, the entire system will not need to be moved again.
When evaluating a third-party Client, users can specifically check whether Gmail／IMAP remains the Source of Truth, whether Rules and Templates can be Exported, whether they can return to native Gmail if the service shuts down, and whether the requested permissions exceed what is actually needed.
The most valuable thing to preserve is not the Notion Mail settings, but the workflow specification
The most difficult part of the Notion Mail shutdown is not that Email will disappear, because the messages themselves already remain in Gmail. The parts that are truly hard to move are those without a standard format, such as “which types of messages should be read first,” “which senders should go into which Project,” “which reply should be used in which situation,” and “what content should trigger the creation of a Task.” If these rules exist only in one product's settings page, they must be reconstructed from memory when that product shuts down.
A more practical approach is to keep a written specification of important Workflows. It does not need to be a complicated SOP. It only needs to make the Input, sorting conditions, required Action, and final destination understandable. Whether the workflow is later moved to a Gmail Filter, Custom Agent, Worker, or another Email Client, this document can be used to rebuild it.
The end of Notion Mail also does not need to be exaggerated into the claim that “Agents will eliminate every interface-based product.” The only current evidence is that Notion itself is moving the Email Workflow toward Agents and that more than half of Notion Mail users have adopted a way of working that does not require opening the Inbox. Whether other products will take the same path depends on their own usage patterns and business models.
One point is already clear: tools can be discontinued, but work habits do not migrate automatically with them. The most valuable things to preserve before September 22 are therefore not just a few Drafts and Snippets, but the rules that have already proved useful every day. The shape of the next tool can be decided later; at least there will be no need to remember from scratch how the previous workflow operated.
FAQs
They should not be assumed to remain automatically. Notion requires users to actively Migrate to Gmail their Drafts and Scheduled Emails before September 21. If they are not saved, they will be permanently deleted after September 22.
The text in a Snippet can be Exported, but Files attached to the Snippet will not transfer automatically. They must be downloaded manually from Notion Mail → Settings → Snippets.
There is no one-click transfer. Notion recommends saving Auto Label Instructions to a Notion Page first, then using a Custom Agent with Gmail Access after shutdown to create a similar Labeling Workflow.
No. Custom Agents currently require a Business or Enterprise Plan, and each run uses Notion Credits. Whether this is cost-effective depends on run frequency, the amount of content read, and the required Tool Calls.
No. Email Records already synchronized to Notion and existing Views will remain, but new Email will stop synchronizing after September 22. The Database will therefore remain frozen in its pre-shutdown state.
It will not stop merely because the Notion Mail Inbox closes. The Gmail AI Connector, existing Mail Blocks, and Agent Mail Tools connected through Gmail will continue to work.
No. Notion required organizations relying on HIPAA Coverage to plan to stop using Notion Mail before June 30, 2026. That date has already passed, so affected organizations should confirm their handling process directly with their internal Admin or Compliance Team.
No. Notion Mail has always synchronized with Gmail in both directions, so received and sent Email already exists in Gmail and will remain there after shutdown. Drafts, Scheduled Emails, Snippets, and Auto Label Instructions require separate handling.
The Notion Mail Web, Desktop, and iOS Inbox will stop operating on September 22, 2026. September 21 is the last day to save Notion Mail-only Data, and all plans are affected.