Notion Overlimit Writer
Create pages or write unlimited content to multiple Notion properties with multi-mapping support
Overview
This node updates existing Notion pages by allowing users to select the target page manually, from a database, or by searching all accessible pages. It supports complex content mappings to update multiple Notion properties, upload files, or append content to the page body. The node is useful for automating content updates in Notion, such as updating project details, appending notes, or managing file attachments across multiple properties.
Use Case Examples
- Updating a Notion page by manually entering its ID or URL and mapping input content to specific page properties.
- Selecting a page from a Notion database and uploading files to file properties while appending additional content to the page body.
- Searching all accessible pages to find a target page and applying multiple content mappings with different formatting and edit actions.
Properties
| Name | Meaning |
|---|---|
| Page Selection Mode | How to select the target Notion page to update, with options for manual ID/URL entry, selecting from database pages, or searching all accessible pages. |
| Page ID or URL | Notion page ID (32 hex characters) or page URL, used when selecting page manually. |
| Database | Select the database containing the target page, used when selecting page from a database. |
| Page | Select the page from the chosen database. |
| Search Pages | Search and select from all accessible pages. |
| Global Settings | Default settings applied to all content mappings, including allocation strategy, parallel processing, validation, retries, debug mode, and default edit actions for properties and page body. |
| Output Settings | Settings controlling output format and content, including whether to include input data, page properties, page body, comments, API rate limits, and batch size. |
| Content Mappings | Map input content to Notion properties or upload files to file properties, supporting multiple mapping types: content, files, and page body with various formatting and edit options. |
Output
JSON
success- Indicates if the update operation was successful.pageId- The ID of the Notion page that was updated.executionTime- Time taken to execute the update operation in milliseconds.mappingsProcessed- Number of content mappings processed.mappingsSuccessful- Number of successful content mappings.mappingsFailed- Number of failed content mappings.propertiesUpdated- List of properties that were updated on the page.totalCharactersProcessed- Total number of characters processed across all mappings.totalChunksCreated- Total number of content chunks created during processing.mappingErrors- Details of errors encountered during mapping processing, if any.partialSuccess- Indicates if the operation partially succeeded despite some mapping failures.error- Error details if the operation failed.inputData- Optional inclusion of input data from the previous node, based on settings.pageData- Formatted page data fetched from Notion, including properties, body, and optionally comments, depending on output settings.
Dependencies
- An API key credential for Notion API access
Troubleshooting
- Common issues include invalid or missing page IDs, incorrect property names, insufficient API permissions, and exceeding API rate limits.
- Error messages related to configuration validation indicate missing or incorrect parameters such as page selection mode or content mappings.
- Mapping processing errors may occur due to invalid content formats or API failures; enabling debug mode can help diagnose these issues.
- If the node fails to fetch page data, verify API credentials and page access rights.
- To resolve errors, check node parameters, ensure required fields are provided, and verify API credentials and permissions.
Links
- Notion API Documentation - Official documentation for the Notion API used by this node.
- n8n Notion Node Documentation - Documentation for the Notion node in n8n, providing usage details and examples.