DocumentationWorkflowsApps and services

Notion Pages node

Pages in your Notion workspace: search, read, create, update, append content. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

9 min readUpdated

What this node does

Pages in your Notion workspace: search, read, create, update, append content.

Use Notion Pages as a clearly defined step in an anymize workflow.

  • Processes one input.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Notion Pages from the node catalog.
  2. 02If your Notion account is not connected yet, connect it right in the node panel or under Connectors.
  3. 03Complete the required fields and map values from previous steps.
  4. 04Run the node with a small test record and inspect its output.
  5. 05Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

  • Search pages
  • Read page
  • Create page
  • Append content
  • Update page
  • Write comment

Settings

FieldMeaningArea
ActionChoices: Search pages, Read page, Create page, Append content, Update page, Write commentStandard
Search termConfigure this value in the node panel.Standard
Count (max. 100)Configure this value in the node panel.Standard
Fetch all resultsFetches more result pages, up to 1000 results.Standard
Next page markerPicks up where the last fetch left off. Use the next page marker from the previous step.Standard
PageLink or ID of the page. The ID is at the end of the Notion URL.Standard
New page goes inChoices: A page, A databaseStandard
Parent page or databaseLink or ID of the page or database the new page is created under.Standard
Data sourceOnly if the new page goes into a database that has several data sources. Otherwise leave it empty.Standard
TitleConfigure this value in the node panel.Standard
FieldsColumn and new value, e.g. Status and Done. When creating, only if the new page goes into a database. Under a page, the step otherwise stops with a notice instead of dropping the values.Standard
TrashChoices: Don't change, Move to trash, Restore from trashStandard
ContentThe text of the page. Markdown is supported (e.g. # for headings).Standard
CommentConfigure this value in the node panel.Standard
Run once per itemOff (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.Standard
If one item fails"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.Standard
Pause between items (milliseconds)Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).Standard

Inputs and outputs

InputMeaningType
StandardReceives the complete result from the previous step.JSON
OutputMeaningType
StandardMakes the result available to the next step as JSON.JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Create weekly report in Notion: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "title": "Wochenbericht {{ $json.date }}",
  "content": "## Highlights\n\n{{ $json.summary }}"
}

Access and security

The node works with your own connected Notion account. It only sees and changes what this account is allowed to. Check the permissions shown when you connect. The matching area (Pages, Databases) must also be switched on in the settings of your Notion connection under Connectors. All areas are on by default.

"Allowed actions" in the settings of your Notion connection under Connectors also applies to this node and is checked on every run. With "Read only" or "Read and draft", only the read actions run: Search pages, Read page. These actions need "Allow changes": Create page, Append content, Update page, Write comment.

Keys and credentials belong in Workflow Secrets or your connected accounts. Never paste them as plain text into workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Connection rejected: reconnect the service and grant the permissions required by this step.
  • Action blocked: set "Allowed actions" of the connection under Connectors to "Allow changes", or pick a read action.
  • List processed once: enable per-item execution in advanced settings.