If a Notion Mail workflow is changing, start by protecting the part that creates value: getting the right new messages into a place your team already uses. Mailsink is a focused email-to-workspace capture tool for that job.
Notion's official help says the Notion Mail inbox shuts down on September 22, 2026. Its announcement and your workspace's current behavior are the source of truth for product-specific details. This guide focuses on a forwarding workflow for new messages; it is not a historical migration plan.
Notion says existing synced email databases remain accessible but stop receiving new messages after the shutdown. Existing email history remains in Gmail. See Notion's official next-steps help article for export guidance. Mailsink is one option for a separate new-message capture route.
What Mailsink does—and does not do
Mailsink gives you a private forwarding address for an Email Inbox. You connect Notion or Airtable, choose or create a destination, and send a message to that address. The resulting workspace record gives you a place to review the message details and continue your workflow.
Mailsink is not a replacement inbox client. It does not recreate Notion Mail's inbox experience, promise access to the same old synced database, or migrate historical mail in this workflow. Prove the new route with one real message before changing a provider-wide rule.
The manual-first setup
- Choose the destination. Connect Notion if you want pages, notes, and flexible database views. Choose Airtable if you want structured rows, filters, and operational tracking.
- Create an Email Inbox. Use the general preset so the first test is about message capture, not a narrow business schema.
- Forward one real message manually. Use your normal mail app and send a message to the generated Mailsink address.
- Review the saved result. Confirm the fields and content available in your destination, and check any attachments against your provider, destination permissions, and plan limits.
- Automate only after the test. Add an approved provider rule only after you know the route is useful and permitted by your organization.
Gmail: use the reliable manual path first
Gmail commonly sends a verification message to the external forwarding destination when you add it. The address must be confirmed before an automatic forwarding rule can run. The current Mailsink beta does not reliably surface that message in-app, so manual forwarding or BCC is the reliable path until you can confirm the automatic route yourself.
If you later confirm the address and enable a narrow filter, test it with a message you can recognize. If it does not arrive, check the filter, the forwarding address, spam, and the Mailsink activity result before broadening the rule.
Microsoft 365: check tenant policy first
Some Microsoft 365 tenants block external automatic forwarding and return a 5.7.520 policy response. That is a tenant-level mail control, not something Mailsink can override. Ask an administrator about the approved route, or use manual forwarding or BCC when your policy allows it.
Keep the workflow tool-focused
The same forwarding pattern can support different jobs:
- Receipts and invoices: use a focused preset when you need finance fields.
- Lead or support email: use a structured workflow when a team needs triage and follow-up.
- Newsletters and research: save useful messages where they can be searched and reused.
- General email inbox: capture a new message first, then decide what fields or views earn their place.
Notion and Airtable remain first-class choices. You can start in Notion for a richer page-based workspace, or use Airtable when a row-oriented operating view is a better fit.
Privacy and security check
Only send messages you intend to capture to the Mailsink address. Workspace connections use OAuth, and the current Privacy Policy describes how Mailsink processes and retains data. Review that policy before routing sensitive email, and keep your first test limited to a message appropriate for the destination.
Next step
See the Notion Mail alternative workflow, create a Notion Email Inbox, or start the same workflow in Airtable.