How to Build a Research Pipeline With Readwise Reader and Obsidian
Saving highlights is the easy half. The other half — getting them into a notes system where they can be found, linked and cited — is where most reading workflows fall apart. Reader and Obsidian can be wired together properly, but the default sync is not the setup you want.
Direct answer: install the community plugin Readwise Official in Obsidian, sync into a dedicated folder, then layer a note template with source metadata. Sync runs from Readwise’s servers, so it costs nothing in API calls and works on mobile.
Why Does the Default Sync Disappoint People?
Out of the box, Readwise Reader exports one file per document with all its highlights. That is fine for a hundred notes and painful for a thousand, because you get near-duplicate files for the same article every time you re-import.
Worse, you lose the individual highlight as a first-class object. If you want a note you can link to from elsewhere, per-highlight export is what you need.
How Do You Set Up the Obsidian Sync Properly?
- In Obsidian, open Settings → Community plugins, turn off Restricted Mode, browse and install Readwise Official.
- Authenticate. The plugin opens a Readwise page where you approve the connection.
- Choose the sync folder. A dedicated top-level folder like
Sources/Readerkeeps exports separate from your own writing. - Enable Highlight text and Update existing files. Turn off legacy book sync unless you want Kindle highlights too.
- Run the initial sync and let it finish before you touch the vault. It can take several minutes for large libraries.
Turn on auto-sync once the first run is clean. It polls hourly by default; the plugin’s manual sync button is faster after a reading session.
What Should the Note Template Contain?
At minimum: source title, author, URL, read date, and your own summary line. The template lives in the plugin settings as plain markdown.
| Field | Why it matters |
|---|---|
| Source URL | Citation when you publish |
| Date captured | Distinguishes current from stale claims |
| One-line summary | Searchable recall hook |
| Tag per project | Lets you pull all research for one article |
The one-line summary is the field people skip and later regret. Write it in your own words while the source is fresh.
How Do You Find Anything Once It Grows?
Full-text search stops being useful past roughly 2,000 notes. Two habits fix it:
- Tag by project, not by topic.
#project/kestrelages well;#aidoes not. - Write index notes that list ten relevant source notes with a sentence each. Manual, but they are the pages you actually return to.
Where Does the Pipeline Break?
Three known failure points.
Renaming. If you rename an exported note, the next sync may recreate it under the original name, leaving you with two files. Use the plugin’s merge setting or avoid renaming exports at all.
PDF highlights. Reader’s PDF highlights sync as page-anchored text. If you later replace the PDF with a different edition, the anchors mean nothing.
Mobile. Obsidian mobile syncs are slower on large vaults. Do not expect Reader highlights to appear on your phone instantly.
Is This Worth the Setup for Casual Readers?
No. If you read a dozen articles a month and rarely write from them, an Obsidian pipeline is overhead. The Reader archive with search is sufficient.
It pays off for people producing 2,000+ words a week from sources — researchers, newsletter writers, analysts. The break-even is around the point where you are spending more than 20 minutes a week hunting for a quote you remember reading.
Key Takeaways
- Use the Readwise Official Obsidian plugin; sync goes through Readwise servers, not a local API.
- Export to a dedicated folder and keep auto-update on to avoid duplicate files.
- Tag by project, not topic — project tags stay useful as the vault grows.
- Never rename synced notes; the next sync may recreate the original filename.
- The pipeline earns its keep above roughly 2,000 words a week of source-based writing.
