Actions16
Overview
The "Get Children" operation of the "Block" resource in this Notion Advanced node retrieves all child blocks of a specified parent block within a Notion workspace. This is useful when you want to programmatically access the content nested inside a block, such as paragraphs, headings, lists, images, or other block types that are children of a given block.
Common scenarios include:
- Extracting the detailed content structure of a page or section.
- Processing or transforming nested content blocks for automation workflows.
- Synchronizing or backing up hierarchical content from Notion.
For example, if you have a block representing a toggle list or a column, you can use this operation to fetch all the blocks contained inside it.
Properties
| Name | Meaning |
|---|---|
| Block ID | The unique identifier of the block whose children you want to retrieve (required). |
| Additional Fields | A collection of optional fields applicable to some operations on blocks (not used here). |
Note: For the "Get Children" operation specifically, only the "Block ID" property is required and used.
Output
The output JSON contains an object with the following structure:
results: An array of block objects representing each child block of the specified parent block. Each block object includes details such as type, content, properties, and potentially nested children.count: The total number of child blocks returned.
This output allows you to inspect or further process each child block's data.
The node does not output binary data for this operation.
Dependencies
- Requires a valid Notion API authentication token configured in the node credentials.
- Uses the Notion API endpoint
/blocks/{block_id}/childrento fetch child blocks. - The node depends on utility functions for resolving block IDs and making paginated requests to handle large numbers of children.
Troubleshooting
- Invalid Notion API credentials: The node will throw an error if the provided API key or token is invalid or missing. Ensure your Notion integration token is correctly set up in the node credentials.
- Block ID not found or invalid: If the specified Block ID does not exist or is malformed, the API call will fail. Verify the Block ID is correct and accessible by your integration.
- Empty results: If the block has no children, the
resultsarray will be empty. This is expected behavior. - API rate limits: If you request too many blocks in a short time, the Notion API may throttle requests. Implement retry logic or reduce request frequency if needed.