Integration Architecture
Convert source files to Markdown using MDConvert, then run two parallel sync jobs:
- Notion: push Markdown blocks into a database page via the Notion API. Use metadata to map to database properties (status, owner, tags).
- Obsidian: sync Markdown files into a Git-managed vault and trigger Obsidian Sync / community plugins to publish updates.
Automation Steps
- Convert Documents. Use MDConvert CLI or API to turn PDFs, DOCX, PPTX into Markdown stored in `/markdown-output`.
- Enrich Front Matter. Add keys like `notion_page_id`, `obsidian_path`, `topic`, and `last_synced` inside YAML front matter.
- Push to Notion. Utilize a GitHub Action or cron job that:
- reads Markdown, converts to Notion block JSON
- updates or creates the target page
- sets properties (owner, tags, review date)
- Sync Obsidian Vault. Commit Markdown to a repo connected to Obsidian Git or Obsidian Sync. Trigger a local refresh so vault users get updates instantly.
# example front matter --- notion_page_id: 2cd7a3f4-12f8-4b7c-993a-1af5f7d3b9a2 obsidian_path: Company Wiki/Playbooks/RAG.md topic: rag last_synced: 2025-06-19 ---
Tips for Each Platform
Notion
- Map Markdown headings (`##`) to toggle blocks or synced block sections.
- Use callouts for warnings or compliance notes.
- Add backlinks to the source Markdown file so teams can edit via PRs.
Obsidian
- Generate `[[wiki-links]]` during conversion with a lookup table.
- Use front matter tags to auto-populate Dataview dashboards.
- Leverage the Publish plugin for external sharing while keeping internal vault private.