n8n inbox capture for PARA vault
TL;DR
Use n8n so external triggers (forms, webhooks, email, chat bots) create or update notes under Inbox/, with an optional second workflow to promote captures into [[Ideas/Ideas]] or [[Projects]] hubs after review.
Proposal
- Ingest: n8n workflow writes Markdown files into the vault’s
Inbox/ (filesystem watcher / git repo path) or calls an automation that does (Obsidian CLI, shell, or cloud sync — choose one deployment).
- Promotion: Either keep human triage only, or add a labeled queue (e.g. frontmatter
status: needs-triage) and a weekly n8n digest.
- Non-goals: Full replacement of manual PARA review (until trust in classification is proven).
Rough value / effort
- Value: Lowers friction for captures from tools that are not Obsidian.
- Effort / risk: Medium — path sync, auth secrets, and deduplication need a small design pass.
Related areas & projects
- Area dashboards: —
- Existing hubs: —
Next step
- Pick runtime (self-hosted vs cloud) and write target (local vault path vs CI bot opening PRs into vault repo).
Related
- Triage intake: [[Inbox/Inbox]]