Skip to content

Support Notion as an alternative to Obsidian #5

@UnbrandedTech

Description

@UnbrandedTech

Summary

Obsidian is the current knowledge base target (local markdown vault). Many teams use Notion instead. Dossiers, daily notes, and client profiles should optionally sync to Notion.

What needs to change

  • setup.sh — ask "Knowledge base? (1) Obsidian (2) Notion"
  • For Notion: need Notion API integration token (internal integration)
  • scripts/setup_obsidian.shscripts/setup_knowledgebase.sh with provider routing
  • Vault operations need an abstraction layer:
    • write_page(path, content) — writes markdown to Obsidian file or creates/updates Notion page
    • read_page(path) — reads from vault or Notion
    • list_pages(directory) — lists files or Notion database entries
  • honcho_obsidian_sync.pyhoncho_kb_sync.py — bidirectional sync with either backend
  • generate_initial_dossiers.py — writes to vault path or Notion database
  • sync_meeting_transcripts.py — daily note updates go to vault or Notion
  • morning_briefing.py — daily note creation targets vault or Notion

Design

A KnowledgeBase class in shared.py with ObsidianBackend and NotionBackend implementations. Scripts call kb.write_page("People/Jane Doe", content) and the backend handles the rest.

For Notion, the People and Clients directories map to Notion databases with properties matching the YAML frontmatter fields.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions