How to Use Readwise With Notion to Build a Reading Knowledge Base
If you've ever highlighted a great passage on your Kindle and then never seen it again, you already know why people pair Readwise with Notion. Readwise is excellent at pulling highlights out of your Kindle, Apple Books, Instapaper, podcasts, and tweets. Notion is excellent at organizing information into something you can actually search and link together later. Neither tool does the other's job well, which is exactly why combining them works so well. This guide walks through how to use Readwise with Notion step by step, including the parts of the sync that confuse almost everyone the first time.
What Readwise and Notion Each Do Well
Readwise's whole job is capture and retention. It aggregates highlights from wherever you read, resurfaces them through its Daily Review spaced-repetition feature, and now layers in some AI summarization tools on top. What it's not built for is deep organization. You can tag things in Readwise, but it's not a workspace where you build out project notes, link ideas together, or create a real second brain.
Notion is the opposite. It's a flexible database and notes tool, but it has no idea what a Kindle highlight even is until you feed it one. On its own, Notion is just an empty workspace waiting for structure.
Put them together and you get a system: Readwise captures everything automatically, Notion becomes the permanent, organized home for it. This is also why we wrote a separate guide on tracking books in Notion if you're building your reading database from scratch rather than importing highlights into it.
What You'll Need Before You Start
You'll need an active Readwise subscription (it runs roughly $7.99 to $9.99 a month depending on billing cycle, with a free trial if you haven't tried it yet), a Notion account on any plan since the free tier handles this fine, and at least one source already connected to Readwise. That usually means your Kindle account linked, the Readwise web clipper installed, or your Readwise Reader app connected to Pocket or Instapaper. If you're coming from a Kindle-heavy reading habit, our guide on syncing Kindle highlights to Notion covers that specific setup in more depth.
Step 1: Connect Readwise to Notion
Log into Readwise and head to the Export settings page. You'll see Notion listed as one of the export destinations alongside Obsidian, Evernote, Markdown, CSV, and Roam. Click to connect, and Readwise will prompt you to authorize access through Notion's OAuth flow. This is the same permission system Notion uses for any third-party integration, so you're not handing over your password, just granting Readwise access to create and update pages in your workspace.
Once authorized, you'll choose where the synced content lands. Readwise can create a brand new database for you automatically, or you can point it at an existing one if you've already got a reading-related database set up. For most people starting fresh, letting Readwise generate its own database is the easier path.
Step 2: Configure Your Export Settings
This is where you decide what actually flows into Notion. Readwise lets you filter by source type, so you can choose to sync only books, only articles, only podcast highlights, or everything at once. If you've got years of tweets saved in Readwise, you probably don't want all of them cluttering your Notion workspace, so filtering by tag or source here matters more than it looks like at first glance.
You can also control layout details, like whether highlights appear as a bulleted list, whether book cover images show up, and how metadata like author and category gets formatted. None of this is locked in forever. You can come back and adjust export settings whenever your needs change, though changes typically apply going forward rather than retroactively reformatting everything already synced.
Step 3: Understand How the Sync Actually Works
This is the part that trips people up, so it's worth being direct about it. The Readwise to Notion sync is not bidirectional. New highlights get appended to the Notion page that matches their source book or article. If you highlight three new passages in a book you've already synced before, those three new highlights show up added to the existing page.
But here's the catch: if you go back into Readwise and edit a highlight, add a note, or change a tag on something you've already synced, that edit does not overwrite what's sitting in Notion. Readwise built it this way on purpose, to avoid accidentally wiping out manual changes you might have made directly in Notion. The tradeoff is that people sometimes assume their Readwise edits are being mirrored over, only to find the Notion version frozen at the state it was in when it first synced.
The practical takeaway: treat Notion as your working copy once content lands there. If you want to edit tags, add context, or restructure a highlight, do it in Notion directly rather than going back to Readwise expecting it to flow through.
Step 4: Turn Your Synced Highlights Into a Real Knowledge Base
The default Readwise export gives you a database with properties like Title, Author, Category, and Tags, plus your highlights nested underneath as sub-blocks with the cover image up top. It's functional, but it's basically a filing cabinet, not a knowledge base, until you add structure on top of it.
A few things that actually make it useful:
Link highlights to project pages. If you're researching a topic across multiple books, create a project or topic page and use Notion's relation property to connect relevant highlight pages to it. Now instead of hunting through dozens of book pages, you've got one page pulling together every quote relevant to what you're working on.
Build a tagging convention and stick to it. Readwise tags carry over, but you can extend them in Notion with your own categories, whether that's by theme, project, or how you plan to use the material (quote to cite, idea to develop, counterargument to address).
Use rollups for a bird's-eye view. If you've got a database of topics or projects, a rollup property can show you highlight counts or recent additions from linked book pages without opening each one individually.
Create filtered views instead of scrolling the main database. A view filtered to "unread" tags, or one sorted by date added, keeps the raw sync usable even as it grows into the hundreds of entries.
This is the layer that separates people who set up the sync once and forget about it from people who actually get research value out of it months later.
Optional: Automating or Customizing Further
The native integration covers most needs, but if you want more control, there are a couple of options worth knowing about. The open source readwise-notion-sync script runs on GitHub Actions, checking for new highlights on an hourly schedule and only processing books with new content since the last run, which keeps your manual edits protected by design. It's a good fit if you're comfortable with a little setup and want sync timing you control rather than relying on Readwise's own schedule.
For more complex workflows, tools like Latenode offer triggers and actions across both platforms, letting you build filtered or conditional syncs, for example only pushing highlights tagged a certain way, or triggering a sync based on a webhook rather than a timer. These are overkill for casual use, but genuinely useful if you're running something closer to a research pipeline.
Common Problems and Fixes
A few issues come up often enough to flag. Duplicate pages usually happen when a book gets re-titled or re-categorized in Readwise after the initial sync, creating a new page instead of updating the old one; manually merging or deleting the stale page fixes it. Missing highlights are often a filter issue, double check your export settings aren't excluding the source type or tag you expected. If your database starts feeling sluggish, it's almost always volume, hundreds of books with deeply nested highlight blocks will slow Notion down, and building filtered views or archiving older entries to a sub-database helps. And if you've lost what felt like an edit, it's probably the one-way sync behavior described above, not a bug.
When This Workflow Isn't the Right Fit
All of this is genuinely great if your goal is a permanent, searchable archive of quotes and ideas for research, writing, or serious study. But it's a DIY system. It takes setup time, ongoing tagging discipline, and periodic cleanup to stay useful rather than becoming another cluttered database you avoid opening.
If what you're actually after is a simple way to track what you're reading, how you feel about it, and your progress over time, rather than archiving highlights for research, a dedicated reading tracker will get you there faster. Bookwise handles reading sessions, quarter-star ratings, mood and pacing tags, and reading stats automatically, with no database configuration required. It also includes an AI book companion if you want to talk through a book's ideas without building a highlight-management system around it. You can see how that compares to spreadsheet-style setups in our breakdown of Goodreads vs Notion for book tracking, or check out Bookwise vs Goodreads if you're weighing trackers more broadly.
Final Thoughts
Readwise and Notion solve different problems, and that's exactly why the combination works. Readwise captures highlights from everywhere you read without you lifting a finger, and Notion gives those highlights a permanent, structured home where they can actually connect to your projects and ideas. The sync isn't perfect, it's one-directional and it requires some upkeep to stay organized at scale, but for researchers, students, and anyone building a long-term knowledge archive, it's still one of the best setups available. If your needs are lighter, simply wanting to remember what you read and how it made you feel, a dedicated tracker might be the faster, lower-maintenance path.