Outlook to Notion: 4 Ways to Connect Outlook and Notion

Notion has no Outlook add-in. Microsoft has no Notion connector of its own. Notion Mail, the one first-party thing that pushed email into a Notion database, was Gmail-only and closes on September 22, 2026. So "outlook notion integration" is a search with no native answer, which is why the results are a mix of Power Automate walkthroughs, Zapier templates, and people asking in forums.

I build Quicktion, which does Outlook to Notion through forwarding, so I have a stake here. What follows is the four options as they stand in 2026, with the honest version of when each one is the right pick.

1. Email forwarding with an Outlook rule (Quicktion)
2. Microsoft Power Automate
3. Zapier or Make
4. Notion Mail, and why it was never an option for Outlook

And the question I get most from Outlook users, answered up front: no, there is no Quicktion Outlook add-in. The Gmail add-on doesn't run in Outlook. Method 1 is forwarding, and forwarding covers most of what people are trying to do.

Method 1: Email forwarding with an Outlook rule (Quicktion)

Outlook can forward mail. Notion can create pages through its API. Quicktion connects the two.

How it works

Connect your Notion workspace in Quicktion, pick a database, and map the parts of an email to its properties: subject to the title, sender to a text or email property, date to a date property, and so on. Quicktion gives you a forwarding address like xyz@in.quicktion.io for that destination.

In Outlook, create a rule. From a client domain, subject contains "receipt", sent to your shared inbox, whatever the pattern is. Action: forward to your Quicktion address. Each matching email becomes a page in the database within seconds, body converted into Notion blocks, attachments uploaded.

There's no flow to build and no JSON to maintain. Rename a property in Notion and the destination keeps working.

The Outlook-specific bits

Rules built in Outlook on the web (or in the Exchange admin center) run on Microsoft's servers, so they don't need your laptop open. Rules built only in the Windows desktop client run when Outlook is running. If the intake needs to work at 3am, make the rule on the web side.

Shared mailboxes are fine. A rule on support@ puts every ticket in the shared database.

If your rule saves but nothing shows up, check whether your tenant blocks external auto-forwarding through Exchange transport rules. That's the usual culprit.

Outlook categories are local metadata and don't survive forwarding. Set default values on the Quicktion destination instead (Source = "Outlook", Status = "Inbox") and every page arrives tagged.

The click-by-click for desktop, web, mobile, and Exchange rules is in How to Save Outlook Emails to Notion, so I won't repeat it.

What you get

The email body as real Notion blocks: headings, lists, links, bold, inline images, all kept. Not a wall of plain text and not raw HTML. Attachments uploaded to the page or a files property. On Pro, AI Email Intelligence reads the body and any PDF or image attachment and fills properties from a prompt you write: amount and vendor for receipts, priority and requester for support mail, company and intent for a partnerships inbox.

What you don't get

Edit-before-save. That's the one thing the Gmail add-on has that Outlook forwarding doesn't. Properties are filled from the destination config, so you can't tweak the Status on one particular email before it lands. Good for predictable intake, less good for one-off "let me tag this differently" moments. Quicktion also isn't a two-way sync; a page in Notion doesn't send or update the email in Outlook.

When to use it

When the goal is "this kind of email should become a page in this database." A client CRM, a receipts log, a support queue, a newsletter archive, a research inbox. It works the same on Outlook desktop, web, mobile, Microsoft 365, and any Exchange that can forward externally.

Free is 25 emails a month and one destination. Pro is $12/month for 1,000 emails and unlimited destinations.

Method 2: Microsoft Power Automate

If you're in a Microsoft shop, this is what IT will suggest, and it does work.

How it works

Trigger: "When a new email arrives (V3)" from the Office 365 Outlook connector, filtered by folder, sender, or subject. Action: "Create a page" from the Notion connector. The page's properties go in as a JSON object you assemble in the flow. If you want the email body on the page, that's a second call, "Append block children", where you build the blocks yourself.

The licensing and the connector

Per Microsoft's connector reference, the Notion connector is an Independent Publisher connector in the Premium tier for Power Automate. A standard Microsoft 365 seat only includes Standard connectors, so you need Power Automate Premium licensing (per user or per flow) to use it. It authenticates with an API key, which for Notion means creating an internal integration and sharing the target database with it. It has no triggers, only actions, which is fine here since Outlook is the trigger.

Where it gets tedious

Notion's page properties API is strict about shape: a title property, a rich_text property, a date property, and a select property all have different JSON structures, and the connector's "Create a page" hands you a raw properties object to fill. Getting one wrong returns a validation error rather than a page. The HTML body needs converting to text (losing links and formatting) or converting to Notion blocks by hand. Attachments have to go somewhere with a public URL first, because Notion's API takes external file URLs, so you're routing through OneDrive or SharePoint sharing links.

None of this is impossible. It's an afternoon the first time and a small maintenance tax after.

When to use it

When you already have Premium licensing and Power Automate flows for other work, and the Notion page is one step in a longer sequence that also touches Teams, SharePoint, or Planner. Or when compliance has standardized on Power Platform and a third-party forwarding tool won't pass review. Those are real reasons. For a standalone "email into a Notion database" job, forwarding is a lot less to own.

Method 3: Zapier or Make

Both have a Microsoft Outlook trigger and a Notion action, and both have templates for this pairing.

How it works

Zapier: "New Email" in Microsoft Outlook, then "Create Database Item" in Notion. Make: Microsoft 365 Email "Watch Messages" feeding a Notion "Create a Database Item" module.

Where they fall short for Notion specifically

The body lands as plain text or raw HTML in a rich text property or as a single text block, not as formatted Notion content. Attachments come through as file objects that need extra steps to become files on the page. Triggers poll on an interval, so there's a delay after the email arrives. And each email is a task or an operation, so anything beyond a trickle turns into per-email billing.

When to use them

When the Outlook email needs to land in several places at once: a Notion page, a Slack message, a row in Sheets, a Teams ping. If Notion is the only destination, forwarding is cheaper and the pages come out cleaner. Zapier Email to Notion Alternative has the detailed comparison.

Method 4: Notion Mail (it never worked with Outlook)

I'm including this because it's the answer that keeps showing up in searches, and it's worth being clear about.

Notion Mail was Notion's own email client, and it could sync incoming email into a Notion database. It only ever connected to Gmail. If you're on Outlook or Microsoft 365, you never had access to it, and no amount of setup was going to change that.

It's also going away. Notion is winding down the Notion Mail inbox on September 22, 2026, and the email-to-database sync ends with it. Existing synced databases stay, but new emails stop arriving. The details are in Notion Mail Is Shutting Down.

So for Outlook users this method has two problems: it never applied, and it's about to not exist for anyone. The reason to mention it is that people arrive at "notion mail outlook" hoping there's a version for them. There isn't. Forwarding is the thing that has always worked regardless of email client, and it's the same setup Gmail users are moving to now that the sync is ending.

Method comparison

Which one should you actually pick

If Notion is where the email needs to end up and that's the whole job, use forwarding. It was built for this, the pages come out readable, and the free plan is enough to see whether your property mapping is right.

If you're a Microsoft shop with Premium licensing and a Power Platform team, and the Notion page is one step in a bigger flow, Power Automate is defensible. Budget the afternoon for the properties JSON.

If the email has to fan out to several apps, Zapier or Make.

If you were hoping for Notion Mail, that ship never docked at Outlook and is now leaving for everyone.

Getting started

Sign up for Quicktion, connect your Notion workspace, create a destination on the database you want, and set one Outlook rule. Forward a test email and check that the body reads well as blocks and the attachment is on the page. Free is 25 emails a month.

Related guides

• How to Save Outlook Emails to Notion, the step-by-step for Outlook desktop, web, mobile, and Exchange rules
• Notion Mail Is Shutting Down, what ends on September 22 and what to do about it
• Gmail to Notion Integration, if part of your team is on Gmail and wants the add-on
• Zapier Email to Notion Alternative, the Zapier comparison in depth
• Outlook to Notion, the product page