README file from
GithubEmail to Vault
Things worth keeping arrive by email — a receipt, a confirmation, a thread you want to think about — and getting them into Obsidian means copying, pasting and re-saving the attachments by hand. This plugin makes an email address the way into your vault: send or forward mail to it and each message becomes a note, with From, To, CC, Subject, Body and attachments preserved.
Use the built-in disposable mailbox (Mail.tm) for a one-click address that needs no account, or connect your own IMAP server — Gmail, Outlook, self-hosted — and keep everything on infrastructure you already trust. No backend and no paid service either way. Inspired by Save emails into Evernote.
Demo vault
The documentation is a demo vault. Every feature has a note explaining what it does and why you would want it, and walking you through it.
Start reading here — it is plain markdown, so it works on GitHub with nothing installed.
A copy of the vault ships with every release. You can access it via any of the following:
- Running the
Email to Vault: Open demo vault command. - Downloading
email-to-vault-demo-vault.zipfrom the Releases. It unzips into a singleemail-to-vault-demo-vault-<version>folder. - Browsing its source in
demo-vault/in this repository.
[!NOTE]
Unlike most demo vaults, this one cannot pre-bake its feature: it fetches real mail from a live service over the network. The notes walk you through configuring your own inbox instead.
What it does
- Two email modes — a disposable Mail.tm mailbox created in one click, or your own IMAP server. IMAP is desktop only; Mail.tm works everywhere. 01 Create a mailbox · 02 IMAP mode
- Automatic sync — the plugin checks for new mail periodically and saves each message as a note, with full metadata and attachments. 03 Email notes and commands
- Notes shaped the way you want — path and body come from templates, so an email can land anywhere under any name with whatever frontmatter you choose. 04 Settings
- Preserve read state — optionally leave messages untouched on the server, so they stay unread in your other email clients while still being archived here. 04 Settings
- Know where your mail goes. Mail.tm routes messages through a third party; IMAP does not. The difference is spelled out rather than buried. 05 Privacy and data handling
[!WARNING]
In Mail.tm mode, emails are routed through the third-party service mail.tm and retained there for up to 7 days. Do not send sensitive information — use at your own risk. See 05 Privacy and data handling.
See also
| Plugin | Features | How Email to Vault differs |
|---|---|---|
E-mail Importer (IMAP) |
Scheduled unread IMAP mail import; per-message notes and attachments | Same IMAP goal; ready-made mailbox option; note path/body templates |
Gmail Mailbox |
Gmail API; label/thread indexes; Calendar sidebar; own OAuth client required | Alternative integration: IMAP and ready-made mailbox; not Gmail-only |
Hints Flow |
Hosted assistant; Telegram, WhatsApp, Slack, email and SMS; capture templates |
Narrower focus: email-to-note; IMAP option |
mail-to-note |
Hosted personal address; attachment import; name pattern; account/API key | Same forwarded-mail goal; own IMAP account option and note body templates |
MailDump |
Scheduled IMAP folder exports; four accounts; digests and optional message notes | Alternative workflow: forwarded messages become individual notes |
Messager |
Hosted WeChat, HTTP and email capture; account required; paid advanced features | Narrower focus: email-to-note; IMAP option |
Obsidian Email Plugin |
Unlisted alpha; self-hosted SMTP receiving service | Same email-to-note goal; ready-made mailbox or IMAP instead of self-hosted SMTP |
Outlook Teams and Calendar |
Microsoft Graph mail, events and Teams; desktop-only; Azure app required | Narrower focus: email-to-note; no Teams/calendar integration |
Send Email into Vault |
Hosted private address; attachments; desktop/mobile; paid after trial | Same forwarded-mail goal; ready-made mailbox or own IMAP account |
Sync Emails |
Hosted forwarding alias; manual sync; attachments; subscription after trial | Same forwarded-mail goal; IMAP option and scheduled imports |
Last searched for similar plugins on 2026-10-26.
Installation
The plugin is available in the official Community Plugins repository.
Beta versions
To install the latest beta release of this plugin (regardless if it is available in the official Community Plugins repository or not), follow these steps:
- Ensure you have the BRAT plugin installed and enabled.
- Click Install via BRAT.
- An Obsidian pop-up window should appear. In the window, click the
Add pluginbutton once and wait a few seconds for the plugin to install.
Debugging
By default, debug messages for this plugin (id: email-to-vault) are hidden.
If you need to enable them refer to the documentation.
Changelog
All notable changes to this project will be documented in the CHANGELOG.
Contributing
Contributions are welcome — see CONTRIBUTING to get set up.
Support
Filing an issue (for AI agents and humans)
Open issues through the issue forms, not as blank issues.
To report a bug from inside Obsidian, run the Email to Vault: Report a bug command. It opens the bug form with the plugin version, the Obsidian version and your operating system already filled in.
Filing from the CLI or the API (gh issue create --body, or an AI agent filing for you) skips the form, and gh issue create --template cannot load an issue form. In that case, open the matching form in .github/ISSUE_TEMPLATE/, copy every field as a ### <label> heading in the form's order, and fill in each one. Always state the plugin version, the Obsidian version and your operating system.