Notion Mail is shutting down on 22 September 2026. If you relied on it to turn email into Notion database entries, Mailhooks picks up where it leaves off — and goes further.
Every incoming email becomes a structured Notion database page in seconds: rich formatting preserved, properties mapped to your schema, attachments linked. No forwarding services, no Gmail-only limits.
Notion has announced that the Notion Mail inbox is going away. Export your Notion Mail–only data by 21 September 2026. Your emails remain in Gmail, and Notion’s Gmail/Outlook connections continue — but nothing that pipes new, incoming email into a Notion database replaces it.
Notion Mail’s database-sync view was the only first-party way to turn incoming email into Notion database entries automatically. It has no replacement inside Notion. Mailhooks does exactly this natively: authorize your workspace, pick a database, map fields — done.
Many teams used Notion Mail as a focused client over their Gmail. That need doesn’t disappear — but if your goal was “important emails organized into Notion automatically,” routing them into a database beats re-reading another inbox. Everything lands as structured, filterable pages your team already lives in.
Snippets and auto-label rules configured in Notion Mail stop working. In Mailhooks, each mailhook address routes to whatever destination you choose — a Notion database, a webhook, Discord, or n8n — so the routing logic lives outside a single product.
| Capability | Mailhooks | Notion Mail |
|---|---|---|
| Email into a Notion database | ||
| Status | Active | Shutting down 22 Sept 2026 |
| Receives email from anyone | ||
| Custom domain inbound (MX) | 250 domains on Pro | |
| Works without connecting your Gmail account | ||
| Property mapping (sender → field, subject → title) | ||
| Attachments stored and linked in Notion | ||
| Webhook / API access to raw email | ||
| Discord, n8n, webhook destinations | ||
| 365-day retention independent of your mailbox | ||
| Free tier | 100 emails/mo | Discontinued |
Authorize Mailhooks against your workspace and pick the database that should receive your emails. Required properties are created automatically — your existing data is untouched.
Sender → Email, Subject → Title, received date → Date, status → Status. You control the schema, and multiple hooks can feed different databases (invoices here, newsletters there).
Every hook gets its own address. Forward from Gmail with a filter, hand the address to senders directly, or point a custom domain at it via MX. Emails appear as Notion pages within seconds of arrival.
Notion Mail only saw your connected Gmail. Mailhooks receives from anyone — customers, forms, billing systems, monitoring alerts — straight to MX.
Beyond Notion, every email is available as clean JSON via webhook, API, SSE push, or IMAP — so the same inbound stream can power automations elsewhere.
Receive at [email protected] instead of a forwarding address. Up to 250 domains on Pro, with deliverability handled for you.
Emails and attachments are stored independently of your mailbox — 365-day retention on Pro — searchable and downloadable even after you archive from Gmail.
Depends on which part of Notion Mail you actually used:
You automated email into databases — Mailhooks is a direct, more powerful replacement. Custom domains, field mapping, attachments, and retention that Notion Mail never had.
You mainly wanted triage and labelling inside Notion — Notion’s own Gmail/Outlook connections survive the shutdown, and may cover lighter needs on their own.
You want a plain forwarding service — cheaper tools exist (TaskRobin, Quicktion), but they’re forwarding-only, Gmail-scoped, or volume-capped at a few hundred emails/month.
Simpler inbound email webhooks vs Mailgun’s full platform
Better DX for email webhooks vs SendGrid
Modern alternative for inbound email webhooks
Standalone inbound without the outbound requirement
Purpose-built inbound vs Resend’s newer inbound beta
Deep dive on turning incoming email into Notion database entries