Email to Notion: four routes that work without Notion Mail

Notion has no email address of its own, and the app that came closest ends on 22 September 2026. Here is what still works, what it costs you, and where each route breaks.

Jacky Fakkeldij Building Driftto, on his own

You cannot CC a Notion database. There is no address to forward to, no notion.so mailbox, nothing built in. Thirteen years of Notion and the one thing people keep asking for is still not there, which is why a small industry of forwarding tools exists around it.

And the product that came closest is going away. The Notion Mail inbox ends on 22 September 2026; Notion's own help page names 21 September as the last day to save anything, and says unsaved data is deleted after that. Your actual mail is fine, because Notion Mail always synced both ways with Gmail, so everything you sent or received is still sitting in Gmail. What you lose is the place where email and your workspace were the same thing.

So here are the four routes that are left. I have put them in the order most people should try them, and I have written down where each one breaks, because that is the part the comparison posts usually leave out.

Why Notion has no email address

Notion is a database, not an inbox. A mail message has a sender, a subject, a body, attachments and a thread; a Notion row has whatever properties you decided it has. Somebody has to decide how one becomes the other, and Notion has never wanted to make that decision for you. Every route below is really just a different answer to the same question: who maps the email onto your columns.

That is worth holding onto while you read, because it explains the failure mode each route has. Whoever does the mapping is also the thing that breaks, and in this category that is the complaint that outlives every other one: across 336 reviews of capture apps, the note not arriving came first for thirteen years running.

Route one: a forwarding address from a third-party tool

The most common answer. A service gives you a unique address, you tie it to one database, and anything you send there turns up as a row. Quicktion and NotionSender both work this way, and the Gmail to Notion add-on in the Google Workspace marketplace does the same job from inside Gmail. Setup is a few minutes and it needs nothing from you afterwards.

Where it breaks: your mail goes through somebody else's server on its way in, which is a real consideration if the mail is client work. It is another subscription on top of Notion. And the mapping is theirs, so when you want the sender in one property and the subject in another, you get whatever fields they chose. If the service stops, the address stops, and you find out because a row did not appear.

Route two: an automation you wire up yourself

Zapier, Make and n8n all have an email trigger: they hand you an address, you parse the message, and you write the row through the Notion API yourself. This is the route with no ceiling. You decide which part of the mail goes in which property, you can filter on sender or subject, and you can send the same message to two places at once.

Where it breaks: you are now maintaining it. Parsing rules that work on your own plain messages fall over on a forwarded thread with a signature and three quoted replies. Most of these platforms bill per task, so a noisy inbox gets expensive quietly. And when a run fails, it fails in a dashboard you are not looking at, which means the note is simply not in Notion and nothing told you.

Route three: the Gmail connector Notion points you to now

This is what Notion itself recommends in place of Notion Mail: connect Gmail so Notion AI can search and draft against it, and put mail blocks on the pages where you want a conversation visible. Those blocks keep working after the shutdown. It is free with Notion and it is the least work of anything here.

Where it breaks: it is built for reading, not for filing. It lets Notion see your mail; it does not put a row in a database with your properties filled in. If what you wanted was an inbox you could query from a Notion view, this is not that, and no amount of setup turns it into that.

Route four: stop sending the email

Worth asking what is actually in the mail you keep sending yourself. If it is a real message from a real person that you need to keep, none of this applies and you want route one or two. But a lot of what lands in an inbox this way is not mail at all. It is a thought, addressed to yourself, because email was the fastest text field within reach.

That is the one I built Driftto for. Type it, speak it or snap it once, pick Notion as the destination, and it becomes a page in the database you chose with the fields filled, without an inbox in the middle. Reminders, Todoist, Asana, Jira and more destinations work the same way, and one capture can go to several at once. Driftto is in the App Store on October 1.

Where it breaks, and I would rather say it than have you find out: Driftto does not forward mail. There is no address to send to. If your job is getting messages other people sent you into Notion, it is the wrong tool and one of the first two routes is the right one.

Which one you want

• Archiving real emails, and you want it working today

  A forwarding tool. Least setup, known mapping, and you can be filing mail in five minutes.

• Real emails, but the mapping has to be yours

  An automation. More work up front and it needs an owner, but nothing else lets you decide which part of a message lands in which property.

• You mostly want to read and search mail near your notes

  Notion's own Gmail connector. Free, no third party, and it does not pretend to be a filing system.

• The mail you send is mail to yourself

  Skip the inbox. The thought was never email; it just went out through email because that was the fastest way to get it out of your head.

Every one of these routes is somebody deciding how a message becomes a row. Pick the one whose decision you can live with, because that is also the one that will break.

Questions