Using the Obsidian Quick Add Plugin

TL;DR

QuickAdd’s core unit is a configurable “choice,” which can be a template, capture, macro, or multi-step folder-like structure.

Briefing Cornell Notes

Briefing

Obsidian’s QuickAdd community plugin earns its keep not by making note-taking easier, but by automating repeatable actions—turning “a few clicks” into one hotkey. After installation and enabling, QuickAdd centers everything around “choices,” which are configured elements that can create notes from templates, capture text into existing files, or run multi-step macros. The payoff is speed and consistency: meetings, daily logging, and task capture can all follow the same structure every time.

QuickAdd’s first major building block is **Template**. A template choice can create a new note using a specified template file and a controlled filename format. In the walkthrough, a “Add New Default Meeting” template choice is configured to prompt for a meeting name while embedding the date (year-month-day) into the filename. It also targets a dedicated folder (a “meetings” directory) and controls how the created note opens—optionally in a new tab or pane so the current work stays intact. The workflow becomes even faster when the template choice is converted into a QuickAdd command via the lightning-bolt option, letting users trigger it directly from Obsidian’s command palette or assign a hotkey.

The second building block is **Capture**, designed for adding content without opening or leaving the current note. For daily logging, a “Capture - Log in Daily Note” choice captures entries into the correct daily note file (creating it if needed) and inserts them into a specific section—such as a “log” heading—rather than dumping text at the end. The capture format is tailored to the user’s needs: in this case, a bullet with a timestamp (date plus HH and minute) so entries remain chronological and scannable. The same capture mechanism is reused for meeting agendas tied to specific people.

For recurring meetings, QuickAdd can capture into a person’s existing note. A “Capture - Add to agenda with Pepe” choice targets the “Pepe” file inside a “people” folder, formats the captured item as a task, and inserts it into the “agenda” section at the end—without opening the file. That means a user can quickly add “remind him to ask Mark about project X,” then later open Pepe’s note to see a ready-made agenda.

The most advanced option is **Macro**, which chains multiple steps—captures, templates, and even Obsidian commands—into one action. A standout example automates content creation from a Kanban board: when a card is added, the macro captures the idea into the Kanban “raw” section, prompts for a title, then creates a new note using a specific template (placed into the right folder). The macro also reuses the same title input across steps, avoiding duplicate typing. Once assigned a hotkey, the entire flow runs from anywhere in the vault, producing correctly formatted notes and Kanban updates in one shot.

Overall, QuickAdd’s value comes from modular automation: start with templates and captures for immediate wins, then graduate to macros when the workflow demands multi-step consistency across plugins like Kanban, Data View, Buttons, and Templater.

Cornell Notes

QuickAdd turns Obsidian note-taking into automated workflows by using configurable “choices.” **Template** choices create new notes from a template file, with controlled filenames (like date-based meeting names) and predictable placement in folders. **Capture** choices insert text into existing files—such as daily notes or a specific person’s agenda—without disrupting the current note, including insertion into named sections and custom timestamp/task formats. **Macros** chain multiple steps (capture into Kanban, prompt for a title, then create a templated note) so one hotkey can update boards and generate ready-to-use notes. This matters because it reduces repetitive work while enforcing consistent structure across meetings, logging, and task management.

What does QuickAdd mean by a “choice,” and why does that matter for automation?

In QuickAdd, anything configured in the options area is treated as a “choice.” The terminology is unusual, but the practical point is that each choice can be one of several types—**template**, **capture**, **macro**, or **multi**. Once a choice is set up, it can be triggered via the command palette and even assigned a hotkey, turning a multi-step workflow into a single action.

How does the “Template” type help standardize meeting notes?

A template choice can create a new note using a specified template file and a filename pattern. In the meeting example, the “Add New Default Meeting” choice prompts for a meeting name while embedding the date in the filename using a double-bracket date format (year-month-day). It also forces the note into a dedicated **meetings** folder and can open the created file in a new tab/pane so the current note isn’t replaced.

Why is “Capture” better than manually editing a daily note when logging mid-day?

Capture is designed to add content without opening the daily note or leaving the current context. The daily logging setup creates (if needed) the correct daily note file based on date, then inserts the entry into a specific section—like the **log** heading—using an “insert after” setting. The capture format can be customized to match the user’s style, such as a bullet with a timestamp (date plus HH and minute).

How can QuickAdd keep meeting agendas tied to specific people?

By creating a capture choice that targets a single existing person note. The “Capture - Add to agenda with Pepe” example captures into the **Pepe** file (under the people folder), formats the entry as a task, and inserts it into the **agenda** section at the end. The file doesn’t need to be opened at capture time; the agenda is ready when the person’s note is reviewed.

What makes a QuickAdd “Macro” different from using template and capture separately?

A macro chains multiple steps into one action. In the Kanban-based example, the macro first captures the idea into the Kanban board’s **raw** section (a markdown section), prompts for a title, then creates a new note using a specific template (the NVDH template) in the correct folder. It also reuses the same title input across steps, so the user types once and the macro applies the value to both the task name and the filename.

How does the lightning-bolt option change day-to-day usability?

Enabling the lightning-bolt for a configured choice creates a dedicated command for that choice. Instead of running QuickAdd and selecting the choice each time, the command appears directly in Obsidian’s command palette and can be assigned a hotkey (via Settings → Hotkeys). This reduces friction and makes automation feel instantaneous.

Review Questions

How would you configure a Template choice to include a date in the filename and ensure notes land in a specific folder?
What settings would you use in a Capture choice to insert a log entry under a named heading rather than at the end of the file?
In the Kanban macro example, how is the user’s title input reused across steps to avoid duplicate typing?

Key Points

1
QuickAdd’s core unit is a configurable “choice,” which can be a template, capture, macro, or multi-step folder-like structure.
2
Template choices can create new notes from a template file while enforcing filename formats (including date) and folder destinations.
3
Capture choices add content to files without opening them, supporting insertion into specific sections like a “log” heading or “agenda” block.
4
Capture formats can be customized for timestamped bullets or task-style entries, keeping logs and agendas consistent.
5
Macros chain multiple actions—such as updating a Kanban board and generating a templated note—into one hotkey-driven workflow.
6
Turning a choice into a QuickAdd command (via the lightning-bolt) enables direct command-palette access and hotkey assignment, cutting repeated clicks.
7
QuickAdd becomes more powerful when combined with other plugins (e.g., Kanban, Data View, Buttons, Templater) to match a specific workflow end-to-end.

Highlights

QuickAdd’s real value is automation: templates, captures, and macros turn repeatable note actions into hotkey-triggered workflows.

Meeting notes can be generated with a date-based filename pattern and routed into a dedicated meetings folder, optionally opening in a separate pane.

Daily logging can be captured into the correct daily note and inserted under a specific “log” heading with timestamped bullets—no need to switch notes.

A macro can take a Kanban card idea, insert it into the board’s markdown “raw” section, then create a new templated note using the same title input.

Capture into a person’s agenda note (like Pepe) keeps meeting prep efficient by storing tasks where they’ll be reviewed later.

Topics

QuickAdd Choices
Template Notes
Capture Logging
Meeting Agendas
QuickAdd Macros