Actions16
Overview
The node provides advanced integration with Notion, specifically allowing users to update properties of an existing Notion page. This operation is useful when you want to modify metadata or content attributes of a page without recreating it. Common scenarios include updating status fields, changing tags, modifying dates, or adjusting any custom property on a Notion page.
For example, you might use this node to:
- Change the "Status" select property of a project page from "In Progress" to "Completed".
- Update a date property to reflect a new deadline.
- Add or remove people assigned to a task page.
- Archive a page by setting its archived flag.
This flexibility makes it ideal for automating workflows that keep your Notion workspace up-to-date based on external triggers or data changes.
Properties
| Name | Meaning |
|---|---|
| Page ID | The unique identifier or URL of the Notion page to update. |
| Properties | A collection of one or more properties to update on the page. Each property includes: |
| - Name: The name of the property to update. | |
| - Type: The type of the property. Options include Title, Rich Text, Number, Select, Multi-select, Date, People, Files, Checkbox, URL, Email, Phone, Formula, Relation, Rollup, Created Time, Created By, Last Edited Time, Last Edited By. | |
| - Value: The value to set for the property. For complex types, this should be JSON-formatted. | |
| Additional Fields | Optional extra settings for the page update: |
| - Icon | An emoji or image URL to set as the page icon. |
| - Cover | A URL to set as the page cover image. |
| - Archive | Boolean flag indicating whether to archive the page (true to archive). |
Output
The node outputs the updated page object as returned by the Notion API. The output JSON contains all the standard Notion page fields, including the updated properties and metadata such as creation time, last edited time, and archival status.
No binary data is produced by this operation.
Dependencies
- Requires valid Notion API credentials configured in n8n to authenticate requests.
- Uses the Notion REST API endpoints for pages.
- No additional external dependencies beyond the Notion API and n8n environment.
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 n8n credentials.
- Invalid Page ID: If the Page ID or URL is incorrect or does not exist, the API call will fail. Verify the page identifier is correct.
- Malformed Property Value: Complex property values must be valid JSON strings. Improperly formatted JSON will cause errors. Use JSON validators or carefully format the input.
- Unsupported Property Type or Name: Using a property name or type not recognized by Notion will result in an error. Confirm the property exists in the target database schema.
- Archiving Conflicts: Setting the archive flag incorrectly may cause unexpected behavior. Use the dedicated archive operation if unsure.