Get AI summaries of any video or article — Sign up free
How to process notes in Obsidian // Readwise Official Obsidian plugin thumbnail

How to process notes in Obsidian // Readwise Official Obsidian plugin

Nicole van der Hoeven·
5 min read

Based on Nicole van der Hoeven's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Readwise functions as a capture-and-export layer that reduces the need to take notes immediately while consuming content.

Briefing

A practical workflow for turning scattered highlights into usable knowledge is built around Readwise as a “middleware” layer between raw reading and an Obsidian vault. Instead of trying to capture everything at the moment of consumption—or expecting one pass through a source to stick forever—the system funnels Kindle highlights, PDF notes, and even saved tweets into Obsidian, then relies on scheduled processing to convert those fragments into original notes.

The process starts with installing the Readwise Official Obsidian plugin. In Obsidian, users enable Community plugins, search for “Readwise,” and install the “Official Readwise to Obsidian integration.” After connecting the plugin to a Readwise account, the setup page becomes the control center: exports can be formatted as Markdown, and sources like books, articles, tweets, and podcasts can be routed into separate folders to reduce naming collisions. A key customization is how imported items are tagged—such as using a “Te Verzetteln” (TVZ) inbox tag to mark material that still needs processing. The plugin also supports sync behavior, including an “Initiate Sync” action and a re-sync frequency setting; the workflow recommends switching from manual to hourly so new highlights don’t sit idle.

Once configured, the system works across devices. Kindle e-readers and the Kindle app can sync highlights and notes automatically, which then land in Obsidian as appended highlights in the relevant Markdown files. The same pipeline handles social saving: a tweet can be shared via “Send as a private message” to Readwise, where it appears within minutes, and then pulled into Obsidian via a manual sync if needed. In Obsidian, the result is searchable, linked material—sometimes as highlighted text, sometimes as a bookmarked tweet—complete with a link back to the original source.

The real value arrives after ingestion. Each day at 9:00 pm, the workflow reviews items tagged with TVZ (or another chosen tag) and extracts ideas from the highlighted passages. For a fiction book like “Klara and the Sun” by Kazuo Ishiguro, that means creating a separate note outside the Readwise folder that summarizes themes (hope, loneliness, superstition) and points to supporting scenes—shifting from quotes to interpretation. For an academic-style work about Kubedim (a proxy enabling control theory to improve microservices performance), the process similarly moves from highlighted sections to a new “in my words” page. Direct author quotes can be kept in a separate note to preserve authorship boundaries, while additional concepts mentioned by the author—like the circuit breaker pattern—become new linked pages that connect to broader areas such as Site Reliability Engineering.

There’s no strict stopping rule. The workflow acknowledges an endless expansion risk: Kubedim leads to circuit breakers, which can lead to dimming/brownout, and so on. Instead of chasing a finish line, it recommends going as deep as feels relevant at the time, trusting that notes remain in the vault for later refinement.

Cost is straightforward: the Obsidian plugin is free, while Readwise is paid. Readwise Light costs $4.49/month and Readwise costs $7.99/month, with the higher tier adding features like space repetition for highlights. A free trial is available, and a referral link can extend trial time.

Cornell Notes

Readwise acts as a middleware layer that collects highlights and notes from sources like Kindle, PDFs, and tweets, then exports them into an Obsidian vault as Markdown. After syncing, the workflow doesn’t stop at imported quotes; it schedules daily processing of items tagged (often TVZ / “Te Verzetteln”) to turn fragments into original “in my words” notes. Examples include creating theme-based notes for “Klara and the Sun” by Kazuo Ishiguro and building concept pages for Kubedim, circuit breaker patterns, and related ideas. The system accepts that knowledge work has no clean endpoint—notes can keep expanding as relevance emerges, while earlier work stays available for later refinement. Readwise Official is free, but the service is paid, with Light and full plans differing in features like space repetition.

Why use a middleware layer like Readwise instead of taking notes directly in Obsidian while reading?

The workflow treats note-taking as a two-stage process: capture first, then process later. Direct in-the-moment notes can fail when reading happens on phones/tablets, when someone isn’t in the mood to write, or when not everything consumed deserves a place in the vault. Readwise reduces that noise by collecting highlights and saved items automatically, then exporting only what was explicitly saved/highlighted into Obsidian for later review.

How does the Readwise Official plugin help manage imported material in Obsidian?

After installing “Readwise Official” (the “Official Readwise to Obsidian integration”), the plugin connects to a Readwise account and exports sources as Markdown. The setup allows choosing where books/articles/tweets/podcasts go (separate folders to avoid similarly named items) and applying custom formatting and tags. A practical tag like “Te Verzetteln” (TVZ) marks items that still need processing. Sync controls include “Initiate Sync” and re-sync frequency (recommended hourly rather than manual) so new highlights arrive without constant manual effort.

What does “processing” look like after highlights land in the vault?

Processing happens in a daily review at 9:00 pm of items tagged with TVZ (or another chosen tag). The goal is to extract ideas from highlighted passages and convert them into new notes outside the Readwise folder. For “Klara and the Sun” by Kazuo Ishiguro, that means writing theme-focused notes (hope, loneliness, superstition) and referencing supporting scenes, shifting from quotes to interpretation.

How does the workflow separate different kinds of text and authorship?

It uses multiple notes to keep boundaries clear. Imported highlights can stay in the Readwise folder, while “in my words” pages summarize meaning and connect ideas to broader work. For direct author quotes, the workflow creates a separate note containing the author’s wording, then adds additional pages for concepts the reader derives—such as circuit breaker patterns—supported by links to diagrams or external explanations.

What prevents the system from spiraling into endless note creation?

There’s no quantitative stopping rule. Kubedim can lead to circuit breaker pattern pages, which can lead to dimming/brownout and then to broader areas like Site Reliability Engineering. The workflow’s safeguard is intentional depth: go as deep as feels relevant when creating notes, knowing everything remains in the vault for later revisit rather than trying to “finish” the knowledge tree.

Review Questions

  1. When should highlights be reviewed and transformed into “in my words” notes in this workflow, and what tag typically triggers that review?
  2. What sync settings and export options are used to ensure highlights from Kindle and saved tweets reliably reach Obsidian?
  3. How does the workflow handle authorship boundaries between direct quotes and the reader’s interpretation?

Key Points

  1. 1

    Readwise functions as a capture-and-export layer that reduces the need to take notes immediately while consuming content.

  2. 2

    The Readwise Official Obsidian plugin can export books, articles, tweets, and podcasts as Markdown into chosen folders with customizable formatting and tags.

  3. 3

    Setting re-sync frequency to hourly helps keep the Obsidian vault current without relying on manual sync.

  4. 4

    Daily processing converts imported highlights into original notes, often using a TVZ (“Te Verzetteln”) inbox tag to identify what needs work.

  5. 5

    The workflow separates author quotes from the reader’s interpretation by creating distinct notes for each purpose.

  6. 6

    Knowledge expansion has no fixed endpoint; the system favors relevant depth over trying to fully complete a topic.

  7. 7

    Readwise Official is free, but Readwise Light ($4.49/month) and Readwise ($7.99/month) differ in features such as space repetition.

Highlights

Readwise is positioned as middleware: it captures highlights and saved items first, then Obsidian processing turns them into ideas later.
A TVZ (“Te Verzetteln”) tag acts as a queue for daily review, turning an inbox of fragments into structured notes.
The workflow explicitly separates direct author quotes from “in my words” interpretation to preserve authorship boundaries.
There’s no clear stopping rule for note expansion; relevance and time determine depth, not completion.

Topics

Mentioned