Get Pages from Notion (Lookup) v1.0.0 Help ​

Retrieves a list of pages from Notion as individual pages or as part of a database.

How can I use the Step? ​

Use this Step when you need to fetch a list of pages or databases from Notion to integrate with your Lookup collection or for processing within your Flow. This can be useful for content synchronization, data migration, or building dynamic content repositories.

How does the Step work? ​

The Step utilizes the Notion API to fetch a list of pages based on the specified page type (either database or page). It can fetch either individual pages or databases based on the specified page type. The results are then returned and can be processed further or stored.

Prerequisites ​

  • Obtain a Notion Secret API key to authenticate requests and ensure you can access the Notion workspace to fetch data from it.

Input settings ​

  • Secret API key: the Notion Secret API key to authenticate requests. Required for authentication and accessing your Notion workspace.
  • Page type: the type of Notion page, either Database or Page to specify the type of Notion content you are retrieving.

Merge field settings ​

The Step returns the result as a JSON object and stores it under the Merge field name. To learn more about Merge fields and how to work with them, see our Merge fields guide.

Output example ​

The output object has the following properties:

  • object: [string] the type of object returned, a list in the provided example.
  • results: [array] an array of page objects, each representing a Notion page with its metadata and content.
  • next_cursor: [string|null] the cursor used for pagination; null if there are no more data to fetch.
  • has_more: [boolean] indicates whether there are more pages to fetch.
  • type: [string] the type of pages included in the results, either page or database.
  • page_or_database: [object] additional information about the page or database.
  • request_id: [string] the ID of the request for tracking and debugging purposes.

Example:

json
{
    "object": "list",
    "results": [],
    "next_cursor": null,
    "has_more": false,
    "type": "page_or_database",
    "page_or_database": {},
    "request_id": "46206ff0-84cc-443b-bc92-ac05a4b71cfa"
}
{
    "object": "list",
    "results": [],
    "next_cursor": null,
    "has_more": false,
    "type": "page_or_database",
    "page_or_database": {},
    "request_id": "46206ff0-84cc-443b-bc92-ac05a4b71cfa"
}

Error handling ​

By default, the Step handles errors using a separate exit. So if any error occurs during the Step execution, the Flow proceeds down the error exit. For more information, see Error and timeout handling.

Reporting ​

The Step automatically generates Reporting events during its execution, allowing for real-time tracking and analysis of its performance and user interactions. To learn more, see Reporting events

Service dependencies ​

  • flow builder - v2.28.3
  • event-manager - v2.3.0
  • deployer - v2.6.0
  • library v2.11.3
  • studio v2.64.1

Release notes ​

v1.0.0

  • Initial release