Auto-Synced Reading Highlights in Notion via Readwise (Kindle, Pocket, Instapaper)
Based on August Bradley's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Readwise’s beta integration can automatically sync Kindle, Apple Books, Pocket, Instapaper, and Twitter saved threads into a new Notion media vault after a one-time setup.
Briefing
A new Readwise beta integration makes it possible to automatically sync Kindle, Apple Books, Pocket, Instapaper, and even Twitter saved threads into a Notion “media vault,” turning scattered highlights and notes into a single searchable database. The practical payoff is speed and continuity: after an initial setup, new highlights and notes flow into Notion with little effort, and the resulting entries are formatted for fast review—so knowledge capture becomes closer to a system than a one-off habit.
The workflow starts with a paid Readwise plan (about $8–$9/month depending on billing cadence) and then a Notion connection. Readwise creates a new Notion database for the synced vault, and the integration relies on specific property names and category headings—especially “category” plus the default categories for “books,” “tweets,” and “articles.” Users can customize the database’s look (titles, fonts, added categories like videos or podcasts), but renaming or reordering the synced properties can break the mapping. Setup is described as taking under two minutes, though syncing a large library may take longer.
For people who already built a Notion vault, the integration requires moving to the newly created synced database. The recommended migration approach is to create the new vault, rename overlapping properties in the old one to match the synced schema (for example, changing “creator” to “author” and “medium” to “category”), then move entries in bulk. Any categories that don’t match will be added as new properties, but the goal is to align the structure so existing data carries over cleanly.
A key design choice affects how articles are stored. With Pocket and Instapaper, the integration syncs only the highlighted segments—not the full article—though each entry includes a link back to the original URL. If someone wants the entire article, they’re expected to use the Notion web clipper separately. This trade-off changes highlighting behavior: instead of saving only “perfect gems,” the system encourages capturing a wider slice of context around key ideas, then using tiered highlight colors (yellow/orange/red) to mark importance. The result is a smaller, more skimmable set of excerpts when returning to Notion.
Books get an additional upgrade through a simple tagging trick. Readwise can’t automatically infer section headers from the book text, but users can add “.h1”, “.h2”, or “.h3” to a highlight note while reading. Those markers become heading levels in Notion, producing a table-of-contents-like structure that groups highlights by section.
Beyond Notion, Readwise’s core value is spaced repetition. The app’s daily review surfaces highlights at irregular intervals, letting users “check” items they want to revisit and “x” items they don’t. The transcript also describes saving Twitter threads via direct message to Readwise, and capturing notes for audiobooks or paper books by manually entering a note in the Readwise app and attaching it to a selected title.
Overall, the system reframes reading capture as automation plus review: highlights from multiple platforms land in Notion automatically, while spaced repetition helps ensure the best ideas get revisited and internalized.
Cornell Notes
Readwise’s beta Notion integration automates syncing highlights and notes from Kindle, Apple Books, Pocket, Instapaper, and Twitter saved threads into a new Notion “media vault.” Setup is quick, but the integration depends on specific property names and default categories (notably “category,” plus “books,” “tweets,” and “articles”), so users should avoid renaming or reordering synced fields. For articles saved via Pocket/Instapaper, only the highlighted excerpts sync—full articles require the Notion web clipper. Books can be organized by section using “.h1/.h2/.h3” tags added to highlight notes, which become heading levels in Notion. Readwise’s core spaced-repetition review then resurfaces the most valuable highlights in the app so they’re revisited over time.
What does the Readwise-to-Notion setup require, and what can break the sync?
How does the system handle Pocket/Instapaper articles compared with Kindle highlights?
How can book highlights be organized into sections inside Notion?
What’s the recommended approach for migrating an existing Notion media vault to the new synced database?
How does Readwise’s spaced repetition work alongside the Notion vault?
How are Twitter threads saved into the vault?
Review Questions
- Why does the integration insist on keeping the default synced property names like “category,” and what symptom might appear if those are changed?
- What are the trade-offs of syncing Pocket/Instapaper content as highlights only, and how does the system compensate when full context is needed?
- How do “.h1/.h2/.h3” tags change the way book highlights appear in Notion, and where must those tags be added?
Key Points
- 1
Readwise’s beta integration can automatically sync Kindle, Apple Books, Pocket, Instapaper, and Twitter saved threads into a new Notion media vault after a one-time setup.
- 2
The synced Notion database depends on specific property names and default categories; renaming or reordering them can misclassify entries.
- 3
Pocket/Instapaper syncing stores only highlighted excerpts (with links back to the original), while full articles require the Notion web clipper.
- 4
Book section structure in Notion can be created by adding “.h1/.h2/.h3” to highlight notes while reading.
- 5
Migrating an existing vault means aligning old property names (e.g., “creator”→“author,” “medium”→“category”) before bulk-moving items into the new synced database.
- 6
Readwise’s spaced repetition daily review helps ensure the most valuable highlights resurface over time, using “check” to keep and “x” to remove from future review.
- 7
Twitter threads can be saved via direct message to “@readwise.io,” avoiding public announcements while still syncing into the vault.