Plaud Sync

Sync your Plaud voice recordings into Markdown notes inside your Obsidian vault — transcripts, AI summaries, highlights, and metadata included.

Unofficial plugin. Plaud does not offer a public API. This plugin uses a reverse-engineered API discovered by inspecting the Plaud web app. It may break without notice if Plaud changes their backend. Use at your own risk.

Features

• Incremental sync — only fetches recordings newer than your last sync checkpoint; never creates duplicates
• Rich Markdown notes — renders title, date, duration, AI summary, key highlights, and full transcript with speaker labels
• Idempotent updates — uses a stable file_id in frontmatter to update existing notes in place
• Secure token storage — stores your Plaud session token via Obsidian's Secret Storage API (local fallback if unavailable)
• Retry with backoff — transient failures (network, rate-limit, 5xx) are retried automatically; permanent failures (auth, bad response) are surfaced immediately
• Trash filtering — recordings you deleted in Plaud are automatically skipped
• Content hydration — fetches full transcript and AI summary content from Plaud's signed URLs

Requirements

• Obsidian 0.15.0 or later
• A Plaud account with recordings
• A session token extracted from the Plaud web app (see Obtaining your token)

Installation

Manual install

git clone https://github.com/leonardsellem/plaud-sync-for-obsidian.git
cd plaud-sync-for-obsidian
npm ci
npm run build

Copy these three files into your vault's plugin directory (e.g. <vault>/.obsidian/plugins/plaud-sync/):

• main.js
• manifest.json
• styles.css

Restart Obsidian and enable Plaud Sync under Settings → Community plugins.

Obtaining your token

Plaud has no official API or developer portal. The token is a JWT session cookie stored in your browser when you use the Plaud web app.

1. Open web.plaud.ai and log in
2. Open your browser's Developer Tools (F12 or Cmd+Opt+I)
3. Go to the Console tab and run:

   localStorage.getItem("tokenstr")
   

4. Copy the full string (starts with bearer eyJ...)
5. In Obsidian, open Settings → Plaud Sync and paste it into the Plaud token field

The token is long-lived (~10 months) but will eventually expire. When it does, repeat these steps.

Configuration

Open Settings → Community plugins → Plaud Sync:

Usage

Commands

Open the command palette (Ctrl/Cmd+P) and search for:

How sync works

1. Fetches the full recording list from Plaud
2. Filters out trashed recordings
3. Selects candidates where start_time > lastSyncAtMs
4. For each candidate, fetches detail + content (transcript, AI summary)
5. Creates or updates the Markdown note in your sync folder
6. Advances the lastSyncAtMs checkpoint only after the full batch succeeds

If sync is already running (startup or manual), additional attempts are blocked until the current run finishes.

Troubleshooting

Development

npm ci                # install dependencies
npm run dev           # watch mode with hot reload
npm run build         # typecheck + production build
npm run test          # run test suite (Node.js native test runner)
npm run lint          # eslint

Project structure

src/
├── main.ts                 # Plugin lifecycle, command dispatch, error handling
├── commands.ts             # Command registration
├── settings.ts             # Settings UI tab
├── settings-schema.ts      # Settings interface and defaults
├── secret-store.ts         # Token storage (Obsidian secrets + fallback)
├── plaud-api.ts            # API client, error categorization
├── plaud-api-obsidian.ts   # Obsidian requestUrl transport adapter
├── plaud-normalizer.ts     # Payload normalization across API variants
├── plaud-renderer.ts       # Markdown rendering
├── plaud-content-hydrator.ts # Content inflation from signed URLs
├── plaud-vault.ts          # Vault note identity and upsert logic
├── plaud-sync.ts           # Incremental sync orchestration
├── plaud-retry.ts          # Retry/backoff with telemetry sanitization
└── sync-runtime.ts         # Single-flight sync guard
test/
└── *.test.mjs              # Matching test suite for each module

Legal Basis

This is an unofficial community plugin, not affiliated with or endorsed by PLAUD, Inc.

Interoperability under EU law

This project is developed and distributed under the interoperability provisions of EU Directive 2009/24/EC (the Software Directive):

• Article 5(3) permits users to observe, study, and test software to determine underlying ideas and principles
• Article 6 permits decompilation and reverse engineering when necessary to achieve interoperability with independently created software
• Article 9 renders contractual clauses restricting these rights null and void

The Court of Justice of the European Union has consistently upheld these protections, notably in SAS Institute v. World Programming (C-406/10) and Top System v. Belgian State (C-13/20).

Interoperability intent

This plugin enables PLAUD users to connect their recording data with Obsidian, an independently created knowledge management application. PLAUD already supports third-party automation through their official Zapier integration, demonstrating acceptance of interoperability use cases. This project extends similar functionality to the Obsidian ecosystem.

Disclaimer

This software is provided as-is for interoperability purposes. Users are responsible for compliance with PLAUD's Terms of Service and applicable laws in their jurisdiction. The maintainers make no warranty regarding account standing or service availability.

Contributing

Contributions are welcome. Please see CONTRIBUTING.md for guidelines.

License

MIT — Leonard Sellem