Destinations

Where to connect

Open the extension side panel → gear icon → Connectors. You'll need to be signed in (cloud mode). Each connector has a toggle; flipping it on starts the connect flow for that service.

Notion

Notion uses OAuth. Tokens are stored encrypted on transcribed.dev — your browser never sees them.

Connect

1. 1Toggle Notion on in Connectors. A Notion authorization page opens.
2. 2Choose the workspace.
3. 3On the page-picker, share at least one page or database with the “YouTube Transcriber” integration. We recommend sharing a dedicated database.
4. 4Authorize. The popup closes itself; the toggle turns green.

Where transcripts land

• —If you shared a database — especially one whose title mentions “transcript”, “transcription”, or “YouTube” — each transcript becomes a new row in that database. The page title is the video title.
• —If you only shared a regular page, the integration creates a sub-page called “YouTube Transcripts” the first time you send something, then adds each transcript as a child page under it.
• —Every Notion page includes the source URL and the full transcript body, split across paragraphs so long videos fit Notion’s 2,000-character paragraph limit.

Recommended setup

1. 1In Notion, create a database called something like “YouTube Transcripts”.
2. 2Open the database → ••• → Connections → add “YouTube Transcriber”.
3. 3Connect from the extension. New transcripts will appear as rows automatically.

Troubleshooting

• “Notion integration has no accessible pages or databases.” In Notion, open any page → ••• → Connections → add “YouTube Transcriber”. Then send again.
• Send fails with a 401 / “authorization failed”. Notion revoked the token. Disconnect the toggle and connect again.
• Transcripts going to the wrong database. Once a database is auto-picked, we keep using it. Disconnect, share only the database you want, and reconnect.

Obsidian

Obsidian works over a local URL scheme — there's no account, no OAuth, and nothing leaves your machine. The extension builds an obsidian://new?... URL and your browser hands it to the desktop app.

Prerequisites

• —Obsidian desktop app installed and running on the same machine as Chrome.
• —A vault open in Obsidian with the exact name you’ll enter below (case-sensitive).

Connect

1. 1Toggle Obsidian on in Connectors.
2. 2In the “Obsidian vault name” field, type your vault’s name exactly as it appears in Obsidian’s sidebar.
3. 3(Optional) Expand “More” and check “Use Advanced URI plugin” if you’ve installed it (see below).

The first send will trigger Chrome's “Open in Obsidian?” prompt — allow it.

Advanced URI (recommended for long transcripts)

Stock Obsidian's obsidian://new caps URL length, so very long transcripts can be truncated or fail outright. The community Advanced URI plugin handles long content reliably. Install it inside Obsidian, then enable the "Use Advanced URI plugin" checkbox in Connectors.

Note format

# {Video Title}
**Source:** https://www.youtube.com/watch?v=...
**Author:** {Channel}

## Transcript

{full transcript body}

Troubleshooting

• Nothing happens after “Send to Obsidian”. Obsidian must be running. Check that you allowed the protocol handler in Chrome (chrome://settings/handlers).
• Wrong vault opens / vault not found. The vault name is case-sensitive and must match Obsidian's sidebar exactly.
• Long transcript is cut off. Install the Advanced URI plugin and enable it in Connectors.

Privacy

• —Notion: OAuth tokens are stored encrypted on transcribed.dev. Transcript content is sent over HTTPS to api.notion.com when you press Send.
• —Obsidian: stateless. The note URL is built locally and handed to the desktop app — nothing transcript-related leaves your machine for this destination.