How to Forward Gmail to Notion (Manual-First 2026 Guide)

If you manage client messages, receipts, support requests, or newsletters in Gmail, manually copying selected emails into Notion can become repetitive and easy to skip.

Moving away from Notion Mail? Use the focused Notion Mail transition guide first. It separates the shutdown export steps from this new-message Gmail-to-Notion workflow.

The good news? You can use a focused forwarding workflow for new messages. Mailsink gives you a private inbox address and a destination setup to test with one real email; the fields, content, and attachments available depend on your provider, destination permissions, and plan. No historical migration or full inbox client is implied.

This guide walks through a manual-first Gmail-to-Notion setup for CRM notes, support requests, receipts, newsletters, and similar workflows.

Why Forward Gmail to Notion?

Before the setup, decide which messages are useful enough to become Notion records.

The Problem with Manual Email Management

Copying messages by hand adds another step and can lose useful context such as sender, date, or the original body. A focused forwarding route is most useful when the destination database already has a clear job.

What You Gain with Automatic Forwarding

When you use a tested forwarding route from Gmail to Notion, new messages can become workspace records alongside related projects, contacts, and notes. Review the fields and content your destination receives, then shape the database around the workflow you actually need. Provider rules, destination permissions, and plan limits still apply.

What You'll Need

You need a Gmail account and a Notion workspace. Allow extra time to authorize the workspace, map fields, and test a real message; Gmail automatic forwarding also requires provider verification.

Having a clear use case in mind helps—whether that's building a CRM, tracking support tickets, organizing receipts, or any other email-powered workflow. Basic familiarity with Gmail filters and Notion database properties will make the process smoother, but we'll walk you through everything step by step.

Step 1: Set Up Your Notion Database

First, you need a Notion database to receive your emails. If you already have one set up, you can skip to Step 2.

Creating a New Email Database in Notion

1. Open Notion and navigate to the workspace where you want to store emails
2. Create a new database by typing /database and selecting "Table - Inline"
3. Name your database something like "Emails", "Client Communications", or "Support Inbox"

Essential Database Properties

Start with properties such as Subject (Title), From (Text), To (Text), Date (Date), and Body (Text). Mailsink's setup can create recommended properties when auto-create is enabled. Add an Attachments property only if attachment handling is available for your configuration and plan.

For workflow management, consider adding optional properties like Status (Select) for tracking workflow stages and Priority (Select) for categorizing importance. You can customize these properties later based on your specific workflow needs. Many users add properties like "Client Name", "Project", "Response Needed", or "Follow-up Date" to create more powerful email management systems.

Step 2: Connect Your Notion Workspace to Mailsink

Now let's set up the automation that will forward your Gmail to Notion.

Why Mailsink?

Mailsink provides a separate address for each inbox and maps forwarded message data into a chosen Notion database. Rendering, available fields, and attachment behavior depend on the message, mapping, destination permissions, and plan, so verify them with a real test before adding a broad rule.

Connection Steps

1. Go to Mailsink.app and create an account.
2. Open Connections and choose Connect Notion.
3. Authorize Mailsink to access the pages you select in your Notion workspace.
   • Select the pages Mailsink can access (choose the workspace where you want emails to live).
   • Click "Allow access".
4. Create an inbox from Inboxes.
   • Keep Email Inbox selected as the workflow and choose Notion as the destination.
   • Choose where emails should land:
     • Create a brand new Notion database directly from Mailsink, or
     • Link an existing database that already has the properties you want to use.
   • Keep the Auto-create properties toggle enabled for recommended fields, then confirm which properties were created. Configure attachment mapping only when it is available for your setup and plan.
5. Click "Create inbox". Mailsink verifies the connection, autoconfigures the database, and generates a unique inbox address (like abc123@in.mailsink.app).
6. Copy the generated inbox address — you'll use this for email forwarding.
7. Optional customization: Open the inbox drawer later and fine-tune mappings in the Email Content, Email Metadata, Attachments, or Thread Linking tabs. You can rerun autoconfigure at any time if you add new properties in Notion.

Important: Copy and save your inbox address — you'll need it in the next step!

Step 3: Set Up Gmail Forwarding

Now configure Gmail only after a manual forwarding test works. Gmail automatic forwarding has its own verification step, and the current Mailsink beta does not reliably surface the verification message sent to the destination address. Manual forwarding or BCC is the reliable starting path.

Method A: Forward ALL Emails

If you want every email to go to Notion (great for dedicated support or project email addresses):

1. Open Gmail settings by clicking the gear icon → "See all settings"
2. Click the "Forwarding and POP/IMAP" tab
3. Click "Add a forwarding address"
4. Paste your Mailsink inbox address and click "Next" → "Proceed"
5. Wait for Gmail's verification message at the Mailsink destination address (this beta does not reliably surface it in-app)
6. Only enable automatic forwarding after you can complete Gmail's verification step yourself; otherwise use manual forwarding or BCC
7. If verified, back in Gmail settings, select "Forward a copy of incoming mail to [your-address@in.mailsink.app]"
8. Choose what happens to Gmail's copy - Usually "keep Gmail's copy in the Inbox"

Method B: Forward Specific Emails (Recommended)

Most users prefer selective forwarding using Gmail filters. This gives you more control:

1. In Gmail, click the search bar and then click "Show search options" (the filter icon)
2. Set your criteria:
   • From: Specific email addresses (e.g., clients@company.com)
   • To: Specific recipient (e.g., support@yourcompany.com)
   • Subject: Keywords to filter (e.g., "invoice" or "support request")
   • Has the words: Additional filtering (e.g., "urgent" or project names)
3. Click "Create filter"
4. Check "Forward it to" and select your Mailsink address
5. Optional: Add labels, mark as read, or categorize
6. Click "Create filter"

Popular Filter Patterns

Here are some common filter patterns that work well for different use cases. For client emails, you can filter by sender domain using from:@client-company.com and forward those to your "Client CRM" database. For receipts and invoices, use subject:receipt OR subject:invoice to catch all financial documents and route them to your "Finance" database. Support requests sent to support@yourcompany.com can automatically go to your "Support Tickets" database, while newsletters from sources like Substack or Medium can be filtered with from:@substack.com OR from:@medium.com and forwarded to a "Reading List" database. The best part is you can create multiple filters for different use cases, giving you complete control over how emails are organized.

Step 4: Test Your Setup

Let's make sure everything works correctly:

1. Send a test email to the email address you've set up filtering for
2. Allow time for processing, then refresh Mailsink's activity view
3. Check your Notion database and confirm whether the test arrived
4. Review the fields and content available in your destination. Attachment behavior depends on provider, destination permissions, and plan limits.

Troubleshooting

If your email isn't showing up in Notion, first check that the Mailsink address is correct and inspect Mailsink's activity state. For missing attachments, check the mapping, file type, and plan limits. If the saved body is not useful, review the inbox's email-content mapping and test a simpler representative message. If Gmail's forwarding address is still unverified, use manual forwarding or BCC; the current beta does not reliably surface the verification message sent to the Mailsink destination.

Real-World Use Cases

Now that you've set up Gmail to Notion forwarding, here are some powerful ways to use it:

1. Client CRM

Forward selected client messages to a dedicated "Clients" database, then confirm which standard fields your mapping receives. Add properties such as company, last-contact date, status, and linked project. Optional AI extraction can populate configured fields, but should be tested against representative emails before you rely on it.

2. Support Ticket System

Test a support message with a "Support Tickets" database before routing a shared address. Add status, owner, and resolution fields in Notion. If you enable AI extraction, treat categorization and priority as suggestions until you have checked its results on your own ticket mix.

3. Receipt & Invoice Tracking

Forward a sample receipt to a "Finance" database and verify the body, fields, and any attachment before adding a rule. Optional AI extraction can attempt vendor, amount, or due-date fields; keep the original message as the source and review extracted financial data.

4. Job Application Tracker

Use a "Candidates" database for selected recruiting messages, with properties for role, stage, interview date, and notes. Verify how resumes and other attachments are handled in your plan. Optional AI extraction can attempt configured candidate fields, but a person should review hiring data.

5. Newsletter Archive

Setup: Forward newsletters to a "Reading List" database Properties: Source, topic, read status, highlights, saved for later Workflow: Build a searchable knowledge base from your favorite newsletters

Pro tip: Add tags for different topics to filter your archive.

Advanced Tips & Tricks

Multiple Inbox Addresses

You can create multiple inbox addresses in Mailsink, each pointing to different Notion databases. Each inbox gets a unique auto-generated address:

• abc123@in.mailsink.app → Client CRM database
• xyz789@in.mailsink.app → Support Tickets database
• def456@in.mailsink.app → Finance database

This lets you route different emails to different places automatically.

Gmail Filter Combinations

Get creative with filter combinations:

from:@client-domain.com AND subject:"Project Alpha"
→ Forward to "Project Alpha" database

from:orders@shopify.com
→ Forward to "Order Fulfillment" database

has:attachment filename:pdf AND subject:contract
→ Forward to "Legal Documents" database

Notion Database Views

Set up multiple views in your email database:

• Table view: See all emails in a list
• Board view: Group by status (To Review, In Progress, Done)
• Calendar view: Timeline of email communications
• Gallery view: Visual view of emails with attachments

Alternatives to Consider

While Mailsink is built specifically for email-to-workspace integration, here are alternatives:

• Manual copy and paste when only a few messages matter each month
• General automation tools when the workflow must coordinate several apps
• A custom script when you can own provider APIs, monitoring, and maintenance

Choose the smallest option that you can verify with a real message and maintain for the workflow.

Troubleshooting Common Issues

"My emails aren't showing up in Notion"

Checklist:

1. Verify your Gmail filter is active (Settings → Filters)
2. Check your Mailsink inbox address is correct
3. Check Mailsink's activity state for the test message
4. Test with a simple email (no attachments first)
5. If Gmail forwarding is not verified, use manual forwarding or BCC instead of assuming the rule is active

"Attachments are missing"

Solutions:

• Check your Mailsink plan for attachment size limits
• Check that the "Attachments" property exists in your Notion database
• Test the representative file types your workflow receives and confirm each result

"Email formatting is broken"

Fixes:

• Review the inbox's email-content mapping and the destination Body property
• Some complex HTML emails may not render as they do in Gmail
• Keep the original message as the source when formatting matters

"I'm hitting my email limit"

Options:

• Use filters to be more selective about which emails forward
• Check your Mailsink plan for current limits

Conclusion

Gmail-to-Notion forwarding is useful when selected new messages belong in a specific workspace workflow. Start narrow, verify the resulting record, and expand only after the route is reliable for your provider and data shape.

Your next steps:

1. Create your Notion email database (or use an existing one)
2. Sign up for Mailsink and connect your Notion
3. Manually forward one representative message
4. Review the saved fields, content, and any attachment
5. Add a Gmail rule only after forwarding verification is complete

Ready to get started? Create a Notion Email Inbox →

Frequently Asked Questions

Q: Can I forward from multiple Gmail accounts? A: Yes! Create separate Gmail filters in each account, all pointing to the same (or different) Mailsink inbox addresses.

Q: Will this delete emails from Gmail? A: No, Gmail keeps a copy unless you specifically tell it to delete forwarded emails (not recommended).

Q: Can I stop forwarding later? A: Absolutely. Just delete the Gmail filter or forwarding rule, and new emails won't be sent to Notion.

Q: Does this work with Google Workspace (G Suite)? A: It can work when the Google Workspace administrator permits the forwarding route. Organization settings can differ from personal Gmail, so verify the address and test the rule in the actual account.

Q: How do I forward only specific emails? A: Use Gmail filters (covered in Step 3, Method B) to forward only emails matching your criteria.

Q: Can I edit emails after they're in Notion? A: Yes, once in Notion, they're regular database entries you can edit, annotate, and enhance.

Q: What happens if I reach my email limit? A: New emails won't be processed until your monthly limit resets or you adjust your plan.

Last updated: September 1, 2026