All use cases

Work

Tip only: let bots pick Notion DB vs Obsidian markdown

Forcing every note into one tool fights how the work actually wants to be stored.

Share

What hurt

Mike P (@mikepat711) uses Notion alongside Obsidian with Grok Bot: Obsidian organizes markdown files; Notion handles anything that works better as a database. He lets Grok Bots pick the best format for the job — and having bots write into Notion taught him the platform faster than staring at an empty UI. Tip-only — steal the split + bot-chooses-sink pattern.

What to install or create

Two sinks. Bot chooses DB vs markdown per task. Learn Notion by letting bots write first.

Bots

  • Format picker desk

    Chooses Notion DB vs Obsidian markdown per task and writes there.

Plugins

  • Notion

    Required

Files

  • Rule of thumb: markdown files → Obsidian; tabular/queryable → Notion DB.

Routines

  • When starting a new routine, ask the bot which sink fits before it invents a third store.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/mikepat711/status/2100005473290223967.
  2. 2Connect Notion (and point Obsidian at a vault the bot can write).
  3. 3Tell your bots: Obsidian for markdown files; Notion for database-shaped work — you pick.
  4. 4Start one new routine by asking the bot which sink fits; let it create the first rows/files.
  5. 5Review the structure once; reuse that pattern instead of opening empty Notion from scratch.

Approval fence

Bots may write notes/DB rows you asked for. No publish or spend from the knowledge sink.

What to tweak

Steal Obsidian=files, Notion=DB, bot picks. Empty Notion is a trap — write with a bot.

Source

Mike P @mikepat711 · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro