In my previous blog post, I discussed my use of Obsidian, a powerful note-taking tool that allows for a personal knowledge base built from Markdown files, in both my personal and professional life. However, while Obsidian is an incredible tool, it faces challenges in the corporate environment, particularly where Microsoft Office and other traditional suites are prevalent. Many professionals find it difficult to integrate their note-taking and task management within Obsidian when these systems dominate their workflow.

Fortunately, there’s a way to bridge this gap by connecting your Obsidian Vault with Microsoft Office using Power Automate and OneDrive.

Tools for Integration: Power Automate and OneDrive

Utilizing OneDrive is not unexpected; it serves as a critical component in many Office-based workflows and is a Microsoft service well known and widely used. To ensure that your Obsidian Vault functions smoothly within an Office context, it’s essential to store it in a OneDrive folder.

On the other hand, Power Automate is a robust solution that, while not as universally recognized, serves as a workflow automation platform. In simple terms, Power Automate functions as a workflow engine, enabling connections between numerous Microsoft and third-party services to automate tasks. This system offers functionality for data transfer, automated scheduling, and even intricate approval processes within your Microsoft environment.

Example Flow: Add Flagged Mails as Tasks to Obsidian

Let’s examine a practical use case: transferring flagged emails from your Microsoft Inbox into your Obsidian Vault as tasks. Here’s how the steps of this Power Automate flow can be outlined…

When an email is flagged in your Inbox, this acts as the trigger for your automation. However, depending on your specific needs, you might also choose different triggers, such as when a new email arrives, a calendar event is created, or a planner task is assigned.

Personally, I have 3 flows (with 3 different triggers) collecting tasks from my Microsoft environment and transfer to Obsidian as a task:

1. When an Email is flagged
2. When a Planner task is assigned
3. When a Message in Teams is flagged

As the trigger might be different pending on your use case most of the rest of the flow, the core logic stays the same.

As you build your flow, the next step involves initializing the necessary variables—like the task name and the URL linking back to the email in the Office web applications.

For instance, to construct a navigable URL for an email, you can use the following JavaScript snippet:

concat('https://outlook.office.com/owa/?ItemID=',variables('MailMessageId'),'&viewmodel=ReadMessageItem&path=&exvsurl=1')

The task I want to add to Obsidian is a simple string I want to later append to a Markdown file. I construct the task as follows:

concat('- [ ] Mail: ', variables('MailSubject'), ' [Link](', variables('MailUrl'),') #inbox #mail 📅 ', formatDateTime(utcNow(), 'yyyy-MM-dd'), decodeUriComponent('%0A'))

This is in a nutshell basically all that is required. We can bring the different components together:

You are reading out the OneDrive markdown where you want all your Microsoft Office tasks to go to via a special action available in Power Automate:

You append the string (Markdown task) which was constructed before and overwrite your new string to the same file - voila! That’s all what is required.

Summary

In summary, by understanding these flows and variables, you can successfully integrate your task management needs from Microsoft Office into your Obsidian Vault.

One Final Remark

To prevent race conditions while reading and writing files in OneDrive, I recommend setting the parallelism in the Automate Flow trigger to 1. This ensures even during rapid task creation—such as quickly flagging several emails—that Power Automate flows do not attempt to modify the same OneDrive file simultaneously.