Skip to main content

I am using the Readwise-to-Notion integration to sync Kindle highlights into a Notion database. Each book creates its own individual page within this database, and every highlight and attached note for the book is stored inside the page.

 

I want to automate the process of identifying highlights containing specific keywords (e.g., 'essay') and moving those highlights into a separate Notion database. The new database should include:

  • The excerpt or highlight text.
  • The associated note (if any).
  • The title of the book.

I am encountering these challenges:

  1. Nested Data Access: Since each book is stored as an individual page in the main database, Zapier cannot directly access or scan the content of these nested pages. Instead, it only recognizes the database-level metadata (e.g., page title).
  2. Keyword Filtering: I want Zapier to continuously scan these individual pages for specific keywords like 'essay' in the highlights or notes.
  3. Automation Scope: I need the Zap to automatically transfer matching highlights into a separate Notion database, ensuring the necessary fields (excerpt, note, book title) are correctly mapped.

My current workflow looks like this:

  1. I highlight text and add notes in Kindle.
  2. These highlights are synced into Notion using Readwise, where each book creates a new page containing all its highlights and notes.
  3. I want Zapier to look inside these pages, identify relevant highlights (based on keywords like 'essay'), and copy them into another Notion database for essay ideas.

The issue seems to be that Zapier cannot "see" or "read" the nested content of the individual pages created for each book. I need guidance on:

  • Whether this is possible using Zapier alone.
  • If not, what alternative methods, tools, or integrations can achieve this functionality.

Example of how excerpts look on the database:

 

 

Hi ​@Forero395,

 

Welcome to the Community.

 

Zapier's integration with Notion doesn't support nested data access, so it can't trigger on sub-pages or nested databases. Alternatively, you could use an intermediary tool with a more advanced Notion integration, adjust your Readwise-to-Notion setup to handle highlights as top-level pages, manually tag highlights in Notion for Zapier to watch, or use Readwise's tagging feature to filter highlights. These workarounds may only partially automate your process but can help manage complex workflows.

 

I hope this helps. Let me know if you have any other questions.


Reply