I Replaced My Notion Templates with Buttons
Based on Irfan Bhanji's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Templates pre-populate complete pages, while buttons trigger targeted actions like inserting blocks and updating properties.
Briefing
Notion “buttons” replace repetitive template workflows by letting users trigger prebuilt actions inside a page—often with less friction than creating and managing new template pages. Templates still pre-populate entire pages on demand, but buttons can insert blocks, edit properties, and even generate new database entries with a single click, making them better suited for repeatable checklists and daily routines.
Templates work by storing a page layout that can be opened and pre-filled. In a PKM dashboard, hovering over “recent notes” reveals saved templates; selecting one (like a “booknotes” template) instantly creates a new page already categorized and filled with predefined fields and sections. The result is a ready-to-edit note where metadata and content prompts (e.g., “metadata,” “Kindle highlights,” and summary bullet points) are already in place.
Buttons, by contrast, act like mini-templates that run actions on the current workspace context. A practical example is an “edit checklist” button used before publishing an article. Instead of creating a fresh template page every time, the user bookmarks a single checklist page in Chrome and clicks the button. The click automatically inserts the checklist blocks, sets a property (changing a “note type” field to “note”), and provides a structured workflow: check items, run Grammarly and Hemingway editor steps, read the article out loud, then publish. After publishing, the checklist content is deleted and the same button can be reused immediately.
Creating a button is done via Notion’s slash command (“/button”), where the user defines an emoji label (e.g., a briefcase) and configures the action. The key action used here is “insert blocks,” along with formatting and property updates (such as adding an H2 section header and a to-do list, then setting the “note type” property). The button can also open pages, show confirmations, or edit properties—enabling workflows that feel more like automation than static page layouts.
The workflow expands further with nested and multi-step button systems. On a homepage “new daily note” button, clicking generates a new page inside a “daily note” database, names it with a date (e.g., “daily note 2023”), and opens it in full screen. Inside that daily note, additional buttons create structured “game plan” content and even an “anxiety/unblock” layer for task clarity. The system also records the exact time the note was created.
Buttons can be combined with templates for flexible “building blocks.” A “default note” uses toggles containing ready-made sections like pros/cons and outlines, allowing users to drag in formatted structures without committing to a single rigid template path.
Finally, buttons can break complex templates into sequential steps. A “video template version 4” uses multiple buttons (title/thumbnail, script template, and upload checklist) so a creator can build a YouTube workflow one stage at a time, keeping the page clean by tucking sections into toggles. Overall, buttons are positioned as a more modular, reusable alternative to templates—especially for checklists, daily planning, and multi-stage content production.
Cornell Notes
Notion buttons function as mini-templates that run actions—like inserting blocks and updating properties—without forcing users to create or open a whole new template page each time. Templates are best for pre-populating complete pages (e.g., a “booknotes” page with metadata and highlight prompts). Buttons shine for repeatable workflows such as an “edit checklist” before publishing, where one click inserts the checklist, sets “note type,” and supports a consistent proofreading routine. More advanced setups generate new database entries (like creating a dated “daily note” page in full screen) and can be nested for multi-step planning. Buttons can also be wrapped around templates or used to split heavy templates into sequential stages, keeping pages tidy via toggles.
How do templates differ from buttons in practical use?
Why does an “edit checklist” button feel simpler than a template page for publishing?
What does setting up a button typically involve in Notion?
How can buttons generate new pages inside a database?
How do buttons help manage complex workflows like video production?
What does it mean to wrap buttons around templates or building blocks?
Review Questions
- When would a full-page template be the better choice over a button-based workflow?
- Describe a scenario where inserting blocks and editing properties via a button would save time compared with opening a template page.
- How do nested buttons (buttons inside a newly created daily note) change the way a user plans a day?
Key Points
- 1
Templates pre-populate complete pages, while buttons trigger targeted actions like inserting blocks and updating properties.
- 2
A single reusable checklist page can be more efficient than creating a new template page for every publishing cycle.
- 3
Buttons are created with “/button,” configured with an action (often “insert blocks”), and can include formatting plus property changes.
- 4
Buttons can generate new database entries and open them in full screen, enabling dated daily-note workflows.
- 5
Nested buttons support multi-layer planning (e.g., daily note → game plan → unblock/anxiety clarity).
- 6
Buttons can be combined with template-like building blocks (toggles) to keep notes flexible when the structure isn’t known upfront.
- 7
Breaking heavy workflows into sequential button steps (with toggles) keeps pages clean and reduces decision fatigue during creation.