Prompt Library

Notion Setups That Actually Get Used

20 copy-paste prompts

20 ChatGPT prompts for database schemas, formulas, templates, dashboards, and workflows — built so your Notion actually runs your life instead of being a pretty graveyard.

Templates & Setup

5 prompts

Notion Workspace Architect

1/20

Design my Notion workspace from scratch. My role: [describe]. What I need to manage: [list areas — projects, tasks, notes, goals, people, etc.]. Team size: [solo / team of X]. Design: (1) top-level page structure (5-7 main hubs max), (2) databases vs pages for each area, (3) relational links between databases, (4) what NOT to put in Notion (tools that do it better), (5) a daily/weekly usage ritual that keeps the system alive, (6) migration plan from my current tools.

Designs a complete Notion workspace with page hierarchy, database relations, and a usage ritual that prevents abandonment.

💡

Pro tip: The #1 reason Notion workspaces die: too many databases trying to track everything. Start with 3-5 core databases (Tasks, Projects, Notes) and expand only when you feel the real pain of missing one. Over-architecting kills adoption.

Project Management Template

2/20

Build a project management template in Notion for [describe projects — marketing campaigns, software sprints, events, etc.]. Team size: [number]. Create: (1) a Projects database with essential properties (status, owner, deadline, priority, tags), (2) a Tasks database related to Projects, (3) views for each stakeholder (PM view, team view, executive view), (4) automation opportunities (buttons, templates, formula-based statuses), (5) meeting notes integration, (6) archive strategy for completed work.

Builds a complete PM template with database relations, role-specific views, automation, and archival.

💡

Pro tip: Notion's relation property is what makes it a real project management tool. Projects → Tasks → Meetings → Notes, all linked. Flat task lists without relations are just prettier versions of sticky notes.

Second Brain / PKM Setup

3/20

Build a Notion-based second brain / personal knowledge management system. My capture habits: [describe where I save notes now]. My output needs: [writing, teaching, decisions]. Design: (1) a Notes database with properties (type, topic, source, status, related), (2) a PARA or LATCH-style organization, (3) quick-capture workflow (Notion widget, Web Clipper, mobile), (4) weekly review ritual, (5) how to surface old notes when relevant, (6) what to keep vs let die.

Designs a PKM/second brain system with capture workflow, organization, weekly review, and surfacing strategy.

💡

Pro tip: Second brains fail because capturing is easy but retrieving is hard. Design the retrieval system first (how will I find this in 6 months?) then the capture system second. No tags, no taxonomy, no system = notes cemetery.

Habit Tracker Template

4/20

Build a habit tracker in Notion. Habits I want to track: [list 5-10]. Tracking frequency: [daily / weekly]. Create: (1) a database design that supports checkboxes + streaks, (2) formula for current streak and longest streak, (3) weekly review template showing my consistency, (4) visual progress via bar charts or progress bars, (5) a reflection prompt for weekly reset, (6) home page widget showing today's habits. Simple > fancy — must take under 60 seconds daily.

Builds a habit tracker with streak formulas, weekly review, and a home page widget designed for 60-second daily use.

💡

Pro tip: Habit trackers in Notion fail when daily logging takes more than 60 seconds. Make it one click. If you can't complete your daily log during a toothbrush session, the system will die within 3 weeks.

Client / Customer CRM

5/20

Build a lightweight CRM in Notion for [describe business]. Client count: [estimate]. Deal stages: [list]. Create: (1) a Contacts database with properties (stage, company, value, next step, last contact), (2) an Interactions database related to Contacts, (3) Kanban view by stage, (4) calendar view of next steps, (5) a follow-up automation (formula + manual check), (6) when to graduate to a real CRM (Hubspot, Pipedrive) and what to export.

Builds a lightweight Notion CRM with contacts, interactions, Kanban, calendar views, and a graduation plan to dedicated CRMs.

💡

Pro tip: Notion CRMs work great up to ~100 active contacts. Past that, you need real CRM features (email sync, call logging, pipeline analytics). Don't force Notion to be Salesforce — use it for the 80% solopreneur use case.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Databases & Formulas

5 prompts

Database Schema Designer

6/20

Design a Notion database schema for [describe what I'm tracking]. Core entities: [list]. Relationships: [describe]. Deliver: (1) database structure with all properties and types (text, select, multi-select, relation, formula, rollup), (2) relation + rollup combinations to avoid redundancy, (3) views per use case (Table, Board, Calendar, Timeline, Gallery), (4) filters and sorts for each view, (5) what NOT to track (avoid data bloat), (6) migration path if I outgrow Notion's database model.

Designs complete database schemas with properties, relations, rollups, and purpose-driven views.

💡

Pro tip: Notion databases become bloated when people track too many properties. 5-8 properties per database is the sweet spot. If you need more, you probably need a second database with a relation — not more columns.

Formula Builder

7/20

Write a Notion formula to [describe what I want]. Available properties in my database: [list with types]. Deliver: (1) the formula in Notion's formula syntax (2.0 if available — supports if/then, let, concat cleanly), (2) explain each part, (3) edge cases handled (empty values, divide-by-zero), (4) a simpler alternative if possible, (5) how to display the result nicely (text, number with format, emoji, etc.). Bonus: suggest related formulas I might want.

Builds Notion formulas with edge-case handling, version-aware syntax, and display formatting.

💡

Pro tip: Notion Formula 2.0 is a massive upgrade — let/if/switch/ifs, typed dates, array methods. If you're still writing formulas with nested prop() calls, learn Formula 2.0. Cleaner, faster, easier to debug.

Rollup Master

8/20

Help me use rollups effectively for [describe scenario]. Related databases: [describe]. What I want to roll up: [count, sum, average, latest, earliest, all values]. Deliver: (1) the exact rollup configuration, (2) when to use rollup vs a formula that does it, (3) how to handle filtered rollups (e.g., "only active tasks"), (4) performance considerations (rollups are slow on huge databases), (5) a dashboard-friendly display using rollups, (6) common gotchas to avoid.

Configures rollups for counts/sums/aggregations across related databases with filtering and display optimization.

💡

Pro tip: Rollups are Notion's most underused feature. Calculated property based on related items — "how many open tasks does this project have?" updates automatically. Most "I need a spreadsheet" moments in Notion actually need rollups.

Status Automation

9/20

Automate status changes in my Notion database. Current manual process: [describe what triggers a status change]. Rules: [describe logic]. Deliver: (1) formula-based status automation where possible, (2) button-based automation for manual triggers, (3) Notion Automations (if on paid plan) for property-based changes, (4) third-party tools (Make, Zapier) for complex logic, (5) a sanity check on whether automation is worth it vs just eyeballing it.

Automates status changes via formulas, buttons, Notion Automations, or external tools like Make/Zapier.

💡

Pro tip: Automation only pays off when the manual process is truly repetitive. If you change status once a day, don't automate. If it's 20 times a day, absolutely automate. Count first, build second.

Relation + Rollup Dashboard

10/20

Build a dashboard that aggregates data across multiple related databases. Databases involved: [list]. What the dashboard should show: [describe KPIs]. Deliver: (1) each KPI's formula or rollup, (2) how to display on a single page (linked databases, views, toggles), (3) filter controls for date ranges or entities, (4) visual design (headings, dividers, columns), (5) mobile-friendly considerations, (6) update frequency and when to manually refresh.

Builds a cross-database dashboard using rollups and relations, with filter controls and mobile-safe layout.

💡

Pro tip: Notion dashboards load slowly when they have 20+ linked databases. Trim ruthlessly — show only the 5-7 KPIs that matter. Everything else belongs one click away, not on the main screen.

Workflows & Rituals

5 prompts

Daily Dashboard

11/20

Design my Notion daily dashboard / home page. My top priorities: [describe]. What I need to see every morning: [list]. Create: (1) page layout with clear sections (Today, This Week, Waiting On, Quick Capture), (2) linked database views showing only today-relevant items, (3) daily rituals at the top (intentions, quick wins), (4) quick-capture buttons for tasks, notes, ideas, (5) closing ritual for end-of-day review, (6) how to keep it from getting cluttered over time.

Designs a daily command center dashboard with morning intentions, today views, quick capture, and evening review.

💡

Pro tip: Your daily page is the front door to your system. If it takes more than 10 seconds to find what you need, your system isn't working. Test by asking: "Can I start my day in under 5 minutes here?"

Weekly Review Template

12/20

Create a weekly review template in Notion. Areas to review: [work, health, relationships, finances, personal — adjust]. Structure: (1) review questions per area (what worked, what didn't, what's next), (2) stats auto-populated from other databases (tasks completed, habits consistency), (3) notes on patterns / lessons learned, (4) next week's top 3 priorities, (5) celebration section for wins, (6) archive so I can look back at past weeks.

Builds a structured weekly review template with auto-populated stats, pattern notes, and next-week priorities.

💡

Pro tip: Weekly reviews are where productivity systems earn their keep. Without review, capture just creates clutter. 20 minutes every Friday to review the week pays back more than any app or template.

Meeting Notes Template

13/20

Build a meeting notes template in Notion. Meeting types I run: [describe]. Create: (1) a Meetings database with properties (date, attendees, type, project, action items count), (2) a template page with sections (agenda, notes, decisions, action items), (3) action items that link to my Tasks database, (4) a follow-up reminder if action items aren't completed, (5) a searchable archive, (6) a quick "scratchpad" variant for hurried notes.

Builds a meeting notes template with linked action items, follow-up reminders, and a quick scratchpad variant.

💡

Pro tip: Meeting notes die when action items don't escape the notes page. Always have an Action Items property/section that syncs to your task system — otherwise decisions made in meetings just decompose into noise.

Content Calendar

14/20

Build a content calendar in Notion for [describe content types — blog, social, YouTube, newsletter]. Posting frequency: [describe]. Create: (1) a Content database with properties (platform, topic, status, publish date, url, performance), (2) views — Calendar, Kanban by status, Timeline by platform, (3) an idea backlog that graduates into scheduled content, (4) a post-publish review where I log performance, (5) a content pillar tracker showing balance, (6) integration with my Tasks database for the work behind each piece.

Builds a content calendar with publication workflow, backlog, post-publish performance tracking, and pillar balance views.

💡

Pro tip: Content calendars in Notion work when they connect to the work needed to make each piece. Without linked tasks, publish dates slip. With linked tasks, deadlines stay real.

Goals & OKRs

15/20

Set up goals / OKRs tracking in Notion. My time horizon: [annual, quarterly, monthly]. Format: [SMART goals, OKRs, or custom]. Create: (1) a Goals database with properties (area, timeline, status, parent goal), (2) key results or milestones as child entries, (3) weekly check-ins that update progress %, (4) a dashboard showing all goals and their progress, (5) a retrospective template for the end of each period, (6) how to archive without losing context.

Sets up goals/OKRs with parent-child structure, weekly check-ins, and a progress dashboard with retrospectives.

💡

Pro tip: Most OKRs fail because they're reviewed quarterly instead of weekly. Notion makes weekly OKR check-ins trivial — 10 minutes to update progress %, 5 minutes to note what moved. That's the entire secret to OKRs working.

Notion AI & Advanced

5 prompts

Notion AI Workflow Design

16/20

Design how I should use Notion AI (built-in) in my workflow. Current pain points: [describe — slow writing, meeting notes, summarization]. Where AI could help: [describe]. Recommend: (1) specific Notion AI commands for each pain point, (2) which tasks should stay manual (AI slop creates worse output), (3) how to use AI blocks in templates, (4) Notion AI vs ChatGPT/Claude for different tasks, (5) cost-benefit of Notion AI subscription, (6) guardrails to avoid over-automation.

Designs Notion AI integration into workflows with command recommendations, guardrails, and cost-benefit analysis.

💡

Pro tip: Notion AI is best at summarizing meeting notes, rewriting drafts, and generating outlines — tasks with Notion context it already has. For creative or strategic tasks, ChatGPT and Claude still outperform Notion AI. Pick tools by strength, not vendor loyalty.

Template Gallery for Teams

17/20

Build a reusable template gallery for my team in Notion. Team size: [number]. Templates we need: [list — meeting notes, project briefs, 1:1s, retrospectives, etc.]. Deliver: (1) a Templates hub page with categorized templates, (2) each template designed for consistency (shared properties, views), (3) instructions for each template (when to use, how to customize), (4) governance — who owns templates, how to propose new ones, (5) a "featured templates" section that rotates, (6) onboarding guide for new team members.

Builds a team template gallery with governance, onboarding guide, and featured rotation to drive adoption.

💡

Pro tip: Template galleries die without a shepherd. Assign one person to own them, review them quarterly, and retire unused ones. Without ownership, you end up with 50 templates nobody uses.

Public Site from Notion

18/20

Turn a Notion page into a public site / docs / portfolio. Purpose: [describe]. Content structure: [describe pages and hierarchy]. Recommend: (1) when native Notion sharing is enough vs when to use a publishing tool (Super, Potion, Notion Sites, Feather), (2) SEO considerations (Notion's default SEO is weak), (3) custom domain setup, (4) design and branding limitations, (5) how to keep content fresh, (6) when to migrate off Notion to a real CMS.

Publishes Notion content as a public site with SEO, custom domains, and migration guidance to a real CMS if needed.

💡

Pro tip: Notion Sites (official) is now good enough for most simple sites and docs. Use third-party tools (Super, Potion) only when you need heavy customization. For high-traffic sites, migrate to a real CMS — Notion's SEO ceiling is real.

Notion + Calendar Sync

19/20

Sync Notion with my calendar. Calendar: [Google, Outlook, Apple]. Goal: [describe what I want visible in both]. Deliver: (1) native Notion calendar integrations (Google Calendar, Outlook), (2) what syncs vs what doesn't, (3) a Notion Calendar setup (if using their app), (4) Zapier/Make workarounds for complex sync, (5) how to keep Notion as source of truth without double-entry, (6) mobile considerations.

Syncs Notion with calendar apps including Notion Calendar, native integrations, and Zapier/Make workarounds.

💡

Pro tip: Notion Calendar (the standalone app) is the cleanest way to blend calendar + tasks. Tasks from Notion appear alongside calendar events, and you can schedule tasks directly. If you haven't tried it, it's the best Notion feature you're not using.

Migration To/From Notion

20/20

Help me migrate [from / to] Notion. Current tool: [describe]. Data volume: [rough size]. Priority: [preserve history, preserve structure, speed]. Deliver: (1) export format from the source tool, (2) import approach into Notion (CSV, Markdown, native import), (3) what will be preserved vs lost in migration, (4) data cleanup before/after migration, (5) a phased migration plan (don't boil the ocean), (6) rollback plan if migration goes wrong.

Plans a migration into or out of Notion with phased approach, cleanup, and rollback strategy.

💡

Pro tip: Never migrate everything at once. Pick one use case (e.g., just projects, not notes), migrate it, use it for 2 weeks, then migrate the next. Big-bang migrations usually fail because you don't know what to keep and what to drop.

Frequently Asked Questions

Notion AI ($10/month on top of Notion) is worth it if you use Notion 2+ hours daily for writing-heavy tasks (meeting notes, summarization, drafts). It's integrated into your existing content, so you don't copy-paste between tools. For occasional use or complex creative tasks, ChatGPT/Claude are better and cheaper. The value is context, not model quality.

Four rules: (1) limit top-level pages to 5-7 hubs, (2) delete or archive weekly — don't just add, (3) one person owns "the architecture" and gatekeeps structural changes, (4) monthly audits where you ask "do I use this?" and delete if no. Messy Notion workspaces come from additive-only thinking. Subtraction is the discipline that keeps it alive.

Notion for team work, databases, and visual layouts. Obsidian for personal knowledge graphs, offline use, and plain-text freedom (no vendor lock-in). Roam for networked note-taking and research workflows. For most people: Notion for work stuff (projects, clients, tasks) + Obsidian or Apple Notes for personal journaling. Different tools for different modes.

Yes, and it's good at it — especially Notion Formula 2.0 which has cleaner syntax. Always specify your properties (name + type), version (1.0 or 2.0), and desired output. Test formulas in a throwaway database before using in production — Notion formulas can be finicky with type mismatches.

Notion wins for teams that value customization and connected docs/databases. Dedicated PM tools (Asana, ClickUp, Linear) win for teams that need robust time tracking, strong permissions, advanced automations, and reporting. Rule of thumb: teams under 15 that value flexibility → Notion. Larger or process-heavy teams → dedicated PM tool.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Productivity courses

7-day free trial. Cancel anytime.

Browse All Prompt Collections