Capturing actions from an Excalidraw whiteboard into your GTD workflow in Obsidian

TL;DR

Use Excalidraw as an action-capture surface by adding action lists directly to the canvas after the discussion, preserving context.

Briefing Cornell Notes

Briefing

Capturing workshop actions directly from an Excalidraw whiteboard into an Obsidian GTD workflow prevents the familiar failure mode: commitments get scribbled during a meeting, then drift into inboxes, photos, or “someday” notes—until they’re forgotten. The core idea is to embed action text inside Excalidraw in a way that turns into normal Obsidian tasks, so follow-ups happen as part of an established system rather than as an afterthought.

The workflow starts with treating the Excalidraw canvas as more than a sketching surface. During the workshop, teams use Excalidraw’s flexibility to rearrange ideas on an “infinite whiteboard,” which the creator found more practical than flip charts or post-it notes—post-its can fall off, are hard to pack, and usually end up as a photo-only record. After the discussion, actions are added to the chart itself so they remain in context with the decisions that produced them.

To make the action list usable, Excalidraw needs to be opened in Markdown mode. The process requires creating a text element to hold the actions, then switching to Markdown mode to edit that element. Because Excalidraw doesn’t wrap text automatically, action details are structured as bullet points nested under each action. This is where the GTD pattern comes in: each action entry begins with a tag that identifies the context (for example, “waiting for”), followed by the contact or person, then the deadline, and finally the action itself.

Once the action text is embedded in Excalidraw, it becomes standard Obsidian to-do items. The transcript then outlines three ways to access and manage those tasks inside Obsidian. First, a personal GTD plugin (not published to the community store) allows clicking to complete an action, which immediately marks it complete on the drawing as well. Second, a DataView approach uses a query based on a script by Chris Aliast (linked in the video description), enabling task retrieval through structured querying. Third, Obsidian’s built-in search can surface action details, with emphasis on learning the “task to do” and “task done” search filters to quickly separate open work from completed commitments.

The practical payoff is follow-through: actions and promises made during the workshop can be tracked over coming weeks using the same GTD workflow already used for everyday work. Instead of relying on memory, scattered notes, or email threads, the system keeps meeting agreements attached to tasks—reducing the chance that an action everyone cared about ends up in the recycle bin.

Cornell Notes

Excalidraw can be used as a meeting capture tool, not just a drawing space, by embedding action lists inside the canvas in Markdown mode. Actions are formatted as bullet points under each action and follow a GTD-style structure: a context tag, the person/contact, a deadline, and the action text. Once added, those entries become normal Obsidian to-do items that can be managed like any other tasks. Access options include a personal GTD plugin that syncs completion back to the drawing, a DataView query (based on a script by Chris Aliast), and Obsidian’s built-in task searches such as “task to do” and “task done.” This matters because it preserves meeting context and makes follow-up reliable.

Why does capturing actions on a whiteboard often fail, and what does this workflow change?

Actions written on a whiteboard or flip chart typically get separated from their context after the meeting—first into “eight minutes of meetings” notes, then into days or weeks of confusion, and eventually into a recycle bin. This workflow changes the outcome by placing action items directly into the Excalidraw canvas in a structured, GTD-compatible format, then turning them into Obsidian tasks so follow-up happens through an existing task system rather than memory or scattered notes.

What technical step makes Excalidraw actions usable inside Obsidian?

The key step is opening Excalidraw in Markdown mode. A text element must be created to hold the actions, then Markdown mode is used to edit that element. Actions are entered as bullet points because Excalidraw doesn’t wrap text, so the structure must be explicit to keep entries readable and parseable.

How are actions formatted to fit a GTD workflow?

Each action entry follows a consistent pattern: it starts with a tag to identify context (e.g., “waiting for”), then the contact/person, then the deadline, and finally the action itself. The transcript also notes that action details are placed into bullet points nested under each action to work around Excalidraw’s lack of text wrapping.

What are three ways to access and manage the resulting tasks in Obsidian?

(1) A personal GTD plugin lets the user click to complete an action and immediately marks it complete on the drawing. (2) DataView can retrieve tasks using a query based on a script by Chris Aliast (linked in the description). (3) Obsidian’s built-in search can filter tasks using “task to do” and “task done,” letting the user view open versus completed items and action details.

Why is Excalidraw preferred over flip charts or post-it notes for this use case?

Excalidraw’s flexibility supports rearranging ideas during the workshop, which is essential for interactive discussions. The transcript also highlights practical issues with post-its: they can fall off, are hard to pack afterward, and often leave only a photo record. Excalidraw, by contrast, retains editable content so actions can be added and managed after the workshop.

Review Questions

How does switching Excalidraw to Markdown mode enable action text to become Obsidian to-do items?
What GTD fields are included in each action entry, and why does the workflow use bullet points under each action?
Compare the three Obsidian access methods (plugin, DataView, and built-in search). What does each add to the workflow?

Key Points

1
Use Excalidraw as an action-capture surface by adding action lists directly to the canvas after the discussion, preserving context.
2
Open Excalidraw in Markdown mode and edit a dedicated text element to store actions in a structured format.
3
Format each action entry with a GTD pattern: context tag, person/contact, deadline, and action text.
4
Because Excalidraw doesn’t wrap text, place action details into bullet points nested under each action for clarity and consistency.
5
Convert the embedded action text into normal Obsidian to-do items so meeting commitments enter the same task workflow as everyday work.
6
Manage tasks in Obsidian using a plugin (with completion syncing), DataView queries, or built-in task searches like “task to do” and “task done.”
7
Track promises made during workshops over coming weeks by relying on Obsidian’s task system instead of photos, emails, or memory.

Highlights

Excalidraw actions become actionable Obsidian to-dos when the canvas is edited in Markdown mode with a dedicated text element.

A GTD-style action format (context tag → person → deadline → action) keeps workshop commitments structured and searchable.

Three access paths—plugin syncing, DataView querying, and Obsidian task search—turn the whiteboard into a living task system.

Excalidraw avoids the post-it problem of falling off and ending as an unsearchable photo-only record.