Actions16
Overview
This node interacts with Notion's API to retrieve detailed information about a specific block within a Notion workspace. The "Get Block" operation fetches the content and metadata of a block identified by its unique Block ID. This is useful when you want to programmatically access the details of a particular block, such as paragraphs, headings, images, or other content types in Notion.
Practical scenarios include:
- Extracting content from a specific block for processing or display elsewhere.
- Integrating Notion content into other applications by fetching block data.
- Automating workflows that depend on the content or properties of individual blocks.
Properties
| Name | Meaning |
|---|---|
| Block ID | The unique identifier of the block to retrieve. |
| Additional Fields | (Not applicable for Get operation on Block resource) |
The provided input properties JSON defines "Block ID" as required for this operation. Additional fields are available for other operations but not relevant here.
Output
The output JSON contains the full data structure of the requested block as returned by the Notion API. This includes:
- The block's type (e.g., paragraph, heading_1, image).
- Content details depending on the block type.
- Metadata such as timestamps, block ID, and any formatting or properties.
- Nested children blocks if applicable (though for "get" operation it returns the single block).
No binary data output is produced by this operation.
Example output structure (simplified):
{
"object": "block",
"id": "block-id-string",
"type": "paragraph",
"paragraph": {
"text": [
{
"type": "text",
"text": {
"content": "Example text",
"link": null
},
"annotations": {...},
"plain_text": "Example text",
"href": null
}
]
},
"created_time": "...",
"last_edited_time": "...",
...
}
Dependencies
- Requires a valid Notion API authentication token configured in n8n credentials.
- Uses Notion API endpoints to fetch block data.
- No additional external services beyond Notion API.
Troubleshooting
- Invalid Notion API credentials: The node will throw an error if the API key/token is invalid or missing. Ensure the credential is correctly set up in n8n.
- Block not found or invalid Block ID: If the Block ID does not exist or is malformed, the API will return an error. Verify the Block ID is correct.
- API rate limits: Frequent requests may hit Notion API rate limits causing errors. Implement retry logic or reduce request frequency.
- Network issues: Connectivity problems can cause request failures. Check network connection and proxy settings if applicable.