Podcast to Notion: A Database That Keeps the Ideas Worth Keeping
A podcast notes database that survives contact with a busy week: the properties, the three ways to fill it, and the review views that stop it turning into a dump.
Guide5 min read
Everyone who listens to podcasts with intent has the same folder. It starts as "Podcast notes" and ends as 200 pages, each with a title, a pasted show-notes block, and nothing you would ever search for again.
The tool is not the problem. A Notion database gives you exactly what a notes system needs: properties you can filter, pages you can link, and a place to write one sentence in your own words. What it does not give you is a reason to come back. That has to come from the schema.
Why podcast notes rot
Three things go wrong, in this order:
- The capture is a transcript. You paste 4,000 words and call it a note. Nothing is marked as important, so nothing is.
- There is no provenance. Six months later you remember a claim about churn but not the show, the guest, or the minute it came from.
- Nothing asks for a second visit. The page is written once and never opened again, which means the idea never made it into your thinking.
A database fixes all three if you decide the properties before you fill it.
The schema
Keep it to seven properties. Every extra field is one more thing to skip.
| Property | Type | Why |
|---|---|---|
| Name | Title | The claim, not the episode title. "Pricing power comes from switching costs" beats "Ep. 214 with the CEO." |
| Show | Text or relation | Who said it; also the filter you use most |
| Guest | Text | Optional, but useful when a person shows up across shows |
| Captured | Date | When you saved it, not when the episode aired |
| Idea | Select | One of five buckets you actually care about, e.g. pricing, hiring, craft, health, reading |
| Source | URL | The episode link, with a timestamp if you have one |
| Status | Select | Inbox, used, discard |
The Source link is the one people skip. It is also the only one that lets you check a quote before you publish it.
Getting episodes in
There are three realistic flows, from cheapest to most automated.
Capture while you read. Open the episode in Podwise, read the summary, and paste the two or three takeaways you want to keep into a new page. The timestamp comes with the highlight, so Source is a two-second copy. This is the flow most people should start with, and it pairs well with the summary view.
Send the whole note. If you have connected Notion in Settings › Connections, Podwise can send an episode to the database you choose, with the summary, chapters, and highlights already structured. The Notion integration page covers what lands where. Do this for episodes you want in full; use the manual capture for the ones you only need one idea from.
Let an agent do it. The MCP server exposes send_episode and create_clip, so a workflow like "send every episode I mark as read this week into Notion" is a prompt, not a script. Start from the MCP guide and the episode-notes recipe.
What a good page looks like
One page, five lines:
Pricing power comes from switching costs
The guest argues that SaaS teams over-index on features because features are easy to demo. Switching cost is boring to demo and does the actual work.
Why it matters to us: our onboarding is doing the opposite — it makes leaving easy.
Source: show name, 00:41:12
The "why it matters to us" line is the difference between a saved note and a used one. It takes ten seconds and it is the only part of the page a future search will not find.
The views that earn the database its keep
Set these up once, and the folder stops being a folder:
- Inbox: Status is Inbox, sorted by Captured. Clear it weekly.
- By idea: grouped on the Idea select. This is the view you open when you are writing about pricing and want to remember five things you already know.
- Unused this month: Status is Inbox and Captured is more than 30 days ago. Anything still here after a month is not going to be used. Be honest and discard it.
Two rules keep it healthy. A page with no "why it matters" line is not allowed to leave the Inbox. And a page that has been open twice without being used becomes discard — the database is not an archive, it is a working set.
Start smaller than you think
The version of this that survives is the boring one: seven properties, one sentence per idea, ten minutes on Sunday. If you want the capture to be faster, spend the effort there — connecting the app, learning two keyboard shortcuts, processing episodes before you open Notion. The database is the easy part.
