Skill: Notion Page Content Updater
Purpose
Update a specified Notion page with structured content extracted from a source document (e.g., Word, PDF, text). This skill automates the end-to-end process of finding the page, reading the document, parsing its content, and updating the Notion page's blocks accordingly.
Core Workflow
Follow these steps precisely:
- Clarify Request & Identify Target: Confirm the exact name of the Notion page to update and the path/filename of the source document.
- Locate the Notion Page:
- Use
notion-API-post-search with the exact page name. If no results, search more broadly (e.g., partial name) or use an empty query {} to list all pages/databases.
- From the search results, identify the correct page by its
title property. Note its id.
- Extract Source Content:
- Use the appropriate tool (
word-get_document_text, pdf-get_document_text, filesystem-read_file) to read the source document's full text.
- Analyze Page Structure & Plan Updates:
- Retrieve the current page structure using
notion-API-get-block-children with the page ID.
- Analyze the returned blocks to identify the target sections (e.g., headings for "About Me", "Paintings"). Note the block IDs that come immediately before where new content should be inserted.
- Parse the extracted document text to identify the relevant content for each target section.
- Execute Page Updates (Section by Section):
- For placeholder content: If a section contains placeholder text (e.g.,
[Birth, Your education...]), delete the old block using notion-API-delete-a-block.
- To add new content after a heading/block: Use
notion-API-patch-block-children. Specify the page ID as block_id, use the after parameter with the ID of the heading block, and provide the new content in the children array.
- Structure the content appropriately: Use
paragraph blocks for descriptive text and bulleted_list_item blocks for lists.
- Process one major section at a time (e.g., About Me, then Paintings, then Workshop, etc.).
- Verify & Conclude: After all updates, retrieve the page children again to confirm the changes. Provide a clear summary of what was updated.
Critical Implementation Notes
- Block Update Limitation: The
notion-API-update-a-block endpoint has very limited functionality and often cannot be used to change a block's type or rich text content. The primary method for adding content is patch-block-children.
- Content Chunking: Notion API calls have size limits. Break long document text into logical paragraphs when creating
children arrays.
- Special Characters: Escape quotation marks and newlines (
\n) properly in JSON payloads for block content.
- Error Handling: If a search finds multiple pages with similar names, ask the user for clarification. If a section heading doesn't exist on the target page, you may need to create it first.
Required Tools
notion-API-post-searchnotion-API-get-block-childrennotion-API-patch-block-childrennotion-API-delete-a-blockword-get_document_text / pdf-get_document_text / filesystem-read_filelocal-claim_done
Example Trajectory Pattern
The provided trajectory is a canonical example. Follow its pattern: search, extract, analyze structure, then sequentially update sections using patch-block-children after relevant headings.
1---2name: notion-page-content-updater3description: When the user needs to update or populate a Notion page with structured content extracted from documents or data sources. This skill handles the complete workflow of 1) Searching for and locating specific Notion pages by name, 2) Extracting content from source documents (Word/PDF/text files), 3) Analyzing document structure to identify relevant sections, 4) Mapping extracted content to Notion page sections, 5) Modifying page blocks (adding, deleting, updating paragraphs, lists, and headings), and 6) Organizing information in appropriate Notion formats (bullet lists, paragraphs, structured sections). Use this skill when users request to 'update a Notion page with information from a document' or need to synchronize content between documents and Notion workspaces.4---5# Skill: Notion Page Content Updater
6
7## Purpose
8Update a specified Notion page with structured content extracted from a source document (e.g., Word, PDF, text). This skill automates the end-to-end process of finding the page, reading the document, parsing its content, and updating the Notion page's blocks accordingly.
9
10## Core Workflow
11Follow these steps precisely:
12
131. **Clarify Request & Identify Target:** Confirm the exact name of the Notion page to update and the path/filename of the source document.
142. **Locate the Notion Page:**
15 * Use `notion-API-post-search` with the exact page name. If no results, search more broadly (e.g., partial name) or use an empty query `{}` to list all pages/databases.
16 * From the search results, identify the correct page by its `title` property. Note its `id`.
173. **Extract Source Content:**
18 * Use the appropriate tool (`word-get_document_text`, `pdf-get_document_text`, `filesystem-read_file`) to read the source document's full text.
194. **Analyze Page Structure & Plan Updates:**
20 * Retrieve the current page structure using `notion-API-get-block-children` with the page ID.
21 * Analyze the returned blocks to identify the target sections (e.g., headings for "About Me", "Paintings"). Note the block IDs that come **immediately before** where new content should be inserted.
22 * Parse the extracted document text to identify the relevant content for each target section.
235. **Execute Page Updates (Section by Section):**
24 * **For placeholder content:** If a section contains placeholder text (e.g., `[Birth, Your education...]`), delete the old block using `notion-API-delete-a-block`.
25 * **To add new content after a heading/block:** Use `notion-API-patch-block-children`. Specify the page ID as `block_id`, use the `after` parameter with the ID of the heading block, and provide the new content in the `children` array.
26 * **Structure the content appropriately:** Use `paragraph` blocks for descriptive text and `bulleted_list_item` blocks for lists.
27 * Process one major section at a time (e.g., About Me, then Paintings, then Workshop, etc.).
286. **Verify & Conclude:** After all updates, retrieve the page children again to confirm the changes. Provide a clear summary of what was updated.
29
30## Critical Implementation Notes
31* **Block Update Limitation:** The `notion-API-update-a-block` endpoint has very limited functionality and often cannot be used to change a block's type or rich text content. The primary method for adding content is `patch-block-children`.
32* **Content Chunking:** Notion API calls have size limits. Break long document text into logical paragraphs when creating `children` arrays.
33* **Special Characters:** Escape quotation marks and newlines (`\n`) properly in JSON payloads for block content.
34* **Error Handling:** If a search finds multiple pages with similar names, ask the user for clarification. If a section heading doesn't exist on the target page, you may need to create it first.
35
36## Required Tools
37* `notion-API-post-search`
38* `notion-API-get-block-children`
39* `notion-API-patch-block-children`
40* `notion-API-delete-a-block`
41* `word-get_document_text` / `pdf-get_document_text` / `filesystem-read_file`
42* `local-claim_done`
43
44## Example Trajectory Pattern
45The provided trajectory is a canonical example. Follow its pattern: search, extract, analyze structure, then sequentially update sections using `patch-block-children` after relevant headings.
majiayu000