NotebookLM Pipeline¶
The NotebookLM pipeline allows the multi-agent system to interface directly with Google's NotebookLM platform. This enables the automatic generation of Audio Overviews (podcasts), study guides, quizzes, and structured reports from the raw content stored in the Obsidian Vault.
The Broadcaster Agent¶
The pipeline is managed by the Broadcaster agent (skill: vault-mind-broadcaster). The agent uses either:
- MCP tools (mcp__notebooklm-mcp__*) — preferred path, structured output, no shell overhead
- nlm CLI via bash — fallback when MCP server not configured
The Broadcaster auto-loads the nlm-skill which provides comprehensive NotebookLM CLI and MCP guidance.
Workflow¶
1. Trigger¶
The pipeline is typically triggered passively:
* A human tags a folder, document, or collection in the Obsidian Vault with @agent-Broadcaster:podcast.
* The Watcher (Dispatcher) detects the tag, groups any related markers, and spawns the Broadcaster in a forked session.
2. Sourcing¶
The Broadcaster pushes relevant content to NotebookLM.
* The agent reads the local markdown files from the Vault.
* MCP path: Uses mcp__notebooklm-mcp__source_add to upload text directly to a new or existing notebook.
* CLI fallback: Uses nlm notebook add-source <id> --text "$(cat file.md)" via bash.
3. Generation (Studio)¶
Once the sources are loaded, the Broadcaster initiates content generation.
* It uses the studio_create MCP tool.
* For an Audio Overview, it might specify: artifact_type: "audio", format: "deep_dive", length: "default".
* For a study guide: artifact_type: "report", format: "Study Guide".
4. Polling & Delivery¶
- The agent uses
studio_statusto poll NotebookLM until the artifact generation is complete. - Once complete, it uses
download_artifactto pull the.wavfile or the report markdown back to the local machine. - It saves the file to the
Vault/Agent/Presentations/directory. - Finally, it updates the original Obsidian note, replacing the
@agent-Broadcastermarker with an embed link (e.g.,![[My_Podcast.wav]]).
Skills Integration¶
The skills/vault-mind/SKILL.md must be updated to instruct the agent on this workflow, specifically outlining the MCP tools available (source_add, studio_create, download_artifact) and the expected pathing for output delivery.