Built a reading notes generator for book clubs and heavy readers

Most people who read nonfiction don’t retain much of it. You finish a chapter, could roughly describe what it was about, but ask about a specific argument or quote two weeks later and it’s gone. The ideas that made you nod while reading disappear because nothing forced you to process them.

Taking proper notes takes almost as long as reading the chapter itself. So most people don’t.

Built a workflow that generates structured reading notes automatically when a chapter PDF lands in Drive — themes, key concepts with definitions, main arguments, notable quotes with page numbers, discussion questions, action items, and an AI insight summary. Two parallel passes, posted to Slack before you’ve closed the PDF.

What it does

Chapter PDF dropped in Drive → two parallel passes (structured extraction + AI insights) → compiles notes → logs to reading log → posts full summary to Slack

About 15-20 seconds per chapter.

Two passes on the same chapter

Pass 1 — Structured extraction:

  • Book title, author, chapter number and title, page range

  • Main themes (as array)

  • Key concepts — each with definition

  • Main arguments — numbered list

  • Statistics and data cited

  • Notable quotes — text with page number

  • Vocabulary terms with definitions

  • Chapter summary

  • Main takeaway

  • Discussion questions

  • Action items

Pass 2 — AI insights:

  • 3-4 sentence chapter summary

  • Single most important insight from the chapter

  • How it connects to broader themes

  • One practical action the reader could take

Both run in parallel, merge before Slack notification.

What lands in Slack


📚 Chapter Summary

Book: Thinking, Fast and Slow

Author: Daniel Kahneman

Chapter: 12 - The Science of Availability

📋 Summary Stats:

• Themes: cognitive bias, memory, risk perception, heuristics

• Key Concepts: 4

• Arguments: 6

• Quotes: 3

• Action Items: 2

💡 Main Takeaway:

We judge the frequency of events by how easily examples

come to mind — not by actual data — which systematically

distorts our perception of risk and likelihood.

🧠 AI Insights:

This chapter demonstrates how the availability heuristic

creates predictable errors in judgment across domains from

insurance to personal safety decisions. The most important

insight is that emotional salience overrides statistical

reasoning even when we're aware of the bias...

One practical application: before making any risk assessment,

deliberately ask "what data do I actually have vs what examples

am I remembering?"

❓ Discussion Questions:

Q1: Can you identify a recent decision where availability bias

may have influenced your thinking?

Q2: How do news cycles exploit the availability heuristic?

Q3: What systems could reduce availability bias in organizational

decisions?

🔗 View Chapter

What lands in Google Sheets

Each row: Book, Author, Chapter #, Chapter Title, Pages, Main Themes, Key Concepts (count), Arguments (count), Quotes Noted (count), Action Items (count), Main Takeaway, Read Date

Your complete reading history in one sheet. Every book you’ve read, every chapter logged, searchable by theme or concept.

Setup

You’ll need:

  • Google Drive (folder for chapter PDFs)

  • Google Sheets (free)

  • n8n instance (self-hosted — uses PDF Vector community node)

  • PDF Vector account (~6-8 credits per chapter for two passes)

  • Slack (for reading notes sharing)

About 10 minutes to configure. Works well for book clubs — point Slack to a shared channel so everyone gets the notes together.

Download

Workflow JSON:

ebook-chapter-summarizer.json

Full workflow collection:

khanhduyvt0101/workflows


Setup Guide

Step 1: Get your PDF Vector API key

Sign up at pdfvector.com — free plan works for testing.

Step 2: Create Drive folder and Sheet

Folder: “Book Chapters” — copy folder ID.

Sheet headers:


Book | Author | Chapter # | Chapter Title | Pages | Main Themes | Key Concepts | Arguments | Quotes Noted | Action Items | Main Takeaway | Read Date

Step 3: Import and configure

Download JSON → n8n → Import from File.

New Chapter (Drive Trigger):

  • Connect Google Drive (OAuth2), paste folder ID

PDF Vector Extract + PDF Vector Insights:

  • Both run in parallel from Download Chapter

  • Add PDF Vector credential to both nodes

Log to Reading Notes:

  • Connect Google Sheets, paste Sheet ID

Send to Slack:

  • Connect Slack, select your channel (personal or book club)

Accuracy

Tested on nonfiction chapters from business books, academic texts, and self-help books.

  • Book title, author, chapter identification: ~97%

  • Main themes: ~93%

  • Key concepts with definitions: ~90% — reliable when concepts are explicitly defined in the text

  • Notable quotes with page numbers: ~88% — page numbers only when the PDF preserves them

  • Discussion questions quality: ~91% — generates thoughtful questions for most nonfiction

  • Action items: ~85% — depends on how prescriptive the chapter is

Works best on nonfiction. Fiction chapters extract themes and quotes but discussion questions are less useful.

Cost

~6-8 credits per chapter for two passes. Free tier covers ~12-15 chapters per month — one book roughly.

Customizing it

Book club mode:

Route Slack to a shared group channel. Everyone in the club gets the notes and discussion questions automatically after each meeting’s chapter is uploaded.

Spaced repetition:

Add a scheduled workflow that reads your Sheets log weekly and re-posts the main takeaway from a chapter you read 7 days ago — forces review without extra effort.

Connect to Notion:

Replace or supplement Sheets with a Notion database — create a book page per title and add chapter notes as subpages for a clean reading library.


Limitations

  • Requires self-hosted n8n (PDF Vector is a community node)

  • Page numbers in quotes only work on PDFs that preserve page metadata

  • Two-pass approach uses more credits than single-pass workflows

  • Fiction works less well than nonfiction for this use case


PDF Vector n8n integration

Full workflow collection

Questions? Drop a comment.

nice setup, the two-pass approach makes sense for keeping latency down. curious whether this works on scanned PDFs (image-only, no text layer) — wondering if PDF Vector handles OCR internally or if it just doesnt work on those and needs a clean digital source.