How to Integrate Your E-mails With Obsidian Using Webhooks

Saving incoming emails directly into an Obsidian vault is achievable by chaining three pieces together: a Make.com automation scenario, an email-to-Markdown conversion step, and an Obsidian plugin endpoint that writes files into your vault. The practical payoff is simple—messages forwarded to a custom webhook land as readable notes inside Obsidian, so they can be searched, linked, and processed alongside the rest of a knowledge base.

The workflow starts in Make.com (formerly Integromat). After signing in, a new “scenario” is created to connect apps. The first module is a “custom mail hook,” which generates a dedicated email address. Any email forwarded to that address becomes the trigger payload for the automation. Next, the scenario adds a transformation step that converts the email’s HTML content into Markdown. This matters because Obsidian works naturally with Markdown files, making the resulting notes easy to read and edit.

A third module sends the converted Markdown to Obsidian using an HTTP request. For the destination, the setup requires installing the Obsidian plugin called obsidian webhooks. The plugin needs authentication via an Obsidian sign-in token, obtained from obsidian-buffer.webapp, and then configured inside the plugin settings. Once enabled, the plugin provides a webhook URL. That URL is pasted into the Make.com HTTP module, along with a target path inside the vault (for example, a test folder and a filename like email.md). The HTTP request is configured to use POST, with a raw body and a text/plain content type.

After the scenario is assembled, it’s tested by running the scenario once and then forwarding a real email (e.g., from Ryan Holiday) to the custom mail hook address. The automation receives the forwarded message, converts it to Markdown, and posts it to the Obsidian webhook endpoint. In practice, the transfer completes quickly—reported as typically within five to six seconds. Make.com’s scenario history provides success indicators, confirming that the request was accepted and processed.

If the note doesn’t appear or won’t open in Obsidian, the transcript points to a common issue: the file extension. The webhook path must include the correct filename format (such as email.md). Without the .md extension, Obsidian may not recognize the file as a Markdown note.

Once configured correctly, the result is a new note created under the specified folder in the Obsidian vault—containing the forwarded email content in Markdown form. From there, the email can be read and processed like any other Obsidian note. The setup is summarized as: create a Make.com account and scenario, add a custom mail hook plus an HTML-to-Markdown module, send the result via an HTTP request to the obsidian webhooks plugin endpoint, then forward emails to the generated custom mail hook address to automatically store them in Obsidian.