Set up a POWERFUL Obsidian Task and Time Management System with Morgen

A new integration between Obsidian and Morgen turns plain-text markdown tasks into something you can actually plan like a calendar workflow—dragging tasks onto specific times, syncing due dates, and keeping task status consistent across notes. The core payoff is “best of both worlds”: tasks live in Obsidian where they’re easy to write, link, and structure, but they also appear inside Morgen where scheduling and day planning happens with minimal friction.

Instead of manually copying tasks into a calendar, the setup relies on Obsidian’s Tasks plugin plus a few required task properties. Each task needs a unique ID (so Morgen can match it reliably), a due date, and a priority. With those fields added, Morgen can import tasks from an Obsidian vault (either all tasks or only those modified recently, and optionally only tasks that already have IDs). After connecting the vault, tasks show up in Morgen with their note source and metadata, and planning becomes a drag-and-drop exercise: move tasks onto the calendar, adjust due dates, resize time blocks, and open the originating Obsidian note directly from a task.

The workflow then expands beyond basic syncing. A global hotkey capture system lets users add tasks into any Obsidian note without switching contexts. That requires QuickAdd for capture formatting, plus supporting plugins to generate unique timestamps and to interpret natural-language dates. The result is a one-keystroke pipeline: choose (or auto-create) the right section in a note, insert a task name, assign a priority preset, and attach a due date like “tomorrow”—with Morgen reflecting the new task once the ID and due date rules are satisfied.

For project planning, the tutorial emphasizes writing tasks as normal markdown—lists, sublists, links, and nested structure—then using the Outliner plugin to move through that hierarchy quickly. Outliner adds hotkeys for toggling checkboxes, creating list items, and moving tasks up or down while preserving parent/child relationships. Folding and unfolding nested lists helps manage large backlogs without losing structure.

To handle real-world task states, the setup goes further with Multi-State Checkboxes, defining statuses such as not started, in progress, canceled, and completed (and even an optional “question” state). Morgen’s display behavior depends on how the Tasks plugin maps those symbols to task types, so the configuration determines which statuses appear in Morgen when due dates are involved.

Finally, the system is used for both simple scheduling and more complex planning. A podcast project example shows how AI can generate a markdown task plan with time estimates, optional/interactive statuses, and nested subtasks. The user then copies the markdown into Obsidian, cleans it up, and schedules only what fits a realistic daily capacity (often around two hours per day). The day-to-day loop becomes: check Morgen’s due items, drag tasks into time blocks, open the corresponding Obsidian checklist, and mark items complete—keeping planning and execution tightly connected.