Create Document from Notion (Lookup) v1.0.0 Help ​

Сreates a new document in the specified Lookup collection using data fetched from Notion.

How can I use the Step? ​

Use this Step to create and populate a document in a Lookup collection with content sourced from Notion. You can use it to consolidate information from Notion into Lookup or automate the migration of documents from Notion to Lookup collections for better organization and retrieval.

How does the Step work? ​

The Step interacts with the Notion API to fetch the required data and then creates a new document in the specified Lookup collection. It requires the collection and document names in Lookup and the page ID from Notion. You can also provide a document description and settings for importing nested pages or database properties.

Prerequisites ​

  • Obtain a Notion Secret API key to authenticate requests and ensure you can access the Notion workspace to fetch data from it.
  • For custom authentication, ensure proper cross-account settings with the Super Admin permission level for account and Flow and the necessary account ID or authentication token.

Input settings ​

Configure the following parameters before using the Step:

  • Secret API key: the Notion Secret API key to authenticate requests. Required.
  • Collection: A Lookup collection where to create a document. Required.
  • Document name: the document you want to create. It must be between 3 and 100 characters long. Required.
  • Document description: a brief description of the document's content. It must be less than or equal to 2048 characters.
  • Page ID: the ID of the Notion page to fetch the content from. Required.
  • Page type: the type of Notion page, either Database or Page.
  • Import nested pages: option to include nested pages in the document (available only when Page is selected as the page type).
  • Import database properties: option to include database properties in the document (available only when Database is selected as the page type).

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:

  • id: [string] the id of the document.
  • createdAt: [string] the creation date and time of the document.
  • updatedAt: [string] the last update date and time of the document.
  • collection: [array] an array of objects representing the collection that the document belongs to. Each object has two properties:
    • beacon: [string] a unique identifier or locator for the collection within a specific system or database.
    • href: [string] the href value of the collection, valid for direct access or reference.
  • name: [string] the name of the document.
  • sourceUrl: [string] the source URL of the document.
  • status: [string] the status of the document.

Example:

json
{
  "id": "string",
  "createdAt": "string",
  "updatedAt": "string",
  "collection": [
    {
      "beacon": "string",
      "href": "string"
    }
  ],
  "name": "string",
  "sourceUrl": "string",
  "status": "string"
}
{
  "id": "string",
  "createdAt": "string",
  "updatedAt": "string",
  "collection": [
    {
      "beacon": "string",
      "href": "string"
    }
  ],
  "name": "string",
  "sourceUrl": "string",
  "status": "string"
}

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