Getting email into Notion no longer starts with a third-party automation. Notion can now handle the common jobs itself; the exceptions are plan limits, large files and workflows that need the full email object.
Most of the time you don’t care about the email object itself. You care about the information inside it — the lead to log, the task to capture, the invoice to file. The right method depends on which parts of the email your system needs.
What Can Notion Do With Email By Itself in 2026?
Quite a lot. For years, getting email into Notion meant bolting on a third-party automation tool. Today Notion reads your mailbox, labels it, drafts replies, sends them, and fires automations on new messages without any middleware in the chain. Skills, Agents and Workers now cover most jobs that previously needed middleware.
For the email jobs most people actually have, you no longer need a third-party tool. A few specific jobs still do. Knowing where the native path stops — and which of the two mail connections you actually want — is the difference between a setup that works and an afternoon wasted.
What Changed in 2026
Four changes in 2026 reshaped the available options:
- January 2026 — Notion shipped the first native push from Notion Mail into Notion databases: an email action for a single message, or a sync for a whole Notion Mail view.
- 22 September 2026 — the Notion Mail inbox app shuts down. That native sync goes with it. Here’s what the shutdown means in practice.
- 15 August 2026 / 14 September 2026 — Relay.app shuts down, free accounts first, then paying customers. New signups are already disabled. Relay used to be the recommended method on this page; it is no longer a route you can take.
- 15 October 2026 — Notion Workers stop being free. They are free to try on Business and Enterprise during the beta; from that date they run on Notion credits at $0.0023 per run (roughly 4,300 runs per 1,000 credits). Relevant to method 3 below.
Notion Mail appears here as history only. Its shutdown does not affect agents connected to Gmail or Outlook — Notion is explicit that “nothing changes if you’re already using Notion agents for email,” including agents that read, draft, and send. The inbox app dies; the agent mail connection does not.
The Two Ways to Connect Gmail or Outlook to Notion
Notion has two mail connections in two different settings screens. One gives your AI access to your own inbox. The other makes company mail searchable across a workspace.
| Personal Mail & Calendar connection | Workspace AI Connector | |
|---|---|---|
| What it’s for | Giving your Notion AI and agents access to your mailbox | Making the organisation’s mail searchable for everyone in the workspace |
| Who sets it up | You, in your own account settings | An admin — a Google Workspace or Microsoft 365 admin who is also a Notion workspace owner |
| Where | Settings → Account → Mail & Calendar | Settings → Notion AI → AI Connectors |
| What Notion AI can do with it | Search your inbox, draft and send, run new-email triggers, work with your calendar | Search and read company mail. It cannot send. |
| Attachments | ✅ Reads PDFs, images and text files, within size limits | ❌ Notion’s docs state it can’t read attachments |
| Accounts | As many mail and calendar accounts as you like | One Notion workspace to one Google or Microsoft tenant |
| Plan gate | Business or Enterprise (for Skills and Agents) | Business or Enterprise, plus a paid Google Workspace or Microsoft 365 tenant |
For an inbox assistant, use the personal connection under Settings → Account → Mail & Calendar. It can read, draft, send, trigger on new mail and access your calendar. You manage the connection yourself and can attach several accounts.
Company-managed Google Workspace and Microsoft 365 accounts may block third-party connections. IT controls that policy; it does not configure the Notion connection for you. Personal Gmail and Outlook accounts have no equivalent gate.
The Workspace AI Connector makes company mail searchable across Notion. An admin installs it once for the organisation. It is read and search only — it cannot send email, and Notion’s documentation says it cannot read attachments.
If you expected it to reply from your inbox, you picked the wrong connection. Most claims that Notion’s Outlook integration requires IT are describing this connector while intending to use the personal one.
Where the Native Path Stops
The native path has three limits as of 21 July 2026: plan access, usage credits and attachment size. Notion’s help pages carry no “last updated” stamp, so re-check before a big rollout.
- Free and Plus plans get nothing. Skills, Custom Agents and Notion Workers are all “available on Business and Enterprise plans.” Free and Plus get trial AI capabilities only — and Plus is a paid seat that still doesn’t qualify. Below Business, methods 1 to 3 are closed to you and Make isn’t a workaround, it’s your only option.
- It’s metered, and it stops. Custom Agents run on Notion credits, an add-on priced at $10 per 1,000 credits; a mail-triage agent costs roughly 100 to 250 runs per 1,000. Run out and your agents “pause automatically.” Downgrade to Free or Plus and existing agents are switched off. From 15 October 2026 Workers are metered too. Flat-rate middleware can genuinely be cheaper at volume, and it doesn’t halt mid-month.
- Very large or cloud-linked attachments. The personal mail connection does read attachments — see below — but not at any size. Bulk-filing large scans or Drive-linked contracts is still a job for the Make route.
The native path works until you hit a plan, volume or file-size limit.
Can Notion AI Read Email Attachments?
Yes. The personal mail connection reads PDFs, images and text files within size limits. Our product test confirmed this on 21 July 2026. The “no attachments” line in the documentation sits on the Workspace AI Connector pages, where it is accurate; it does not describe the personal connection.
In our 21 July 2026 tests, the main mail connection handled files up to roughly 3 MB and the Gmail-specific reader reached roughly 10 MB. Notion publishes neither limit. Everyday invoices and receipts should be fine; use Make for large scans and cloud-linked files.
Which Method Should You Choose to Get Emails Into Notion?
| Method | What It Is | Plan Gate | Cost | Setup | Attachments | Best For |
|---|---|---|---|---|---|---|
| 1. Skills | A saved briefing your Notion AI runs on demand | Business / Enterprise | Included in the seat | Low | ✅ within size limits | Recurring inbox jobs you trigger yourself |
| 2. Agents | A skill handed to an agent that runs unattended | Business / Enterprise + credits | ~$10 per 1,000 credits | Medium | ✅ within size limits | Hands-off jobs like labelling every new email |
| 3. Full sync | A script that writes real emails into a Notion database | Business / Enterprise as a Notion Worker — none if you self-host | Free until 15 Oct 2026, then metered; free if self-hosted | Higher | Buildable | Actually storing the email object in Notion |
| 4. Make | A no-code automation forwarding mail into Notion | None | Free tier is enough | Medium | ✅ any size, via Google Drive | Free/Plus plans, large attachments, any mail provider |
On Business or Enterprise, start with a skill and promote it to an agent once it works. If you need the actual email object in a database, build the full sync. If you’re on Free or Plus, or you’re moving large files around, go straight to Make — it is the only method here that works on every plan.
Method 1: How Do Skills Teach Your Notion AI to Handle Your Inbox?
A skill is a saved briefing that teaches your Notion AI how to do a repetitive job once, so you can run it any time with a single command. Plan gate: Business or Enterprise. Once you’re there, running skills yourself is included in your seat rather than metered per run.
Say you log new leads into your CRM several times a week. Teach your AI the process once, then say “log today’s leads” whenever you want it to handle the busywork.
A usable skill needs four things: a clear job, the context and tools it may use, a step-by-step process and explicit boundaries. Our complete skill-engineering guide breaks down each part.
For your inbox, there are roughly four types of skills worth building:
- ✅ Summarising — “give me a brief of everything that landed today.” Be specific about what’s actually useful, or the summary won’t help you act.
- ✅ Organising — labelling and filing emails so you can sort your inbox at a glance.
- ✅ Capturing — pulling a lead into the CRM, an invoice into your finance database, or a task out of an email and into Notion.
- ✅ Responding — drafting or sending replies on your behalf, for example answering common questions from a Notion knowledge base.
A great skill captures your judgement. “Read later” or “interesting news” mean different things to different people, so we use the ACDC framework — having the AI ask you clarifying questions up front — so it labels and files things exactly the way you would.
Copy and adapt this triage skill for your inbox:
---
name: triage-inbox
description: >
Read today's unlabelled emails and apply one category label to each, so
the inbox sorts itself. Use it whenever you want to "triage the inbox,"
"label my mail," or clear a backlog of uncategorised messages.
---
# Triage & Label Today's Inbox
Read every unlabelled email in today's inbox, work out what each one is
actually about, and apply exactly one category label. This skill only
labels — it never archives, deletes, replies, or sends.
## Categories
Apply the single best-fit label per email:
- **Action Required** — needs a reply, decision, or task from you
- **Read Later** — worth reading, not time-sensitive (newsletters, long reads)
- **Interesting News** — product or industry news to be aware of
- **Promotions** — marketing, sales, discount offers
- **Travel Information** — bookings, itineraries, check-ins
- **Invoices** — bills, receipts, payment confirmations
## Process
1. Pull today's messages and focus on threads with no category label yet.
2. Read sender, subject, and a snippet of the body to classify each one.
3. Pick one best-fit label. When two fit, prefer "what needs me" over
"nice to know": Action Required > Invoices > Travel > Interesting News >
Read Later > Promotions.
4. Apply the label — only ever add, never strip existing labels.
5. Report back: counts per category, plus anything left unlabelled.
## Rules
- Reuse existing labels by exact name — never spawn near-duplicates like
"Action Needed."
- One category per email; use the priority order to break ties.
- Labelling only — no archiving, deleting, moving, replying, or sending.
- When intent is unclear, leave it unlabelled and flag it rather than
forcing a wrong category.The second example turns inbound enquiries into CRM records:
---
name: log-leads
description: >
Scan today's inbox for genuine inbound leads, extract the key details,
and log each one into the CRM as a linked Contact, Company, and Deal at
the New Lead stage. Use it for "check my inbox for leads" or "log today's
leads."
---
# Log New Leads from the Inbox into the CRM
Find real inbound enquiries in today's inbox and turn each into a clean,
deduplicated CRM entry — Contact > Company > Deal at **New Lead** — with no
manual copy-paste.
## Context
- **Inbox** — your connected email account.
- **CRM** — work only inside Deals/Pipeline, Contacts, Companies, and
(optionally) an Email Sync database.
## Process
1. **Pull today's inbox.** A lead can arrive from any sender or subject, so
work from the inbox, not a keyword search.
2. **Separate leads from noise.** A lead shows inbound interest in your
services (a pricing question, a referral intro, a demo request). Ignore
newsletters, vendor pitches, invoices, and internal mail.
3. **Extract the fields** the CRM needs — name, email, role, company,
website, what they want, and value only if stated.
4. **Deduplicate first.** Match the Contact by email and the Company by
name/domain. Reuse and update existing records — never create a double.
5. **Confirm with me.** Show the shortlist of detected leads before writing
anything, and wait for a go-ahead.
6. **Create records in order:** Company > Contact > Deal, so every relation
has a target. Set every new Deal to **New Lead**.
7. **Report back** what was logged and anything skipped.
## Rules
- Always confirm the shortlist before creating records.
- Deduplicate on email (Contacts) and name + domain (Companies) every time.
- Leave Value and Expected Close blank unless the email states them —
invented numbers corrupt pipeline reporting.
- When intent is ambiguous, surface the email for review rather than logging
or discarding it silently.💡 Keep skills narrow. Organise first, summarise second and respond last. Each stage gives the AI a smaller decision to make.
💡 Our bi-weekly newsletter includes ready-to-copy skills and 41+ free Notion resources. Join 39,000 other readers here.
Method 2: When Should You Hand a Skill to a Notion Agent?
Hand a skill to an agent when the job must run without you remembering to trigger it. Plan gate: Business or Enterprise, plus credits.
A skill is reactive. You have to remember to run your triage, your lead capture, your follow-ups. But your human context window is tiny — you can only keep a handful of things front-of-mind at once. An agent removes that mental load by running the skill in the background, every time it’s needed.
Your personal AI (bottom-right corner) is included in your seat. Custom Agents consume credits per run: roughly 100 to 250 mail-triage runs per $10 — and when the credits run out, your agents pause automatically. Budget for it, or filter hard so the agent only wakes for mail that matters. (For the full picture, see how Notion agent pricing works and three principles to cut your AI bill.)
Always build and test a skill manually first, then promote it to an agent once you know it works. Store the skill separately and have the agent reference it. Multiple agents can then share one skill, and you update it in one place.
How to Connect Outlook (or Gmail) to a Notion Agent
Most setup problems start with the wrong feature. Connect your mailbox under Settings → Account → Mail & Calendar — the personal connection — not the Workspace AI Connector.
You sign in with your own OAuth login, and you can attach several mail and calendar accounts to the same Notion account. You then grant the agent a permission set — “Modify inbox, Draft, and Send” — and can optionally require confirmation before it sends anything, which is the setting most people want on day one. Four new-email triggers are available, filterable by From, To, Subject, Body, or Domain.
For Outlook specifically:
- Outlook has the same Business or Enterprise plan gate as Gmail. Plus and Free do not qualify for either.
- You don’t need a Microsoft 365 admin to set this up. The admin requirement belongs to the Workspace AI Connector, which is a different feature that only searches mail. What your IT team does control is whether staff may connect third-party apps to the tenant at all — a policy switch, not a setup step.
- Attachments work here. The personal connection reads PDFs, images and text files within size limits. The “can’t read attachments” line in Notion’s docs is written about the Workspace AI Connector, not this.
- If you’re connecting Notion Mail to an agent, migrate before 22 September 2026. Gmail and Outlook connections are unaffected.
What Should Actually Run as an Agent?
- ✅ Great for agents: labelling — it can quietly sort every new email in the background.
- ⚠️ Depends: replies. If you’ll review every draft anyway, an agent buys you nothing — you might as well run the skill yourself.
- ✅ Worth it: small “glue” jobs, like watching for a lead’s reply and updating the CRM stage automatically.
Choose the trigger and model separately. Run triage on every new email; run a digest on a schedule. Test the instructions once on a capable model, then move to a faster, cheaper one. If the best model still fails, fix the instructions.
💡 Save credits with inbox rules. Before reaching for AI at all, check whether a plain inbox rule can do the job. If certain senders always belong in one folder, a rule handles it for free — save the AI (and the credits) for the calls that actually need judgement.
Want hands-on help building these? We run a live skills workshop regularly — you’ll find the next date and the sign-up link in our newsletter.
Method 3: How Do You Sync Real Emails Into a Notion Database?
A full sync is for workflows that need the email object itself inside Notion, such as a complete thread on a shared client record. A script pushes the emails straight into a Notion database.
The flow has three parts: a script in Google Apps Script fires a webhook whenever a labelled email arrives, a Notion Worker catches that webhook, and it writes the email into your Notion database. An AI coding agent can build it from clear directions.
Plan gate: Business or Enterprise — Notion Workers sit on the same tier as Skills and Agents, and a workspace owner controls who may create them. They are free to try during the beta; from 15 October 2026 they run on credits at $0.0023 per run.
Self-hosting removes the Business-plan gate and Notion’s per-run meter. A Notion Worker is managed TypeScript, so the same code runs on a small server, cron box or serverless function and writes through the Notion API. You trade the managed runtime for your own deployment and maintenance.
Set Up an Email Tracker Database First
Whichever way you sync, you need somewhere for the emails to land. A simple setup could include these properties:
- Subject Line
- Sender Name
- Email Address
- Date Received
- Status (handy if you want to run the inbox as a pipeline)
The free template at the bottom of this page ships this backend already built, along with related Attachments, Tasks, and Contact CRM databases.
Build the Sync With an AI Coding Agent
Use the five-stage build flow — the same one we use to build a Notion Chrome extension with AI and run with tools like Claude Code and Codex:
- Feasibility — sanity-check that the idea is buildable (for email sync, it is).
- PRD — describe in plain English what should happen, e.g. “one Notion row per email thread.”
- Grill me — let the AI interview you to surface the decisions you forgot to make, like “filter by label, or pull every email?”
- Plan — have the AI turn your answers into a step-by-step build plan.
- Build — let it write the script one slice at a time while you test.
Filter by label — apply one manually or with your triage agent from method 2, then sync only those emails so your Notion database stays focused on what matters. Never paste your Notion API token into the chat. Store it in a .env file using a code editor like VS Code, and grab the token from the Notion Developer Portal so the AI can use it without ever seeing it.
How to Integrate Emails With Your Notion CRM
If you use a Notion CRM, connect your email tracking to it. You’ll need a CRM database with contact information (including email addresses) and a Relation property linking it to your email tracker database.
The logic is the same whichever method you use: look up a contact whose email address matches the sender. If one is found, link the new email to that record. If not, create a new contact and fill in the name and email address from the message.
This is the job the log-leads skill above already does — and it does it better, because it deduplicates and asks you to confirm before writing. Reach for the sync-and-lookup version when you want every email attached to its contact automatically, and the skill when you want judgement applied to which ones are worth logging.
Tip: For newly created contacts, you can have AI enrich the record from public sources before it lands in your pipeline.
Method 4: How to Add Emails to Notion Using Make (No Plan Gate)
Use Make when you are below Business, need to move large files, expect enough volume to make credits expensive, or use a mail provider outside Gmail and Outlook. It is the only method here that works on every Notion plan.
Use Make when any of these is true:
- You’re on Free or Plus. Skills, agents and Workers are all Business/Enterprise; this isn’t gated at all.
- You’re moving large or cloud-linked files. The native connection reads everyday attachments, but this route puts the file itself in Drive at any size and links it back to the email.
- You’re at volume and per-run credits would get expensive or pause mid-month.
- You use a mail provider outside Gmail, Outlook and Notion Mail. The mailhook below is provider-agnostic — anything that can forward an email can feed it.
The Make workflow is unaffected by the 2026 shutdowns. For this example, I created a basic database in Notion to store emails with the properties Subject, Email and Sender.
Step 1: Create Your Make Account
Start by creating an account at Make.com. The free plan is more than enough for what we’re about to build.
Step 2: Add a New Scenario
Once logged in, click the Create a new scenario button to start building your first automation.
Step 3: Add a Mailhook as Your First Module
Inside the scenario builder, click the big purple plus button and type Webhook into the search field. Pick the Webhooks option and then Custom Mailhook under Triggers.
Click the module you just added and add your mailhook by clicking Add and giving your mailhook a name. After that, a long email address appears below the box, which you can copy with the grey Copy address to clipboard button.
Any message forwarded to this address enters the automation, regardless of the original mail provider.
Step 4: Add a Notion Module to Your Automation
Click the half-circle next to your first module to add a second module. Search for Notion in the menu and pick the Create a database item option.
Step 5: Map the Relevant Information to Add Emails to Notion
If you’ve never used Make and Notion together, click Add under connection and authorise Make to access your Notion workspace by following the instructions.
Make sure to give Make access to the Notion page that contains the database where you want to store your emails. Then click Search, type in the name of your Notion database and pick it from the options.
Map each email field to the corresponding database property. Click into one of the fields and pick the information you want from the sidebar that appears.
Step 6: Set Up Automatic Rules for Emails to Forward (Optional)
Decide whether emails enter the workflow manually or through forwarding rules:
- Add the mailhook address from Step 3 to your address book and manually forward emails to it whenever you want to capture something in Notion.
- Set up forwarding rules to automatically capture certain emails (or all of them).
The specific steps depend on your email provider. The Gmail setup runs as follows.
First, open the Make scenario you just built and copy the mailhook address. Then right-click the webhook module and click run this module only.
Then log into your account and navigate to settings. In Settings, head to Forwarding and POP/IMAP and click Add a forwarding address.
In the popup, enter the mailhook address from your scenario and confirm that you want to forward to it.
Google will tell you it sent a test email to verify ownership. Head back to your Make scenario — it should have received the webhook, shown by a little bubble with a 1 above the webhook module. Click it to expand the details, expand the Text option under Output, find the confirmation code and copy it.
Navigate back to your Google account and paste the confirmation code. You can now use a filter to automatically forward emails to your mailhook. Click the filter icon next to the search bar.
Next, set up your condition, such as searching for specific keywords. Instead of clicking search, click Create Filter.
Check the Forward it option and select the mailhook address you just created from the dropdown.
Gmail will now forward every matching email to your scenario, and the scenario will add it to Notion. Turn on your Make scenario with the Scheduling button at the bottom of the scenario screen.
Trigger the forward from an automation. If you want more granular control than Gmail filters offer, fire the forward from another automation instead — on “starred an email,” for example, or any other available trigger.
Alternatively, if you don’t want to build an email-forwarding tool yourself, there are dedicated third-party email-to-Notion tools like TaskRobin.
How to Save Email Attachments in Notion
The personal mail connection reads everyday attachments, but this route is the one for large or cloud-linked files: it puts the file itself in Drive at any size and links it back to the email in Notion.
Create a separate Attachments database in Notion with these properties:
- File Name
- URL
- A Relation back to your email tracker database.
In your Make scenario, after the module that creates the email page in Notion, add a Google Drive → Upload a file module. It walks through the attachments on the incoming email and uploads each one to a folder you choose.
Then add a second Notion Create a database item module pointed at your Attachments database. Map the file name and the Drive link into File Name and URL, and set the Relation to the email page created in the previous step, so every file stays connected to the message it arrived on.
How to Extract Tasks From Emails Into Notion With AI
A stored email can still contain several pieces of information and several tasks. If you use a Task Manager in Notion, turn that email into individual tasks.
On Business or Enterprise, the fastest route is a skill: point Notion AI at the email and have it write the tasks straight into your task database, using the same skill structure shown in method 1. No API keys, no scenario to maintain.
Below is the Make version, which works on any plan and gives you full control over the model and the output format. For this build you need a simple Notion backend with two databases. Your email database saves the email itself:
- Subject
- Summary
- Sender
- Relation to the second database
Your tasks database needs only Task and a Relation back to the first database. You can map the same fields into an existing task or project system.
Step 1: Create a New Scenario
Create a new scenario in Make and add a mailhook module as explained in Step 3 above. Right-click the module, run this module only, and forward an email to the mailhook to make sure it works.
Step 2: Get Your OpenAI API Key
This automation uses OpenAI’s language models via their API. Anyone can sign up, and processing your emails costs a fraction of a cent each.
Head to OpenAI and create your account. Then click Settings in the top right corner and API Keys in the sidebar.
Create a new secret key and copy it somewhere secure. You’ll need it in a second and you won’t be able to view it again after closing the window. If you lose it, generate a new one.
Step 3: Clean Up the Email Data
Before asking OpenAI to summarise the email, clean up the data. Add a Text Parser module and choose the Replace function.
Remove all line breaks from the email by searching for the pattern \n and replacing it with a space or an empty string. Set the module to Global Match: Yes so it removes every line break, not just the first.
Step 4: Extract the Sender of the Email
To identify the person who sent the email, add another Text Parser module with the Match Pattern option. Use From:.*<(.*)> as your pattern to extract the sender address from the forwarded email, and set Global Match to No so it doesn’t match other addresses by accident.
Step 5: Let OpenAI Summarise Your Email
Now send the cleaned-up email to OpenAI. Make offers a pre-built OpenAI module (more on that below), but we’re going to use the HTTP module with Make a request to build a custom API call, which gives you full control.
- URL: https://api.openai.com/v1/chat/completions
- Method: POST
- Header — Name:
authorization, Value:Bearer YOUR OPENAI API KEY
Make sure you leave a space between the word Bearer and your token.
You don’t need any parameters in the query string. The second half of the module should be set to Body type: Raw, Content type: JSON (application/json), Parse response: Yes.
In request content, add the actual instruction for OpenAI. If you’re not familiar with writing API requests, copy the following and adapt it later using the OpenAI API documentation:
{ "model": "gpt-4o-mini", "messages": [{ "role": "user", "content": "You are an expert assistant. Summarize the following email forwarded to you by doing the following: ignore the forwarding header, summarize the email, provide a list of comma separated action items after the title ACTION ITEMS. Email: {{2.text}} SUMMARY:" }], "temperature": 0.5, "max_tokens": 200 }- model —
gpt-4o-miniis a fast, inexpensive option. Replace the model name when you choose a newer model. - content — the actual request. Modify the text to get different responses, but always ask for a comma-separated list of action items or the rest of the automation breaks. Replace
{{2.text}}with the mapped data from your cleaned-up email in Step 3. - temperature — how much creative latitude the model takes when interpreting your prompt.
- max_tokens — how much output the model may produce. 100 tokens is roughly 75 words; raise it for longer emails. Summarising an email costs a fraction of a cent on current models.
Test the build before moving on. Click Run once in the bottom left of the scenario screen and forward an email to your mailhook. The HTTP module should return a 200 status with your answer under Data → Choices → Text.
Troubleshooting
If OpenAI returns an error, read the response. If it says the JSON body is malformed, check that every quotation mark and comma matches the example and that the whole thing is wrapped in curly brackets.
If it’s still failing, the email itself probably contains quotation marks. Replace all double quotes ( ” ) with single quotes ( ‘ ) inside the email by wrapping the text in the HTTP module with a replace function, as shown below.
Using the Official Make OpenAI Module
Make also offers an official OpenAI module. You can swap the HTTP module for it — choose its chat-completion action and set up the same parameters described above.
Step 6: Extract the Tasks From Your Email
Add a Text Parser module, choose Replace and match ^.*: with an empty string. This strips everything up to the ACTION ITEMS label and leaves the comma-separated list. Turn on Global Match. The input is the response you got from OpenAI.
Step 7: File the Email in Notion
Add the Notion module Create a Database item and file the email in your email database. Map the subject line to the name field, the sender you isolated in Step 4 to the sender field, and the response from OpenAI as the summary. If you want to tidy up the subject line, add a small replace function as shown below.
Step 8: Create the Individual Tasks in Notion
Last step: add the individual tasks to Notion. First turn the comma-separated list into an array by adding an Iterator (under flow control) with a split function:
{{split(4.text; ",")}}The iterator then processes each element separately.
Finish by adding another Notion Create a Database item module. This time pick your tasks database, add the result of the iterator as the task name, and the email entry created in Step 7 as the relation.
For another practical AI workflow, see this AI Image Generator.
Frequently Asked Questions
Do I Still Need a Third-Party Tool to Get Email Into Notion?
For most jobs, no. On a Business or Enterprise plan, Notion reads, labels, drafts and sends email natively through skills and agents, attachments included — no middleware in the chain. You still need a third-party tool in three cases: when you’re on Free or Plus, when your volume makes per-run credits more expensive than a flat-rate automation, and when you’re moving large or cloud-linked files that exceed what the mail connection will read. Note that self-hosting the sync script from method 3 also removes the plan gate without bringing in a vendor.
Is Notion Mail Really Going Away?
Yes. The Notion Mail inbox app shuts down on 22 September 2026, and the native Notion Mail to Notion sync goes with it. Your email agents are not affected — Notion states that nothing changes if you’re already using agents for email, including ones that read, draft and send. If you connected an agent to Notion Mail specifically, move that connection to Gmail or Outlook before the date.
What’s the Difference Between the Workspace AI Connector and a Personal Mail Connection?
They’re different features in different settings screens. The personal Mail & Calendar connection (Settings → Account → Mail & Calendar) links your own accounts to your Notion AI and agents, which can then search your inbox, draft, send, fire on new-email triggers, read attachments and work with your calendar. You set it up yourself, you can connect several accounts, and no admin is involved. The Workspace AI Connector (Settings → Notion AI → AI Connectors) is set up once by a Google Workspace or Microsoft 365 admin who is also a Notion workspace owner, and it makes the whole organisation’s mail searchable for everyone — read and search only, no sending, no attachments. Both need Business or Enterprise. For an inbox assistant, you want the personal connection.
Can Notion AI Read My Email Attachments?
Through the personal Mail & Calendar connection, yes — PDFs, images and text files. Our product tests on 21 July 2026 put the practical ceiling at roughly 3 MB through the main mail connection and about 10 MB through the Gmail-specific reader; Notion documents neither figure. Through the Workspace AI Connector, no, and Notion’s documentation says so explicitly. Those doc pages are the source of the widespread belief that Notion can’t read attachments at all; they’re describing the admin-installed connector, not your personal one. For files beyond the size ceiling, or cloud-linked formats, use the Make method on this page, which uploads attachments to Google Drive at any size and links them back to the email in Notion.
I Followed Your Old Relay Guide — What Should I Do Now?
Relay.app shuts down on 15 August 2026 for free accounts and 14 September 2026 for paying customers, and new signups are already closed, so the old walkthrough can’t be followed end to end any more. Your Notion backend is fine — it’s only the automation layer that needs replacing. If you’re on Business or Enterprise, rebuild the workflow as a skill or agent (methods 1 and 2). If not, the Make method rebuilds the same thing, attachments included. Here’s why we now build automations as code.
Do I Need to Know How to Code to Get Emails Into Notion?
No. The skill and agent methods need zero code: you write clear instructions in plain English. For the full email-to-database sync, describe the result you want and direct an AI coding agent through the five-stage process.
Should I Use a Skill or an Agent for My Inbox?
Start with a skill. Running it yourself is included in your seat, so you can test the workflow without burning credits. Once you’ve confirmed it works and the job is something that should happen automatically — like labelling every incoming email — promote it to an agent so it runs in the background.
How Much Does It Cost to Run an Email Agent in Notion?
Custom agents run on Notion credits, an add-on priced at $10 per 1,000 credits. A mail-triage agent costs roughly 100 to 250 runs per 1,000 credits, so budget accordingly. If you run out, agents pause automatically until you top up. Keep costs down by filtering with plain inbox rules first, choosing a fast, cheap model, and only automating jobs that genuinely need to be hands-off.
Which Emails Should Actually Live in Notion?
Usually, keep only the information inside the email: the lead, task or invoice extracted into the right database. Sync the actual message only when you have a specific reason to keep the full thread, such as a shared client record.
Get the Free Email to Notion Template
Download the free Emails to Notion template for the linked Email Tracker, Attachments, Tasks and Contact CRM databases, plus the inbox skills from this guide.
💼 Rolling this out across a team introduces permissions, account policies and failure handling. Our Notion consultants can help design and implement that version.
