Notion - Parable

Sync pages, databases, and users from Notion.

Overview
Setup Guide
Permissions
Troubleshooting

Connect Parable to Notion via an internal connection for access to pages, databases, and workspace data.

Pages & Databases

Page content, database records, properties

Users

Workspace members and collaborators

Data streams

This Provider Plugin defines 6 data streams.

Stream	Description	Sync
`users`	Workspace users	full
`databases`	Databases in the workspace	incremental
`database_items`	Items (pages) within a data source	incremental
`pages`	Pages in the workspace	incremental
`blocks`	Block children of a page	full
`comments`	Comments on a page or block	full

API token

What You’ll Need

Credential	What it is
Token	Internal connection token

Info: Setup access in Notion. These steps require Administrator, or a colleague with equivalent permissions who can create credentials for you. If that is not you, ask your Notion administrator.

Workspace Owner or Admin role
Pages/databases must be explicitly shared with the connection

Step 1: Create Connection

Go to Notion Creator Dashboard
Click Create a new connection
Fill in:

Field	Value
Name	`Parable` (Notion rejects names containing “Integration”)
Associated workspace	Select your workspace
Logo	Optional
Type	Internal

Step 2: Configure Capabilities

Under Configuration > Capabilities, enable:

Capability	Setting
Read content	✅
Update content	❌ (not needed)
Insert content	❌ (not needed)
Read comments	✅
Read user information	✅ (including email)

Step 3: Copy Token

Click Show next to the internal integration secret
Copy the token

Warning: Copy your token now! This is the only time it will be displayed. Store it in a secure password manager before closing this page.

The connection can only access pages and databases you explicitly share with it. You need to share each top-level page or database that contains data you want Parable to sync.For each top-level page or database:

Open it in Notion
Click ••• (three dots) menu in the top right
Click Add connections
Search for and select Parable

Tip: Child pages automatically inherit access from their parent. Share at the highest level that covers the content you need — for example, sharing a team workspace page gives the connection access to all pages nested underneath it.

Warning: Any page or database not explicitly shared (or nested under a shared parent) will be invisible to the connection.

Step 5: Enter values in the form

Token: Paste your Notion internal connection token.
Click Save & test connection.

List Users

curl -X GET "https://api.notion.com/v1/users" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Notion-Version: 2026-03-11"

Search Content

curl -X POST "https://api.notion.com/v1/search" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Notion-Version: 2026-03-11" \
  -H "Content-Type: application/json" \
  -d '{"page_size": 5}'

Success: Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now configure this Provider in Parable.

Tip: Rate Limits: Notion enforces rate limits of 3 requests/second average with bursts allowed. Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Blocks

Developer identifier: blocksBlocks. Block children of a page.

Enables: Reconstruct visible Notion page content from ordered block records and their nested rich-text fragments.
Scope: Reads the records selected by Notion’s /v1/blocks/{id}/children operation as a snapshot stream using full synchronization. This stream is opt-in. Only pages and databases explicitly shared with the Notion integration, plus their reachable children, are visible. Rich-text and block payloads represent content visible to the integration; external or uploaded file bytes are not fetched. Removal is recognized from the provider’s tombstone state rather than absence alone.

Archived

Developer identifier: blocks.archivedArchived. Whether the block has been archived (deleted). It distinguishes the provider-defined archived state or classification for the block.

Enables: Filter Blocks by whether the block has been archived (deleted) in blocks.archived; count true, false, and missing results separately.
Interpretation: Notion reports the block has been archived (deleted) as a boolean on each block; a missing field is unknown, not false.

Audio

Developer identifier: blocks.audioAudio. Audio block content. Present when type is ‘audio’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute audio in blocks.audio to the parent block; identify parent records where that nested audio object is absent.
Interpretation: Notion reports audio as a nested object on each block; optional children may be absent from a valid response.

Caption

Developer identifier: blocks.audio.captionCaption. Caption for the file. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned caption content in blocks.FileBlock.caption while preserving element order and attribution to the parent block.
Interpretation: Notion returns caption as ordered content or provider-generated content metadata on each file block; truncation, omission, and inaccessible source media can limit completeness.

Annotations

Developer identifier: blocks.audio.caption.annotationsAnnotations. Styling annotations for the rich text. It preserves the nested context needed to interpret the parent block.

Enables: Attribute annotations in blocks.RichTextObject.annotations to the parent block; identify parent records where that nested annotations object is absent.
Interpretation: Notion reports annotations as a nested object on each rich text object; optional children may be absent from a valid response.

Bold

Developer identifier: blocks.audio.caption.annotations.boldBold. Whether the text is bold. It distinguishes the provider-defined bold state or classification for the annotation.

Enables: Filter Blocks by whether the text is bold in blocks.Annotations.bold; count true, false, and missing results separately.
Interpretation: Notion reports the text is bold as a boolean on each annotation; a missing field is unknown, not false.

Code

Developer identifier: blocks.audio.caption.annotations.codeCode. Whether the text is displayed as inline code. It distinguishes the provider-defined code state or classification for the annotation.

Enables: Filter Blocks by whether the text is displayed as inline code in blocks.Annotations.code; count true, false, and missing results separately.
Interpretation: Notion reports the text is displayed as inline code as a boolean on each annotation; a missing field is unknown, not false.

Color

Developer identifier: blocks.audio.caption.annotations.colorColor. Text color or background color (e.g., ‘default’, ‘red’, ‘blue_background’). It supplies the returned color text needed to understand the annotation in context.

Enables: Search the returned color text in blocks.Annotations.color and attribute each match to its parent block and reported author when available.
Interpretation: Notion supplies color as returned text on each annotation; truncation, formatting, and access boundaries can limit completeness.

Italic

Developer identifier: blocks.audio.caption.annotations.italicItalic. Whether the text is italic. It distinguishes the provider-defined italic state or classification for the annotation.

Enables: Filter Blocks by whether the text is italic in blocks.Annotations.italic; count true, false, and missing results separately.
Interpretation: Notion reports the text is italic as a boolean on each annotation; a missing field is unknown, not false.

Strikethrough

Developer identifier: blocks.audio.caption.annotations.strikethroughStrikethrough. Whether the text has strikethrough. It distinguishes the provider-defined strikethrough state or classification for the annotation.

Enables: Filter Blocks by whether the text has strikethrough in blocks.Annotations.strikethrough; count true, false, and missing results separately.
Interpretation: Notion reports the text has strikethrough as a boolean on each annotation; a missing field is unknown, not false.

Underline

Developer identifier: blocks.audio.caption.annotations.underlineUnderline. Whether the text is underlined. It distinguishes the provider-defined underline state or classification for the annotation.

Enables: Filter Blocks by whether the text is underlined in blocks.Annotations.underline; count true, false, and missing results separately.
Interpretation: Notion reports the text is underlined as a boolean on each annotation; a missing field is unknown, not false.

Equation

Developer identifier: blocks.audio.caption.equationEquation. Equation content. Present when type is ‘equation’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute equation in blocks.RichTextObject.equation to the parent block; identify parent records where that nested equation object is absent.
Interpretation: Notion reports equation as a nested object on each rich text object; optional children may be absent from a valid response.

Expression

Developer identifier: blocks.audio.caption.equation.expressionExpression. The LaTeX/KaTeX expression. It must be interpreted with the enclosing provider field name, type, or custom schema for the equation content.

Enables: Interpret blocks.EquationContent.expression with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: Notion reports expression under the enclosing custom or typed field contract on each equation content; compare it only with values from the same provider key and type.

Href

Developer identifier: blocks.audio.caption.hrefHref. URL link if the text is a link. It locates the provider resource or path associated with the rich text object.

Enables: Associate each rich text object with the resource identified by href in blocks.RichTextObject.href; verify the link resolves to the expected Notion object.
Interpretation: Notion reports href as a resource locator for each rich text object; access still depends on viewer permissions and the URL may expire or change.

Mention

Developer identifier: blocks.audio.caption.mentionMention. Mention content. Present when type is ‘mention’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute mention in blocks.RichTextObject.mention to the parent block; identify parent records where that nested mention object is absent.
Interpretation: Notion reports mention as a nested object on each rich text object; optional children may be absent from a valid response.

Database

Developer identifier: blocks.audio.caption.mention.databaseDatabase. Database mention. Present when type is ‘database’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute database in blocks.MentionContent.database to the parent block; identify parent records where that nested database object is absent.
Interpretation: Notion reports database as a nested object on each mention content; optional children may be absent from a valid response.

Developer identifier: blocks.audio.caption.mention.database.idID. The UUID of the referenced object. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each ID reference in Blocks to the referenced ID reference through blocks.IdReference.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its ID reference namespace; it is not a universal identity outside Notion.

Date

Developer identifier: blocks.audio.caption.mention.dateDate. Date mention. Present when type is ‘date’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute date in blocks.MentionContent.date to the parent block; identify parent records where that nested date object is absent.
Interpretation: Notion reports date as a nested object on each mention content; optional children may be absent from a valid response.

End

Developer identifier: blocks.audio.caption.mention.date.endEnd. End date or datetime in ISO 8601 format, null for single dates. It anchors the block on the provider’s reported timeline.

Enables: Filter Blocks by end in blocks.DateValue.end; pair that boundary with the corresponding start before measuring elapsed time.
Interpretation: Notion reports end as a timestamp on each date value; timezone and precision follow this API field, and absence is not an inferred event time.

Start

Developer identifier: blocks.audio.caption.mention.date.startStart. Start date or datetime in ISO 8601 format. It anchors the block on the provider’s reported timeline.

Enables: Filter Blocks by start in blocks.DateValue.start; pair that boundary with the corresponding end before measuring elapsed time.
Interpretation: Notion reports start as a timestamp on each date value; timezone and precision follow this API field, and absence is not an inferred event time.

Time Zone

Developer identifier: blocks.audio.caption.mention.date.time_zoneTime Zone. IANA time zone identifier if the date includes a time. It is needed to interpret companion dates and times for the date value in the provider’s intended zone.

Enables: Apply the zone in blocks.DateValue.time_zone when converting the block’s companion start, end, or scheduled timestamps; do not infer it from locale.
Interpretation: Notion reports time zone as a timezone identifier for each date value; supported IANA or provider-specific names and daylight-saving behavior must be preserved.

Link Preview

Developer identifier: blocks.audio.caption.mention.link_previewLink Preview. Link preview mention. Present when type is ‘link_preview’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute link preview in blocks.MentionContent.link_preview to the parent block; identify parent records where that nested link preview object is absent.
Interpretation: Notion reports link preview as a nested object on each mention content; optional children may be absent from a valid response.

URL

Developer identifier: blocks.audio.caption.mention.link_preview.urlURL. The URL being previewed. It locates the provider resource or path associated with the link preview content.

Enables: Associate each link preview content with the resource identified by URL in blocks.LinkPreviewContent.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each link preview content; access still depends on viewer permissions and the URL may expire or change.

Page

Developer identifier: blocks.audio.caption.mention.pagePage. Page mention. Present when type is ‘page’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute page in blocks.MentionContent.page to the parent block; identify parent records where that nested page object is absent.
Interpretation: Notion reports page as a nested object on each mention content; optional children may be absent from a valid response.

Template Mention

Developer identifier: blocks.audio.caption.mention.template_mentionTemplate Mention. Template mention data. Present when type is ‘template_mention’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute template mention in blocks.MentionContent.template_mention to the parent block; identify parent records where that nested template mention object is absent.
Interpretation: Notion reports template mention as a nested object on each mention content; optional children may be absent from a valid response.

Type

Developer identifier: blocks.audio.caption.mention.typeType. The type of mention (user, page, database, date, link_preview, template_mention). It distinguishes the provider-defined type state or classification for the mention content.

Enables: Segment mention content entries in Blocks by type in blocks.MentionContent.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each mention content; preserve unknown labels rather than mapping them by assumption.

User

Developer identifier: blocks.audio.caption.mention.userUser. User mention. Present when type is ‘user’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute user in blocks.MentionContent.user to the parent block; identify parent records where that nested user object is absent.
Interpretation: Notion reports user as a nested object on each mention content; optional children may be absent from a valid response.

Developer identifier: blocks.audio.caption.mention.user.idID. UUID of the user. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each partial user in Blocks to the referenced partial user through blocks.PartialUser.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its partial user namespace; it is not a universal identity outside Notion.

Object

Developer identifier: blocks.audio.caption.mention.user.objectObject. Always ‘user’ for user objects. It distinguishes the provider-defined object state or classification for the partial user.

Enables: Filter Blocks by the exact Notion-defined object in blocks.PartialUser.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each partial user; preserve unknown and newly introduced labels.

Plain Text

Developer identifier: blocks.audio.caption.plain_textPlain Text. Plain text representation without annotations. It defines the content surface available for this block.

Enables: Locate rich text object records by plain text in blocks.RichTextObject.plain_text; attribute each text match to its parent block and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Text

Developer identifier: blocks.audio.caption.textText. Text content. Present when type is ‘text’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute text in blocks.RichTextObject.text to the parent block; identify parent records where that nested text object is absent.
Interpretation: Notion reports text as a nested object on each rich text object; optional children may be absent from a valid response.

Content

Developer identifier: blocks.audio.caption.text.contentContent. The actual text content. It defines the content surface available for this block.

Enables: Locate text content records by content in blocks.TextContent.content; attribute each text match to its parent block and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Link

Developer identifier: blocks.audio.caption.text.linkLink. Optional link object if the text is a hyperlink. It preserves the nested context needed to interpret the parent block.

Enables: Attribute link in blocks.TextContent.link to the parent block; identify parent records where that nested link object is absent.
Interpretation: Notion reports link as a nested object on each text content; optional children may be absent from a valid response.

URL

Developer identifier: blocks.audio.caption.text.link.urlURL. The URL the text links to. It locates the provider resource or path associated with the link object.

Enables: Associate each link object with the resource identified by URL in blocks.LinkObject.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each link object; access still depends on viewer permissions and the URL may expire or change.

Type

Developer identifier: blocks.audio.caption.typeType. The type of rich text (text, mention, equation). It distinguishes the provider-defined type state or classification for the rich text object.

Enables: Segment rich text object entries in Blocks by type in blocks.RichTextObject.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each rich text object; preserve unknown labels rather than mapping them by assumption.

External

Developer identifier: blocks.audio.externalExternal. External file details. Present when type is ‘external’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute external in blocks.FileBlock.external to the parent block; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each file block; optional children may be absent from a valid response.

URL

Developer identifier: blocks.audio.external.urlURL. URL of the external file. It locates the provider resource or path associated with the external file.

Enables: Associate each external file with the resource identified by URL in blocks.ExternalFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each external file; access still depends on viewer permissions and the URL may expire or change.

File

Developer identifier: blocks.audio.fileFile. Notion-hosted file details. Present when type is ‘file’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute file in blocks.FileBlock.file to the parent block; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each file block; optional children may be absent from a valid response.

Expiry Time

Developer identifier: blocks.audio.file.expiry_timeExpiry Time. ISO 8601 expiration time for the temporary URL. It anchors the block on the provider’s reported timeline.

Enables: Order Blocks by expiry time in blocks.NotionHostedFile.expiry_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports expiry time as a timestamp on each Notion hosted file; timezone and precision follow this API field, and absence is not an inferred event time. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: blocks.audio.file.urlURL. Temporary authenticated URL for the Notion-hosted file. It locates the provider resource or path associated with the Notion hosted file.

Enables: Associate each Notion hosted file with the resource identified by URL in blocks.NotionHostedFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion hosted file; access still depends on viewer permissions and the URL may expire or change. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Name

Developer identifier: blocks.audio.nameName. Name of the file. It gives the file block a human-readable provider label while its identifier remains the stable reference.

Enables: Label each file block with name from blocks.FileBlock.name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports name as display text for each file block; names are mutable and are not stable identities.

Type

Developer identifier: blocks.audio.typeType. Whether the file is hosted by Notion (‘file’) or externally (‘external’). It distinguishes the provider-defined type state or classification for the file block.

Enables: Segment file block entries in Blocks by type in blocks.FileBlock.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each file block; preserve unknown labels rather than mapping them by assumption.

Bookmark

Developer identifier: blocks.bookmarkBookmark. Bookmark block content. Present when type is ‘bookmark’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute bookmark in blocks.bookmark to the parent block; identify parent records where that nested bookmark object is absent.
Interpretation: Notion reports bookmark as a nested object on each block; optional children may be absent from a valid response.

Caption

Developer identifier: blocks.bookmark.captionCaption. Caption for the bookmark. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned caption content in blocks.BookmarkBlock.caption while preserving element order and attribution to the parent block.
Interpretation: Notion returns caption as ordered content or provider-generated content metadata on each bookmark block; truncation, omission, and inaccessible source media can limit completeness.

URL

Developer identifier: blocks.bookmark.urlURL. The bookmarked URL. It locates the provider resource or path associated with the bookmark block.

Enables: Associate each bookmark block with the resource identified by URL in blocks.BookmarkBlock.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each bookmark block; access still depends on viewer permissions and the URL may expire or change.

Bulleted List Item

Developer identifier: blocks.bulleted_list_itemBulleted List Item. Bulleted list item content. Present when type is ‘bulleted_list_item’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute bulleted list item in blocks.bulleted_list_item to the parent block; identify parent records where that nested bulleted list item object is absent.
Interpretation: Notion reports bulleted list item as a nested object on each block; optional children may be absent from a valid response.

Color

Developer identifier: blocks.bulleted_list_item.colorColor. Color of the block text or background. It supplies the returned color text needed to understand the rich text block in context.

Enables: Search the returned color text in blocks.RichTextBlock.color and attribute each match to its parent block and reported author when available.
Interpretation: Notion supplies color as returned text on each rich text block; truncation, formatting, and access boundaries can limit completeness.

Rich Text

Developer identifier: blocks.bulleted_list_item.rich_textRich Text. Array of rich text objects forming the block content. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned rich text content in blocks.RichTextBlock.rich_text while preserving element order and attribution to the parent block.
Interpretation: Notion returns rich text as ordered content or provider-generated content metadata on each rich text block; truncation, omission, and inaccessible source media can limit completeness.

Callout

Developer identifier: blocks.calloutCallout. Callout block content. Present when type is ‘callout’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute callout in blocks.callout to the parent block; identify parent records where that nested callout object is absent.
Interpretation: Notion reports callout as a nested object on each block; optional children may be absent from a valid response.

Color

Developer identifier: blocks.callout.colorColor. Color of the callout background. It distinguishes the provider-defined color state or classification for the callout block.

Enables: Filter Blocks by the exact Notion-defined color in blocks.CalloutBlock.color and preserve unknown values as distinct categories.
Interpretation: Notion supplies color from its own taxonomy on each callout block; preserve unknown and newly introduced labels.

Icon

Developer identifier: blocks.callout.iconIcon. The icon displayed in the callout. It preserves the nested context needed to interpret the parent block.

Enables: Attribute icon in blocks.CalloutBlock.icon to the parent block; identify parent records where that nested icon object is absent.
Interpretation: Notion reports icon as a nested object on each callout block; optional children may be absent from a valid response.

Emoji

Developer identifier: blocks.callout.icon.emojiEmoji. The emoji character. Present when type is ‘emoji’. It distinguishes the provider-defined emoji state or classification for the icon object.

Enables: Filter Blocks by the exact Notion-defined emoji in blocks.IconObject.emoji and preserve unknown values as distinct categories.
Interpretation: Notion supplies emoji from its own taxonomy on each icon object; preserve unknown and newly introduced labels.

External

Developer identifier: blocks.callout.icon.externalExternal. External file reference. Present when type is ‘external’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute external in blocks.IconObject.external to the parent block; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each icon object; optional children may be absent from a valid response.

Type

Developer identifier: blocks.callout.icon.typeType. The type of icon (‘emoji’ or ‘external’). It distinguishes the provider-defined type state or classification for the icon object.

Enables: Segment icon object entries in Blocks by type in blocks.IconObject.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each icon object; preserve unknown labels rather than mapping them by assumption.

Rich Text

Developer identifier: blocks.callout.rich_textRich Text. Array of rich text objects forming the callout content. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned rich text content in blocks.CalloutBlock.rich_text while preserving element order and attribution to the parent block.
Interpretation: Notion returns rich text as ordered content or provider-generated content metadata on each callout block; truncation, omission, and inaccessible source media can limit completeness.

Child Database

Developer identifier: blocks.child_databaseChild Database. Child database block content. Present when type is ‘child_database’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute child database in blocks.child_database to the parent block; identify parent records where that nested child database object is absent.
Interpretation: Notion reports child database as a nested object on each block; optional children may be absent from a valid response.

Title

Developer identifier: blocks.child_database.titleTitle. The title of the child database. It gives the child database block a human-readable provider label while its identifier remains the stable reference.

Enables: Label each child database block with title from blocks.ChildDatabaseBlock.title; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports title as display text for each child database block; names are mutable and are not stable identities.

Child Page

Developer identifier: blocks.child_pageChild Page. Child page block content. Present when type is ‘child_page’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute child page in blocks.child_page to the parent block; identify parent records where that nested child page object is absent.
Interpretation: Notion reports child page as a nested object on each block; optional children may be absent from a valid response.

Title

Developer identifier: blocks.child_page.titleTitle. The title of the child page. It gives the child page block a human-readable provider label while its identifier remains the stable reference.

Enables: Label each child page block with title from blocks.ChildPageBlock.title; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports title as display text for each child page block; names are mutable and are not stable identities.

Code

Developer identifier: blocks.codeCode. Code block content. Present when type is ‘code’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute code in blocks.code to the parent block; identify parent records where that nested code object is absent.
Interpretation: Notion reports code as a nested object on each block; optional children may be absent from a valid response.

Caption

Developer identifier: blocks.code.captionCaption. Caption for the code block. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned caption content in blocks.CodeBlock.caption while preserving element order and attribution to the parent block.
Interpretation: Notion returns caption as ordered content or provider-generated content metadata on each code block; truncation, omission, and inaccessible source media can limit completeness.

Language

Developer identifier: blocks.code.languageLanguage. Programming language of the code block (e.g., ‘javascript’, ‘python’). It supplies the language profile facet used to reconcile or attribute the code block.

Enables: Reconcile the block’s language in blocks.CodeBlock.language with its provider profile or directory identity; confirm ambiguous matches with the stable provider ID.
Interpretation: Notion reports language as a mutable profile or directory attribute on each code block; it may be absent, shared, or non-unique.

Rich Text

Developer identifier: blocks.code.rich_textRich Text. Array of rich text objects forming the code content. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned rich text content in blocks.CodeBlock.rich_text while preserving element order and attribution to the parent block.
Interpretation: Notion returns rich text as ordered content or provider-generated content metadata on each code block; truncation, omission, and inaccessible source media can limit completeness.

Column

Developer identifier: blocks.columnColumn. Column block content. Present when type is ‘column’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute column in blocks.column to the parent block; identify parent records where that nested column object is absent.
Interpretation: Notion reports column as a nested object on each block; optional children may be absent from a valid response.

Column List

Developer identifier: blocks.column_listColumn List. Column list block content. Present when type is ‘column_list’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute column list in blocks.column_list to the parent block; identify parent records where that nested column list object is absent.
Interpretation: Notion reports column list as a nested object on each block; optional children may be absent from a valid response.

Created By

Developer identifier: blocks.created_byCreated By. User who created the block. It preserves the nested context needed to interpret the parent block.

Enables: Attribute created by in blocks.created_by to the parent block; identify parent records where that nested created by object is absent.
Interpretation: Notion reports created by as a nested object on each block; optional children may be absent from a valid response.

Created Time

Developer identifier: blocks.created_timeCreated Time. ISO 8601 timestamp when the block was created. It anchors the block on the provider’s reported timeline.

Enables: Order Blocks by created time in blocks.created_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports created time as a timestamp on each block; timezone and precision follow this API field, and absence is not an inferred event time.

Divider

Developer identifier: blocks.dividerDivider. Divider block content. Present when type is ‘divider’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute divider in blocks.divider to the parent block; identify parent records where that nested divider object is absent.
Interpretation: Notion reports divider as a nested object on each block; optional children may be absent from a valid response.

Embed

Developer identifier: blocks.embedEmbed. Embed block content. Present when type is ‘embed’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute embed in blocks.embed to the parent block; identify parent records where that nested embed object is absent.
Interpretation: Notion reports embed as a nested object on each block; optional children may be absent from a valid response.

Caption

Developer identifier: blocks.embed.captionCaption. Caption for the embed. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned caption content in blocks.EmbedBlock.caption while preserving element order and attribution to the parent block.
Interpretation: Notion returns caption as ordered content or provider-generated content metadata on each embed block; truncation, omission, and inaccessible source media can limit completeness.

URL

Developer identifier: blocks.embed.urlURL. The URL of the embedded content. It locates the provider resource or path associated with the embed block.

Enables: Associate each embed block with the resource identified by URL in blocks.EmbedBlock.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each embed block; access still depends on viewer permissions and the URL may expire or change.

Equation

Developer identifier: blocks.equationEquation. Equation block content. Present when type is ‘equation’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute equation in blocks.equation to the parent block; identify parent records where that nested equation object is absent.
Interpretation: Notion reports equation as a nested object on each block; optional children may be absent from a valid response.

Expression

Developer identifier: blocks.equation.expressionExpression. The LaTeX/KaTeX expression. It must be interpreted with the enclosing provider field name, type, or custom schema for the equation block.

Enables: Interpret blocks.EquationBlock.expression with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: Notion reports expression under the enclosing custom or typed field contract on each equation block; compare it only with values from the same provider key and type.

File

Developer identifier: blocks.fileFile. File block content. Present when type is ‘file’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute file in blocks.file to the parent block; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each block; optional children may be absent from a valid response.

Has Children

Developer identifier: blocks.has_childrenHas Children. Whether this block has nested child blocks. It distinguishes the provider-defined has children state or classification for the block.

Enables: Filter Blocks by whether this block has nested child blocks in blocks.has_children; count true, false, and missing results separately.
Interpretation: Notion reports this block has nested child blocks as a boolean on each block; a missing field is unknown, not false.

Heading 1

Developer identifier: blocks.heading_1Heading 1. Heading 1 block content. Present when type is ‘heading_1’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute heading 1 in blocks.heading_1 to the parent block; identify parent records where that nested heading 1 object is absent.
Interpretation: Notion reports heading 1 as a nested object on each block; optional children may be absent from a valid response.

Color

Developer identifier: blocks.heading_1.colorColor. Color of the heading text or background. It supplies the returned color text needed to understand the heading block in context.

Enables: Search the returned color text in blocks.HeadingBlock.color and attribute each match to its parent block and reported author when available.
Interpretation: Notion supplies color as returned text on each heading block; truncation, formatting, and access boundaries can limit completeness.

Is Toggleable

Developer identifier: blocks.heading_1.is_toggleableIs Toggleable. Whether the heading can be toggled to show/hide children. It distinguishes the provider-defined is toggleable state or classification for the heading block.

Enables: Filter Blocks by whether the heading can be toggled to show/hide children in blocks.HeadingBlock.is_toggleable; count true, false, and missing results separately.
Interpretation: Notion reports the heading can be toggled to show/hide children as a boolean on each heading block; a missing field is unknown, not false.

Rich Text

Developer identifier: blocks.heading_1.rich_textRich Text. Array of rich text objects forming the heading content. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned rich text content in blocks.HeadingBlock.rich_text while preserving element order and attribution to the parent block.
Interpretation: Notion returns rich text as ordered content or provider-generated content metadata on each heading block; truncation, omission, and inaccessible source media can limit completeness.

Heading 2

Developer identifier: blocks.heading_2Heading 2. Heading 2 block content. Present when type is ‘heading_2’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute heading 2 in blocks.heading_2 to the parent block; identify parent records where that nested heading 2 object is absent.
Interpretation: Notion reports heading 2 as a nested object on each block; optional children may be absent from a valid response.

Heading 3

Developer identifier: blocks.heading_3Heading 3. Heading 3 block content. Present when type is ‘heading_3’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute heading 3 in blocks.heading_3 to the parent block; identify parent records where that nested heading 3 object is absent.
Interpretation: Notion reports heading 3 as a nested object on each block; optional children may be absent from a valid response.

Developer identifier: blocks.idID. Unique identifier for the block (UUID). It provides the reference needed to connect the block to the corresponding provider object.

Enables: Match repeated block entries on ID in blocks.id; collapse only entries that share this declared transform key.
Interpretation: Notion reports ID as an identifier in its block namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key.

Image

Developer identifier: blocks.imageImage. Image block content. Present when type is ‘image’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute image in blocks.image to the parent block; identify parent records where that nested image object is absent.
Interpretation: Notion reports image as a nested object on each block; optional children may be absent from a valid response.

In Trash

Developer identifier: blocks.in_trashIn Trash. Whether the block is in the trash. It distinguishes the provider-defined in trash state or classification for the block.

Enables: Filter Blocks by whether the block is in the trash in blocks.in_trash; count true, false, and missing results separately.
Interpretation: Notion reports the block is in the trash as a boolean on each block; a missing field is unknown, not false.

Is Locked

Developer identifier: blocks.is_lockedIs Locked. Whether the block is locked from edits. It distinguishes the provider-defined is locked state or classification for the block.

Enables: Filter Blocks by whether the block is locked from edits in blocks.is_locked; count true, false, and missing results separately.
Interpretation: Notion reports the block is locked from edits as a boolean on each block; a missing field is unknown, not false.

Last Edited By

Developer identifier: blocks.last_edited_byLast Edited By. User who last edited the block. It preserves the nested context needed to interpret the parent block.

Enables: Attribute last edited by in blocks.last_edited_by to the parent block; identify parent records where that nested last edited by object is absent.
Interpretation: Notion reports last edited by as a nested object on each block; optional children may be absent from a valid response.

Last Edited Time

Developer identifier: blocks.last_edited_timeLast Edited Time. ISO 8601 timestamp when the block was last modified. It anchors the block on the provider’s reported timeline.

Enables: Order Blocks by last edited time in blocks.last_edited_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports last edited time as a timestamp on each block; timezone and precision follow this API field, and absence is not an inferred event time. A connector directive uses this field to order records for latest-state or incremental processing.

Link Preview

Developer identifier: blocks.link_previewLink Preview. Link preview block content. Present when type is ‘link_preview’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute link preview in blocks.link_preview to the parent block; identify parent records where that nested link preview object is absent.
Interpretation: Notion reports link preview as a nested object on each block; optional children may be absent from a valid response.

URL

Developer identifier: blocks.link_preview.urlURL. The URL being previewed. It locates the provider resource or path associated with the link preview block.

Enables: Associate each link preview block with the resource identified by URL in blocks.LinkPreviewBlock.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each link preview block; access still depends on viewer permissions and the URL may expire or change.

Link To Page

Developer identifier: blocks.link_to_pageLink To Page. Link to page block content. Present when type is ‘link_to_page’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute link to page in blocks.link_to_page to the parent block; identify parent records where that nested link to page object is absent.
Interpretation: Notion reports link to page as a nested object on each block; optional children may be absent from a valid response.

Comment ID

Developer identifier: blocks.link_to_page.comment_idComment ID. The ID of the linked comment. Present when type is ‘comment_id’. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each link to page block in Blocks to the referenced comment through blocks.LinkToPageBlock.comment_id; flag comment ID values that do not resolve in that provider namespace.
Interpretation: Notion reports comment ID as an identifier in its comment namespace; it is not a universal identity outside Notion.

Database ID

Developer identifier: blocks.link_to_page.database_idDatabase ID. The ID of the linked database. Present when type is ‘database_id’. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each link to page block in Blocks to the referenced database through blocks.LinkToPageBlock.database_id; flag database ID values that do not resolve in that provider namespace.
Interpretation: Notion reports database ID as an identifier in its database namespace; it is not a universal identity outside Notion.

Page ID

Developer identifier: blocks.link_to_page.page_idPage ID. The ID of the linked page. Present when type is ‘page_id’. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each link to page block in Blocks to the referenced page through blocks.LinkToPageBlock.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Notion reports page ID as an identifier in its page namespace; it is not a universal identity outside Notion.

Type

Developer identifier: blocks.link_to_page.typeType. The type of link (‘page_id’, ‘database_id’, or ‘comment_id’). It locates the provider resource or path associated with the link to page block.

Enables: Segment link to page block entries in Blocks by type in blocks.LinkToPageBlock.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each link to page block; preserve unknown labels rather than mapping them by assumption.

Numbered List Item

Developer identifier: blocks.numbered_list_itemNumbered List Item. Numbered list item content. Present when type is ‘numbered_list_item’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute numbered list item in blocks.numbered_list_item to the parent block; identify parent records where that nested numbered list item object is absent.
Interpretation: Notion reports numbered list item as a nested object on each block; optional children may be absent from a valid response.

Object

Developer identifier: blocks.objectObject. Always ‘block’ for block objects. It distinguishes the provider-defined object state or classification for the block.

Enables: Filter Blocks by the exact Notion-defined object in blocks.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each block; preserve unknown and newly introduced labels.

Page ID

Developer identifier: blocks.page_idPage ID. Parent page reference copied into each block because the child operation does not return that relationship. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each block in Blocks to the referenced page through blocks.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Parable copies page ID from the parent traversal record into each block; the child Notion operation does not return it.

Paragraph

Developer identifier: blocks.paragraphParagraph. Paragraph block content. Present when type is ‘paragraph’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute paragraph in blocks.paragraph to the parent block; identify parent records where that nested paragraph object is absent.
Interpretation: Notion reports paragraph as a nested object on each block; optional children may be absent from a valid response.

Parent

Developer identifier: blocks.parentParent. Parent object reference (page_id, block_id, database_id, or workspace). It preserves the nested context needed to interpret the parent block.

Enables: Attribute parent in blocks.parent to the parent block; identify parent records where that nested parent object is absent.
Interpretation: Notion reports parent as a nested object on each block; optional children may be absent from a valid response.

Block ID

Developer identifier: blocks.parent.block_idBlock ID. The ID of the parent block. Present when type is ‘block_id’. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each block parent in Blocks to the referenced block through blocks.BlockParent.block_id; flag block ID values that do not resolve in that provider namespace.
Interpretation: Notion reports block ID as an identifier in its block namespace; it is not a universal identity outside Notion.

Database ID

Developer identifier: blocks.parent.database_idDatabase ID. The ID of the parent database. Present when type is ‘database_id’. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each block parent in Blocks to the referenced database through blocks.BlockParent.database_id; flag database ID values that do not resolve in that provider namespace.
Interpretation: Notion reports database ID as an identifier in its database namespace; it is not a universal identity outside Notion.

Page ID

Developer identifier: blocks.parent.page_idPage ID. The ID of the parent page. Present when type is ‘page_id’. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each block parent in Blocks to the referenced page through blocks.BlockParent.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Notion reports page ID as an identifier in its page namespace; it is not a universal identity outside Notion.

Type

Developer identifier: blocks.parent.typeType. The type of parent (page_id, block_id, database_id, workspace). It distinguishes the provider-defined type state or classification for the block parent.

Enables: Segment block parent entries in Blocks by type in blocks.BlockParent.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each block parent; preserve unknown labels rather than mapping them by assumption.

Workspace

Developer identifier: blocks.parent.workspaceWorkspace. True if the parent is the workspace. Present when type is ‘workspace’. It distinguishes the provider-defined workspace state or classification for the block parent.

Enables: Filter Blocks by whether true if the parent is the workspace in blocks.BlockParent.workspace; count true, false, and missing results separately.
Interpretation: Notion reports true if the parent is the workspace as a boolean on each block parent; a missing field is unknown, not false.

PDF

Developer identifier: blocks.pdfPDF. PDF block content. Present when type is ‘pdf’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute pdf in blocks.pdf to the parent block; identify parent records where that nested pdf object is absent.
Interpretation: Notion reports pdf as a nested object on each block; optional children may be absent from a valid response.

Public URL

Developer identifier: blocks.public_urlPublic URL. Public-facing Notion URL for the block, when the block belongs to a shared page. It locates the provider resource or path associated with the block.

Enables: Associate each block with the resource identified by public URL in blocks.public_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports public URL as a resource locator for each block; access still depends on viewer permissions and the URL may expire or change.

Quote

Developer identifier: blocks.quoteQuote. Quote block content. Present when type is ‘quote’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute quote in blocks.quote to the parent block; identify parent records where that nested quote object is absent.
Interpretation: Notion reports quote as a nested object on each block; optional children may be absent from a valid response.

Synced Block

Developer identifier: blocks.synced_blockSynced Block. Synced block content. Present when type is ‘synced_block’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute synced block in blocks.synced_block to the parent block; identify parent records where that nested synced block object is absent.
Interpretation: Notion reports synced block as a nested object on each block; optional children may be absent from a valid response.

Synced From

Developer identifier: blocks.synced_block.synced_fromSynced From. Reference to the original synced block. Null if this is the original. It preserves the nested context needed to interpret the parent block.

Enables: Attribute synced from in blocks.SyncedBlock.synced_from to the parent block; identify parent records where that nested synced from object is absent.
Interpretation: Notion reports synced from as a nested object on each synced block; optional children may be absent from a valid response.

Block ID

Developer identifier: blocks.synced_block.synced_from.block_idBlock ID. The ID of the original synced block. It provides the reference needed to connect the block to the corresponding provider object.

Enables: Connect each synced from in Blocks to the referenced block through blocks.SyncedFrom.block_id; flag block ID values that do not resolve in that provider namespace.
Interpretation: Notion reports block ID as an identifier in its block namespace; it is not a universal identity outside Notion.

Type

Developer identifier: blocks.synced_block.synced_from.typeType. Always ‘block_id’. It distinguishes the provider-defined type state or classification for the synced from.

Enables: Segment synced from entries in Blocks by type in blocks.SyncedFrom.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each synced from; preserve unknown labels rather than mapping them by assumption.

Table

Developer identifier: blocks.tableTable. Table block content. Present when type is ‘table’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute table in blocks.table to the parent block; identify parent records where that nested table object is absent.
Interpretation: Notion reports table as a nested object on each block; optional children may be absent from a valid response.

Has Column Header

Developer identifier: blocks.table.has_column_headerHas Column Header. Whether the first row is a header row. It distinguishes the provider-defined has column header state or classification for the table block.

Enables: Filter Blocks by whether the first row is a header row in blocks.TableBlock.has_column_header; count true, false, and missing results separately.
Interpretation: Notion reports the first row is a header row as a boolean on each table block; a missing field is unknown, not false.

Has Row Header

Developer identifier: blocks.table.has_row_headerHas Row Header. Whether the first column is a header column. It distinguishes the provider-defined has row header state or classification for the table block.

Enables: Filter Blocks by whether the first column is a header column in blocks.TableBlock.has_row_header; count true, false, and missing results separately.
Interpretation: Notion reports the first column is a header column as a boolean on each table block; a missing field is unknown, not false.

Table Width

Developer identifier: blocks.table.table_widthTable Width. Number of columns in the table. It supplies the table width measure for the table block at the provider’s declared unit and grain.

Enables: Measure table width through blocks.TableBlock.table_width for each table block and compare only values with the same unit and record grain.
Interpretation: Notion reports table width as a measure on each table block; compare only records with the same unit and aggregation grain.

Table Of Contents

Developer identifier: blocks.table_of_contentsTable Of Contents. Table of contents block content. Present when type is ‘table_of_contents’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute table of contents in blocks.table_of_contents to the parent block; identify parent records where that nested table of contents object is absent.
Interpretation: Notion reports table of contents as a nested object on each block; optional children may be absent from a valid response.

Color

Developer identifier: blocks.table_of_contents.colorColor. Color of the table of contents text. It supplies the returned color text needed to understand the table of contents block in context.

Enables: Search the returned color text in blocks.TableOfContentsBlock.color and attribute each match to its parent block and reported author when available.
Interpretation: Notion supplies color as returned text on each table of contents block; truncation, formatting, and access boundaries can limit completeness.

Table Row

Developer identifier: blocks.table_rowTable Row. Table row block content. Present when type is ‘table_row’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute table row in blocks.table_row to the parent block; identify parent records where that nested table row object is absent.
Interpretation: Notion reports table row as a nested object on each block; optional children may be absent from a valid response.

Cells

Developer identifier: blocks.table_row.cellsCells. Array of cell contents. Each cell is an array of rich text objects. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned cells content in blocks.TableRowBlock.cells while preserving element order and attribution to the parent block.
Interpretation: Notion returns cells as ordered content or provider-generated content metadata on each table row block; truncation, omission, and inaccessible source media can limit completeness.

Items

Developer identifier: blocks.table_row.cells.itemsItems. The structured items details attached to each table row block cell in Blocks. It preserves the nested context needed to interpret the parent block.

Enables: Attribute items in blocks.TableRowBlockCell.items to the parent block; identify parent records where that nested items object is absent.
Interpretation: Notion reports items as a nested object on each table row block cell; optional children may be absent from a valid response.

Template

Developer identifier: blocks.templateTemplate. Template block content. Present when type is ‘template’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute template in blocks.template to the parent block; identify parent records where that nested template object is absent.
Interpretation: Notion reports template as a nested object on each block; optional children may be absent from a valid response.

To Do

Developer identifier: blocks.to_doTo Do. To-do block content. Present when type is ‘to_do’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute to do in blocks.to_do to the parent block; identify parent records where that nested to do object is absent.
Interpretation: Notion reports to do as a nested object on each block; optional children may be absent from a valid response.

Checked

Developer identifier: blocks.to_do.checkedChecked. Whether the to-do item is checked. It distinguishes the provider-defined checked state or classification for the to do block.

Enables: Filter Blocks by whether the to-do item is checked in blocks.ToDoBlock.checked; count true, false, and missing results separately.
Interpretation: Notion reports the to-do item is checked as a boolean on each to do block; a missing field is unknown, not false.

Color

Developer identifier: blocks.to_do.colorColor. Color of the to-do text or background. It supplies the returned color text needed to understand the to do block in context.

Enables: Search the returned color text in blocks.ToDoBlock.color and attribute each match to its parent block and reported author when available.
Interpretation: Notion supplies color as returned text on each to do block; truncation, formatting, and access boundaries can limit completeness.

Rich Text

Developer identifier: blocks.to_do.rich_textRich Text. Array of rich text objects forming the to-do content. It preserves the nested context needed to interpret the parent block.

Enables: Search the returned rich text content in blocks.ToDoBlock.rich_text while preserving element order and attribution to the parent block.
Interpretation: Notion returns rich text as ordered content or provider-generated content metadata on each to do block; truncation, omission, and inaccessible source media can limit completeness.

Toggle

Developer identifier: blocks.toggleToggle. Toggle block content. Present when type is ‘toggle’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute toggle in blocks.toggle to the parent block; identify parent records where that nested toggle object is absent.
Interpretation: Notion reports toggle as a nested object on each block; optional children may be absent from a valid response.

Type

Developer identifier: blocks.typeType. The type of block (paragraph, heading_1, to_do, etc.). It distinguishes the provider-defined type state or classification for the block.

Enables: Segment block entries in Blocks by type in blocks.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each block; preserve unknown labels rather than mapping them by assumption.

URL

Developer identifier: blocks.urlURL. Internal Notion URL for the block, when one is available. It locates the provider resource or path associated with the block.

Enables: Associate each block with the resource identified by URL in blocks.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each block; access still depends on viewer permissions and the URL may expire or change.

Video

Developer identifier: blocks.videoVideo. Video block content. Present when type is ‘video’. It preserves the nested context needed to interpret the parent block.

Enables: Attribute video in blocks.video to the parent block; identify parent records where that nested video object is absent.
Interpretation: Notion reports video as a nested object on each block; optional children may be absent from a valid response.

Comments

Developer identifier: commentsComments. Comments on a page or block.

Enables: Attribute visible comment text to its author, discussion, page or block, and timestamp.
Scope: Reads the records selected by Notion’s /v1/comments operation as a snapshot stream using full synchronization. This stream is opt-in. Only pages and databases explicitly shared with the Notion integration, plus their reachable children, are visible. Comment rich text is included, but referenced file bytes and unshared page content are not. A later complete read can treat a previously seen record that is absent as removed.

Attachments

Developer identifier: comments.attachmentsAttachments. Files attached to the comment (2026 Notion API). It preserves the nested context needed to interpret the parent comment.

Enables: Associate each returned Notion comment attachment metadata entry in comments.attachments with the parent comment; inventory the reference without assuming file, recording, or attachment bytes are present.
Interpretation: Notion returns attachments as file, recording, or attachment metadata on each comment; the array does not imply that binary content was collected. This field is metadata or a reference for the file or attachment; it does not by itself include binary content.

Category

Developer identifier: comments.attachments.categoryCategory. Attachment category, e.g. ‘audio’, ‘image’, ‘pdf’, ‘video’. It identifies the file, document, recording, or attachment metadata associated with the Notion comment attachment.

Enables: Segment Notion comment attachment entries in Comments by category in comments.NotionCommentAttachment.category; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports category as a label from its own taxonomy on each Notion comment attachment; preserve unknown labels rather than mapping them by assumption. This field is metadata or a reference for the file or attachment; it does not by itself include binary content.

File

Developer identifier: comments.attachments.fileFile. The attached Notion-hosted file with a temporary signed URL. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute file in comments.NotionCommentAttachment.file to the parent comment; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each Notion comment attachment; optional children may be absent from a valid response.

Expiry Time

Developer identifier: comments.attachments.file.expiry_timeExpiry Time. ISO 8601 expiration time for the signed URL. It anchors the comment on the provider’s reported timeline.

Enables: Order Comments by expiry time in comments.NotionCommentAttachment.file.expiry_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports expiry time as a timestamp on each file; timezone and precision follow this API field, and absence is not an inferred event time.

URL

Developer identifier: comments.attachments.file.urlURL. Temporary signed URL for the attached file. It locates the provider resource or path associated with the file.

Enables: Associate each file with the resource identified by URL in comments.NotionCommentAttachment.file.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each file; access still depends on viewer permissions and the URL may expire or change.

Created By

Developer identifier: comments.created_byCreated By. The user who created the comment. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute created by in comments.created_by to the parent comment; identify parent records where that nested created by object is absent.
Interpretation: Notion reports created by as a nested object on each comment; optional children may be absent from a valid response.

Developer identifier: comments.created_by.idID. UUID of the user. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Connect each partial user in Comments to the referenced partial user through comments.PartialUser.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its partial user namespace; it is not a universal identity outside Notion.

Object

Developer identifier: comments.created_by.objectObject. Always ‘user’ for user objects. It distinguishes the provider-defined object state or classification for the partial user.

Enables: Filter Comments by the exact Notion-defined object in comments.PartialUser.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each partial user; preserve unknown and newly introduced labels.

Created Time

Developer identifier: comments.created_timeCreated Time. ISO 8601 timestamp of when the comment was created. It anchors the comment on the provider’s reported timeline.

Enables: Order Comments by created time in comments.created_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports created time as a timestamp on each comment; timezone and precision follow this API field, and absence is not an inferred event time.

Discussion ID

Developer identifier: comments.discussion_idDiscussion ID. The discussion thread UUID this comment belongs to. Groups comments into conversation threads. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Connect each comment in Comments to the referenced discussion through comments.discussion_id; flag discussion ID values that do not resolve in that provider namespace.
Interpretation: Notion reports discussion ID as an identifier in its discussion namespace; it is not a universal identity outside Notion.

Display Name

Developer identifier: comments.display_nameDisplay Name. Display name of the comment author, present for comments authored via public API integrations (2026 Notion API). It preserves the nested context needed to interpret the parent comment.

Enables: Attribute display name in comments.display_name to the parent comment; identify parent records where that nested display name object is absent.
Interpretation: Notion reports display name as a nested object on each comment; optional children may be absent from a valid response.

Custom

Developer identifier: comments.display_name.customCustom. Custom display name payload, present when type is ‘custom’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute custom in comments.display_name.custom to the parent comment; identify parent records where that nested custom object is absent.
Interpretation: Notion reports custom as a nested object on each display name; optional children may be absent from a valid response.

Resolved Name

Developer identifier: comments.display_name.resolved_nameResolved Name. The resolved display name text. It supplies the returned resolved name text needed to understand the display name in context.

Enables: Label each display name with resolved name from comments.display_name.resolved_name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports resolved name as display text for each display name; names are mutable and are not stable identities.

Type

Developer identifier: comments.display_name.typeType. Source of the display name: ‘user’, ‘integration’, or ‘custom’. It distinguishes the provider-defined type state or classification for the display name.

Enables: Segment display name entries in Comments by type in comments.display_name.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each display name; preserve unknown labels rather than mapping them by assumption.

Developer identifier: comments.idID. Unique identifier (UUID) for the comment. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Match repeated comment entries on ID in comments.id; collapse only entries that share this declared transform key.
Interpretation: Notion reports ID as an identifier in its comment namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key.

Last Edited Time

Developer identifier: comments.last_edited_timeLast Edited Time. ISO 8601 timestamp of when the comment was last edited. It anchors the comment on the provider’s reported timeline.

Enables: Order Comments by last edited time in comments.last_edited_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports last edited time as a timestamp on each comment; timezone and precision follow this API field, and absence is not an inferred event time. A connector directive uses this field to order records for latest-state or incremental processing.

Object

Developer identifier: comments.objectObject. Always ‘comment’ for comment objects. It supplies the returned object text needed to understand the comment in context.

Enables: Search the returned object text in comments.object and attribute each match to its parent comment and reported author when available.
Interpretation: Notion supplies object as returned text on each comment; truncation, formatting, and access boundaries can limit completeness.

Page ID

Developer identifier: comments.page_idPage ID. Parent page reference copied into each comment because the child operation does not return that relationship. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Connect each comment in Comments to the referenced page through comments.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Parable copies page ID from the parent traversal record into each comment; the child Notion operation does not return it.

Parent

Developer identifier: comments.parentParent. Parent reference indicating which page or block the comment is attached to. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute parent in comments.parent to the parent comment; identify parent records where that nested parent object is absent.
Interpretation: Notion reports parent as a nested object on each comment; optional children may be absent from a valid response.

Block ID

Developer identifier: comments.parent.block_idBlock ID. The UUID of the parent block, present when type is ‘block_id’. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Connect each comment parent in Comments to the referenced block through comments.CommentParent.block_id; flag block ID values that do not resolve in that provider namespace.
Interpretation: Notion reports block ID as an identifier in its block namespace; it is not a universal identity outside Notion.

Page ID

Developer identifier: comments.parent.page_idPage ID. The UUID of the parent page, present when type is ‘page_id’. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Connect each comment parent in Comments to the referenced page through comments.CommentParent.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Notion reports page ID as an identifier in its page namespace; it is not a universal identity outside Notion.

Type

Developer identifier: comments.parent.typeType. The type of parent: ‘page_id’ or ‘block_id’. It distinguishes the provider-defined type state or classification for the comment parent.

Enables: Segment comment parent entries in Comments by type in comments.CommentParent.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each comment parent; preserve unknown labels rather than mapping them by assumption.

Rich Text

Developer identifier: comments.rich_textRich Text. The comment content as an array of rich text objects. It preserves the nested context needed to interpret the parent comment.

Enables: Search the returned rich text content in comments.rich_text while preserving element order and attribution to the parent comment.
Interpretation: Notion returns rich text as ordered content or provider-generated content metadata on each comment; truncation, omission, and inaccessible source media can limit completeness.

Annotations

Developer identifier: comments.rich_text.annotationsAnnotations. Style annotations applied to this rich text segment. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute annotations in comments.RichText.annotations to the parent comment; identify parent records where that nested annotations object is absent.
Interpretation: Notion reports annotations as a nested object on each rich text; optional children may be absent from a valid response.

Bold

Developer identifier: comments.rich_text.annotations.boldBold. Whether the text is bold. It distinguishes the provider-defined bold state or classification for the rich text annotation.

Enables: Filter Comments by whether the text is bold in comments.RichTextAnnotations.bold; count true, false, and missing results separately.
Interpretation: Notion reports the text is bold as a boolean on each rich text annotation; a missing field is unknown, not false.

Code

Developer identifier: comments.rich_text.annotations.codeCode. Whether the text is displayed as inline code. It distinguishes the provider-defined code state or classification for the rich text annotation.

Enables: Filter Comments by whether the text is displayed as inline code in comments.RichTextAnnotations.code; count true, false, and missing results separately.
Interpretation: Notion reports the text is displayed as inline code as a boolean on each rich text annotation; a missing field is unknown, not false.

Color

Developer identifier: comments.rich_text.annotations.colorColor. The color of the text or its background. It distinguishes the provider-defined color state or classification for the rich text annotation.

Enables: Segment rich text annotation entries in Comments by color in comments.RichTextAnnotations.color; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports color as a label from its own taxonomy on each rich text annotation; preserve unknown labels rather than mapping them by assumption.

Italic

Developer identifier: comments.rich_text.annotations.italicItalic. Whether the text is italic. It distinguishes the provider-defined italic state or classification for the rich text annotation.

Enables: Filter Comments by whether the text is italic in comments.RichTextAnnotations.italic; count true, false, and missing results separately.
Interpretation: Notion reports the text is italic as a boolean on each rich text annotation; a missing field is unknown, not false.

Strikethrough

Developer identifier: comments.rich_text.annotations.strikethroughStrikethrough. Whether the text has strikethrough. It distinguishes the provider-defined strikethrough state or classification for the rich text annotation.

Enables: Filter Comments by whether the text has strikethrough in comments.RichTextAnnotations.strikethrough; count true, false, and missing results separately.
Interpretation: Notion reports the text has strikethrough as a boolean on each rich text annotation; a missing field is unknown, not false.

Underline

Developer identifier: comments.rich_text.annotations.underlineUnderline. Whether the text is underlined. It distinguishes the provider-defined underline state or classification for the rich text annotation.

Enables: Filter Comments by whether the text is underlined in comments.RichTextAnnotations.underline; count true, false, and missing results separately.
Interpretation: Notion reports the text is underlined as a boolean on each rich text annotation; a missing field is unknown, not false.

Equation

Developer identifier: comments.rich_text.equationEquation. Equation data. Present when type is ‘equation’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute equation in comments.RichText.equation to the parent comment; identify parent records where that nested equation object is absent.
Interpretation: Notion reports equation as a nested object on each rich text; optional children may be absent from a valid response.

Expression

Developer identifier: comments.rich_text.equation.expressionExpression. The LaTeX/KaTeX expression string. It must be interpreted with the enclosing provider field name, type, or custom schema for the rich text equation.

Enables: Interpret comments.RichTextEquation.expression with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: Notion reports expression under the enclosing custom or typed field contract on each rich text equation; compare it only with values from the same provider key and type.

Href

Developer identifier: comments.rich_text.hrefHref. URL of any inline link in this rich text segment, if present. It locates the provider resource or path associated with the rich text.

Enables: Associate each rich text with the resource identified by href in comments.RichText.href; verify the link resolves to the expected Notion object.
Interpretation: Notion reports href as a resource locator for each rich text; access still depends on viewer permissions and the URL may expire or change.

Mention

Developer identifier: comments.rich_text.mentionMention. Mention data. Present when type is ‘mention’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute mention in comments.RichText.mention to the parent comment; identify parent records where that nested mention object is absent.
Interpretation: Notion reports mention as a nested object on each rich text; optional children may be absent from a valid response.

Database

Developer identifier: comments.rich_text.mention.databaseDatabase. Mentioned database. Present when type is ‘database’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute database in comments.RichTextMention.database to the parent comment; identify parent records where that nested database object is absent.
Interpretation: Notion reports database as a nested object on each rich text mention; optional children may be absent from a valid response.

Developer identifier: comments.rich_text.mention.database.idID. UUID of the referenced page or database. It provides the reference needed to connect the comment to the corresponding provider object.

Enables: Connect each mention reference in Comments to the referenced mention reference through comments.MentionReference.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its mention reference namespace; it is not a universal identity outside Notion.

Date

Developer identifier: comments.rich_text.mention.dateDate. Date mention. Present when type is ‘date’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute date in comments.RichTextMention.date to the parent comment; identify parent records where that nested date object is absent.
Interpretation: Notion reports date as a nested object on each rich text mention; optional children may be absent from a valid response.

End

Developer identifier: comments.rich_text.mention.date.endEnd. End date or datetime in ISO 8601 format, null for single dates. It anchors the comment on the provider’s reported timeline.

Enables: Filter Comments by end in comments.MentionDate.end; pair that boundary with the corresponding start before measuring elapsed time.
Interpretation: Notion reports end as a timestamp on each mention date; timezone and precision follow this API field, and absence is not an inferred event time.

Start

Developer identifier: comments.rich_text.mention.date.startStart. Start date or datetime in ISO 8601 format. It anchors the comment on the provider’s reported timeline.

Enables: Filter Comments by start in comments.MentionDate.start; pair that boundary with the corresponding end before measuring elapsed time.
Interpretation: Notion reports start as a timestamp on each mention date; timezone and precision follow this API field, and absence is not an inferred event time.

Time Zone

Developer identifier: comments.rich_text.mention.date.time_zoneTime Zone. IANA time zone, if applicable. It is needed to interpret companion dates and times for the mention date in the provider’s intended zone.

Enables: Apply the zone in comments.MentionDate.time_zone when converting the comment’s companion start, end, or scheduled timestamps; do not infer it from locale.
Interpretation: Notion reports time zone as a timezone identifier for each mention date; supported IANA or provider-specific names and daylight-saving behavior must be preserved.

Link Preview

Developer identifier: comments.rich_text.mention.link_previewLink Preview. Link preview mention. Present when type is ‘link_preview’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute link preview in comments.RichTextMention.link_preview to the parent comment; identify parent records where that nested link preview object is absent.
Interpretation: Notion reports link preview as a nested object on each rich text mention; optional children may be absent from a valid response.

URL

Developer identifier: comments.rich_text.mention.link_preview.urlURL. The URL being previewed. It locates the provider resource or path associated with the mention link preview.

Enables: Associate each mention link preview with the resource identified by URL in comments.MentionLinkPreview.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each mention link preview; access still depends on viewer permissions and the URL may expire or change.

Page

Developer identifier: comments.rich_text.mention.pagePage. Mentioned page. Present when type is ‘page’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute page in comments.RichTextMention.page to the parent comment; identify parent records where that nested page object is absent.
Interpretation: Notion reports page as a nested object on each rich text mention; optional children may be absent from a valid response.

Type

Developer identifier: comments.rich_text.mention.typeType. The type of mention. It distinguishes the provider-defined type state or classification for the rich text mention.

Enables: Segment rich text mention entries in Comments by type in comments.RichTextMention.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each rich text mention; preserve unknown labels rather than mapping them by assumption.

User

Developer identifier: comments.rich_text.mention.userUser. Mentioned user. Present when type is ‘user’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute user in comments.RichTextMention.user to the parent comment; identify parent records where that nested user object is absent.
Interpretation: Notion reports user as a nested object on each rich text mention; optional children may be absent from a valid response.

Plain Text

Developer identifier: comments.rich_text.plain_textPlain Text. Plain text representation of this rich text segment without formatting. It defines the content surface available for this comment.

Enables: Locate rich text records by plain text in comments.RichText.plain_text; attribute each text match to its parent comment and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Text

Developer identifier: comments.rich_text.textText. Text content and optional link. Present when type is ‘text’. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute text in comments.RichText.text to the parent comment; identify parent records where that nested text object is absent.
Interpretation: Notion reports text as a nested object on each rich text; optional children may be absent from a valid response.

Content

Developer identifier: comments.rich_text.text.contentContent. The actual text content. It defines the content surface available for this comment.

Enables: Locate rich text text records by content in comments.RichTextText.content; attribute each text match to its parent comment and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Link

Developer identifier: comments.rich_text.text.linkLink. Optional inline link object. It preserves the nested context needed to interpret the parent comment.

Enables: Attribute link in comments.RichTextText.link to the parent comment; identify parent records where that nested link object is absent.
Interpretation: Notion reports link as a nested object on each rich text text; optional children may be absent from a valid response.

URL

Developer identifier: comments.rich_text.text.link.urlURL. The URL the text links to. It locates the provider resource or path associated with the rich text link.

Enables: Associate each rich text link with the resource identified by URL in comments.RichTextLink.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each rich text link; access still depends on viewer permissions and the URL may expire or change.

Type

Developer identifier: comments.rich_text.typeType. The type of rich text: text, mention, or equation. It distinguishes the provider-defined type state or classification for the rich text.

Enables: Segment rich text entries in Comments by type in comments.RichText.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each rich text; preserve unknown labels rather than mapping them by assumption.

Database Items

Developer identifier: database_itemsDatabase Items. Items (pages) within a data source.

Enables: Match each data-source page to its parent data source and compare provider-defined property values and lifecycle timestamps.
Scope: Reads the records selected by Notion’s /v1/data_sources/{id}/query operation as a snapshot stream using incremental synchronization. This stream is opt-in. Only pages and databases explicitly shared with the Notion integration, plus their reachable children, are visible. The stream does not include records the credential, parent traversal, configured filters, or provider API omits. Removal is recognized from the provider’s tombstone state rather than absence alone.

Archived

Developer identifier: database_items.archivedArchived. Whether the item is archived (completed or removed). It distinguishes the provider-defined archived state or classification for the database item.

Enables: Filter Database Items by whether the item is archived (completed or removed) in database_items.archived; count true, false, and missing results separately.
Interpretation: Notion reports the item is archived (completed or removed) as a boolean on each database item; a missing field is unknown, not false.

Cover

Developer identifier: database_items.coverCover. Cover image for the page, or null if none. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute cover in database_items.cover to the parent database item; identify parent records where that nested cover object is absent.
Interpretation: Notion reports cover as a nested object on each database item; optional children may be absent from a valid response.

External

Developer identifier: database_items.cover.externalExternal. External file details, present when type is ‘external’. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute external in database_items.FileObject.external to the parent database item; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each file object; optional children may be absent from a valid response. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: database_items.cover.external.urlURL. URL of the external file. It locates the provider resource or path associated with the external file.

Enables: Associate each external file with the resource identified by URL in database_items.ExternalFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each external file; access still depends on viewer permissions and the URL may expire or change.

File

Developer identifier: database_items.cover.fileFile. Notion-hosted file details, present when type is ‘file’. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute file in database_items.FileObject.file to the parent database item; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each file object; optional children may be absent from a valid response. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Expiry Time

Developer identifier: database_items.cover.file.expiry_timeExpiry Time. ISO 8601 expiration time for the signed URL. It anchors the database item on the provider’s reported timeline.

Enables: Order Database Items by expiry time in database_items.NotionHostedFile.expiry_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports expiry time as a timestamp on each Notion hosted file; timezone and precision follow this API field, and absence is not an inferred event time. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: database_items.cover.file.urlURL. Temporary signed URL for the Notion-hosted file. It locates the provider resource or path associated with the Notion hosted file.

Enables: Associate each Notion hosted file with the resource identified by URL in database_items.NotionHostedFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion hosted file; access still depends on viewer permissions and the URL may expire or change. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Type

Developer identifier: database_items.cover.typeType. The type of file: ‘external’ or ‘file’ (Notion-hosted). It distinguishes the provider-defined type state or classification for the file object.

Enables: Segment file object entries in Database Items by type in database_items.FileObject.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each file object; preserve unknown labels rather than mapping them by assumption. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Created By

Developer identifier: database_items.created_byCreated By. User who created the item. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute created by in database_items.created_by to the parent database item; identify parent records where that nested created by object is absent.
Interpretation: Notion reports created by as a nested object on each database item; optional children may be absent from a valid response.

Developer identifier: database_items.created_by.idID. UUID of the user. It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each partial user in Database Items to the referenced partial user through database_items.PartialUser.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its partial user namespace; it is not a universal identity outside Notion.

Object

Developer identifier: database_items.created_by.objectObject. Always ‘user’ for user objects. It distinguishes the provider-defined object state or classification for the partial user.

Enables: Filter Database Items by the exact Notion-defined object in database_items.PartialUser.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each partial user; preserve unknown and newly introduced labels.

Created Time

Developer identifier: database_items.created_timeCreated Time. ISO 8601 timestamp when the item was created. It anchors the database item on the provider’s reported timeline.

Enables: Order Database Items by created time in database_items.created_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports created time as a timestamp on each database item; timezone and precision follow this API field, and absence is not an inferred event time.

Data Source ID

Developer identifier: database_items.data_source_idData Source ID. Parent data source reference copied into each database item because the child operation does not return that relationship. It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each database item in Database Items to the referenced data source through database_items.data_source_id; flag data source ID values that do not resolve in that provider namespace.
Interpretation: Parable copies data source ID from the parent traversal record into each database item; the child Notion operation does not return it.

Icon

Developer identifier: database_items.iconIcon. Icon for the page (emoji or file), or null if none. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute icon in database_items.icon to the parent database item; identify parent records where that nested icon object is absent.
Interpretation: Notion reports icon as a nested object on each database item; optional children may be absent from a valid response.

Emoji

Developer identifier: database_items.icon.emojiEmoji. Emoji character, present when type is ‘emoji’. It distinguishes the provider-defined emoji state or classification for the icon object.

Enables: Filter Database Items by the exact Notion-defined emoji in database_items.IconObject.emoji and preserve unknown values as distinct categories.
Interpretation: Notion supplies emoji from its own taxonomy on each icon object; preserve unknown and newly introduced labels.

External

Developer identifier: database_items.icon.externalExternal. External file details, present when type is ‘external’. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute external in database_items.IconObject.external to the parent database item; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each icon object; optional children may be absent from a valid response.

File

Developer identifier: database_items.icon.fileFile. Notion-hosted file details, present when type is ‘file’. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute file in database_items.IconObject.file to the parent database item; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each icon object; optional children may be absent from a valid response.

Type

Developer identifier: database_items.icon.typeType. The type of icon: ‘emoji’, ‘external’, or ‘file’. It distinguishes the provider-defined type state or classification for the icon object.

Enables: Segment icon object entries in Database Items by type in database_items.IconObject.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each icon object; preserve unknown labels rather than mapping them by assumption.

Developer identifier: database_items.idID. Unique identifier for the database item (page). It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Match repeated database item entries on ID in database_items.id; collapse only entries that share this declared transform key.
Interpretation: Notion reports ID as an identifier in its database item namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key.

In Trash

Developer identifier: database_items.in_trashIn Trash. Whether the item is in the trash. It distinguishes the provider-defined in trash state or classification for the database item.

Enables: Filter Database Items by whether the item is in the trash in database_items.in_trash; count true, false, and missing results separately.
Interpretation: Notion reports the item is in the trash as a boolean on each database item; a missing field is unknown, not false.

Last Edited By

Developer identifier: database_items.last_edited_byLast Edited By. User who last edited the item. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute last edited by in database_items.last_edited_by to the parent database item; identify parent records where that nested last edited by object is absent.
Interpretation: Notion reports last edited by as a nested object on each database item; optional children may be absent from a valid response.

Last Edited Time

Developer identifier: database_items.last_edited_timeLast Edited Time. ISO 8601 timestamp when the item was last modified. Used as incremental sync cursor. It anchors the database item on the provider’s reported timeline.

Enables: Order Database Items by last edited time in database_items.last_edited_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports last edited time as a timestamp on each database item; timezone and precision follow this API field, and absence is not an inferred event time. A connector directive uses this field to order records for latest-state or incremental processing.

Object

Developer identifier: database_items.objectObject. Always ‘page’ for database items. It distinguishes the provider-defined object state or classification for the database item.

Enables: Filter Database Items by the exact Notion-defined object in database_items.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each database item; preserve unknown and newly introduced labels.

Parent

Developer identifier: database_items.parentParent. Parent reference linking items back to their data source or database container. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute parent in database_items.parent to the parent database item; identify parent records where that nested parent object is absent.
Interpretation: Notion reports parent as a nested object on each database item; optional children may be absent from a valid response.

Block ID

Developer identifier: database_items.parent.block_idBlock ID. UUID of the parent block, present when type is ‘block_id’. It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each parent in Database Items to the referenced block through database_items.Parent.block_id; flag block ID values that do not resolve in that provider namespace.
Interpretation: Notion reports block ID as an identifier in its block namespace; it is not a universal identity outside Notion.

Data Source ID

Developer identifier: database_items.parent.data_source_idData Source ID. UUID of the parent data source, present when type is ‘data_source_id’ (2026 Notion API). It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each parent in Database Items to the referenced data source through database_items.Parent.data_source_id; flag data source ID values that do not resolve in that provider namespace.
Interpretation: Notion reports data source ID as an identifier in its data source namespace; it is not a universal identity outside Notion.

Database ID

Developer identifier: database_items.parent.database_idDatabase ID. UUID of the parent database, present when type is ‘database_id’. It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each parent in Database Items to the referenced database through database_items.Parent.database_id; flag database ID values that do not resolve in that provider namespace.
Interpretation: Notion reports database ID as an identifier in its database namespace; it is not a universal identity outside Notion.

Page ID

Developer identifier: database_items.parent.page_idPage ID. UUID of the parent page, present when type is ‘page_id’. It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each parent in Database Items to the referenced page through database_items.Parent.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Notion reports page ID as an identifier in its page namespace; it is not a universal identity outside Notion.

Type

Developer identifier: database_items.parent.typeType. The type of parent: database_id, page_id, workspace, or block_id. It distinguishes the provider-defined type state or classification for the parent.

Enables: Segment parent entries in Database Items by type in database_items.Parent.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each parent; preserve unknown labels rather than mapping them by assumption.

Workspace

Developer identifier: database_items.parent.workspaceWorkspace. True when the parent is the workspace (type is ‘workspace’). It distinguishes the provider-defined workspace state or classification for the parent.

Enables: Filter Database Items by whether true when the parent is the workspace (type is ‘workspace’) in database_items.Parent.workspace; count true, false, and missing results separately.
Interpretation: Notion reports true when the parent is the workspace (type is ‘workspace’) as a boolean on each parent; a missing field is unknown, not false.

Properties

Developer identifier: database_items.propertiesProperties. All property values for this item. Keys are property names, values are property value objects. Structure is dynamic based on database schema and includes types like title, rich_text, number, select, multi_select, status, date, people, checkbox, URL, email, phone_number, formula, relation, rollup, created_time, created_by, last_edited_time, last_edited_by, unique_id, verification, and files. It preserves the nested context needed to interpret the parent database item.

Enables: Attribute properties in database_items.properties to the parent database item; identify parent records where that nested properties object is absent.
Interpretation: Notion reports properties as a nested object on each database item; optional children may be absent from a valid response.

Public URL

Developer identifier: database_items.public_urlPublic URL. Public URL if the page is published to the web, or null. It locates the provider resource or path associated with the database item.

Enables: Associate each database item with the resource identified by public URL in database_items.public_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports public URL as a resource locator for each database item; access still depends on viewer permissions and the URL may expire or change.

Request ID

Developer identifier: database_items.request_idRequest ID. Unique ID for the API request that returned this object. It provides the reference needed to connect the database item to the corresponding provider object.

Enables: Connect each database item in Database Items to the referenced request through database_items.request_id; flag request ID values that do not resolve in that provider namespace.
Interpretation: Notion reports request ID as an identifier in its request namespace; it is not a universal identity outside Notion.

URL

Developer identifier: database_items.urlURL. URL to the item in Notion for deep linking. It locates the provider resource or path associated with the database item.

Enables: Associate each database item with the resource identified by URL in database_items.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each database item; access still depends on viewer permissions and the URL may expire or change.

Databases

Developer identifier: databasesDatabases. Databases in the workspace.

Enables: Inventory databases returned by search and connect each one to its parent, title, properties, owners, and data-source references.
Scope: Reads the records selected by Notion’s /v1/search operation as a snapshot stream using incremental synchronization. Only pages and databases explicitly shared with the Notion integration, plus their reachable children, are visible. The stream does not include records the credential, parent traversal, configured filters, or provider API omits. Removal is recognized from the provider’s tombstone state rather than absence alone.

Archived

Developer identifier: databases.archivedArchived. Whether the database is archived (soft-deleted). It distinguishes the provider-defined archived state or classification for the database.

Enables: Filter Databases by whether the database is archived (soft-deleted) in databases.archived; count true, false, and missing results separately.
Interpretation: Notion reports the database is archived (soft-deleted) as a boolean on each database; a missing field is unknown, not false.

Cover

Developer identifier: databases.coverCover. Cover image of the database, if set. It preserves the nested context needed to interpret the parent database.

Enables: Attribute cover in databases.cover to the parent database; identify parent records where that nested cover object is absent.
Interpretation: Notion reports cover as a nested object on each database; optional children may be absent from a valid response.

External

Developer identifier: databases.cover.externalExternal. The structured external details attached to each Notion file in Databases. It preserves the nested context needed to interpret the parent database.

Enables: Attribute external in databases.NotionFile.external to the parent database; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each Notion file; optional children may be absent from a valid response. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: databases.cover.external.urlURL. The provider-reported URL for each Notion external file in Databases. It locates the provider resource or path associated with the Notion external file.

Enables: Associate each Notion external file with the resource identified by URL in databases.NotionExternalFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion external file; access still depends on viewer permissions and the URL may expire or change. This stream treats the file or attachment as metadata and references; binary bytes are not included.

File

Developer identifier: databases.cover.fileFile. The structured file details attached to each Notion file in Databases. It preserves the nested context needed to interpret the parent database.

Enables: Attribute file in databases.NotionFile.file to the parent database; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each Notion file; optional children may be absent from a valid response. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Expiry Time

Developer identifier: databases.cover.file.expiry_timeExpiry Time. The provider-reported expiry time for each Notion hosted file in Databases. It anchors the database on the provider’s reported timeline.

Enables: Order Databases by expiry time in databases.NotionHostedFile.expiry_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports expiry time as a timestamp on each Notion hosted file; timezone and precision follow this API field, and absence is not an inferred event time. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: databases.cover.file.urlURL. The provider-reported URL for each Notion hosted file in Databases. It locates the provider resource or path associated with the Notion hosted file.

Enables: Associate each Notion hosted file with the resource identified by URL in databases.NotionHostedFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion hosted file; access still depends on viewer permissions and the URL may expire or change. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Type

Developer identifier: databases.cover.typeType. The provider-reported type for each Notion file in Databases. It distinguishes the provider-defined type state or classification for the Notion file.

Enables: Segment Notion file entries in Databases by type in databases.NotionFile.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion file; preserve unknown labels rather than mapping them by assumption. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Created By

Developer identifier: databases.created_byCreated By. User who created the database. It preserves the nested context needed to interpret the parent database.

Enables: Attribute created by in databases.created_by to the parent database; identify parent records where that nested created by object is absent.
Interpretation: Notion reports created by as a nested object on each database; optional children may be absent from a valid response.

Developer identifier: databases.created_by.idID. User ID (UUID). It provides the reference needed to connect the database to the corresponding provider object.

Enables: Connect each Notion partial user in Databases to the referenced Notion partial user through databases.NotionPartialUser.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its Notion partial user namespace; it is not a universal identity outside Notion.

Object

Developer identifier: databases.created_by.objectObject. Always ‘user’. It distinguishes the provider-defined object state or classification for the Notion partial user.

Enables: Filter Databases by the exact Notion-defined object in databases.NotionPartialUser.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each Notion partial user; preserve unknown and newly introduced labels.

Created Time

Developer identifier: databases.created_timeCreated Time. ISO 8601 timestamp when the database was created. It anchors the database on the provider’s reported timeline.

Enables: Order Databases by created time in databases.created_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports created time as a timestamp on each database; timezone and precision follow this API field, and absence is not an inferred event time.

Data Sources

Developer identifier: databases.data_sourcesData Sources. Array of data source references associated with this database (API version 2025-09-03+). It preserves the nested context needed to interpret the parent database.

Enables: Attribute every returned Notion data source reference in databases.data_sources to its parent database; keep each relationship distinct and distinguish an absent array from an explicitly empty one.
Interpretation: Notion returns data sources as an array of Notion data source reference entries on each database; missing, empty, and permission-redacted arrays are not equivalent.

Data Source ID

Developer identifier: databases.data_sources.data_source_idData Source ID. The provider-reported data source ID for each Notion data source reference in Databases. It provides the reference needed to connect the database to the corresponding provider object.

Enables: Match repeated Notion data source reference entries on data source ID in databases.NotionDataSourceReference.data_source_id; collapse only entries that share this declared transform key.
Interpretation: Notion reports data source ID as an identifier in its data source namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key.

Type

Developer identifier: databases.data_sources.typeType. The provider-reported type for each Notion data source reference in Databases. It identifies the related provider object that gives the Notion data source reference its parent, owner, or container context.

Enables: Segment Notion data source reference entries in Databases by type in databases.NotionDataSourceReference.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion data source reference; preserve unknown labels rather than mapping them by assumption.

Database Parent

Developer identifier: databases.database_parentDatabase Parent. Grandparent of the data source (the database container’s parent), present on data source search results under API 2025-09-03+. It preserves the nested context needed to interpret the parent database.

Enables: Attribute database parent in databases.database_parent to the parent database; identify parent records where that nested database parent object is absent.
Interpretation: Notion reports database parent as a nested object on each database; optional children may be absent from a valid response.

Block ID

Developer identifier: databases.database_parent.block_idBlock ID. The provider-reported block ID for each Notion parent in Databases. It provides the reference needed to connect the database to the corresponding provider object.

Enables: Connect each Notion parent in Databases to the referenced block through databases.NotionParent.block_id; flag block ID values that do not resolve in that provider namespace.
Interpretation: Notion reports block ID as an identifier in its block namespace; it is not a universal identity outside Notion.

Page ID

Developer identifier: databases.database_parent.page_idPage ID. The provider-reported page ID for each Notion parent in Databases. It provides the reference needed to connect the database to the corresponding provider object.

Enables: Connect each Notion parent in Databases to the referenced page through databases.NotionParent.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Notion reports page ID as an identifier in its page namespace; it is not a universal identity outside Notion.

Type

Developer identifier: databases.database_parent.typeType. Type of parent. It identifies the related provider object that gives the Notion parent its parent, owner, or container context.

Enables: Segment Notion parent entries in Databases by type in databases.NotionParent.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion parent; preserve unknown labels rather than mapping them by assumption.

Workspace

Developer identifier: databases.database_parent.workspaceWorkspace. The provider-reported workspace for each Notion parent in Databases. It distinguishes the provider-defined workspace state or classification for the Notion parent.

Enables: Filter Databases by whether workspace in databases.NotionParent.workspace; count true, false, and missing results separately.
Interpretation: Notion reports workspace as a boolean on each Notion parent; a missing field is unknown, not false.

Description

Developer identifier: databases.descriptionDescription. Description of the database as an array of rich text objects. It preserves the nested context needed to interpret the parent database.

Enables: Search the returned description content in databases.description while preserving element order and attribution to the parent database.
Interpretation: Notion returns description as ordered content or provider-generated content metadata on each database; truncation, omission, and inaccessible source media can limit completeness.

Annotations

Developer identifier: databases.description.annotationsAnnotations. Styling annotations. It preserves the nested context needed to interpret the parent database.

Enables: Attribute annotations in databases.NotionRichText.annotations to the parent database; identify parent records where that nested annotations object is absent.
Interpretation: Notion reports annotations as a nested object on each Notion rich text; optional children may be absent from a valid response.

Bold

Developer identifier: databases.description.annotations.boldBold. The provider-reported bold for each Notion annotations in Databases. It distinguishes the provider-defined bold state or classification for the Notion annotation.

Enables: Filter Databases by whether bold in databases.NotionAnnotations.bold; count true, false, and missing results separately.
Interpretation: Notion reports bold as a boolean on each Notion annotation; a missing field is unknown, not false.

Code

Developer identifier: databases.description.annotations.codeCode. The provider-reported code for each Notion annotations in Databases. It distinguishes the provider-defined code state or classification for the Notion annotation.

Enables: Filter Databases by whether code in databases.NotionAnnotations.code; count true, false, and missing results separately.
Interpretation: Notion reports code as a boolean on each Notion annotation; a missing field is unknown, not false.

Color

Developer identifier: databases.description.annotations.colorColor. The provider-reported color for each Notion annotations in Databases. It distinguishes the provider-defined color state or classification for the Notion annotation.

Enables: Filter Databases by the exact Notion-defined color in databases.NotionAnnotations.color and preserve unknown values as distinct categories.
Interpretation: Notion supplies color from its own taxonomy on each Notion annotation; preserve unknown and newly introduced labels.

Italic

Developer identifier: databases.description.annotations.italicItalic. The provider-reported italic for each Notion annotations in Databases. It distinguishes the provider-defined italic state or classification for the Notion annotation.

Enables: Filter Databases by whether italic in databases.NotionAnnotations.italic; count true, false, and missing results separately.
Interpretation: Notion reports italic as a boolean on each Notion annotation; a missing field is unknown, not false.

Strikethrough

Developer identifier: databases.description.annotations.strikethroughStrikethrough. The provider-reported strikethrough for each Notion annotations in Databases. It distinguishes the provider-defined strikethrough state or classification for the Notion annotation.

Enables: Filter Databases by whether strikethrough in databases.NotionAnnotations.strikethrough; count true, false, and missing results separately.
Interpretation: Notion reports strikethrough as a boolean on each Notion annotation; a missing field is unknown, not false.

Underline

Developer identifier: databases.description.annotations.underlineUnderline. The provider-reported underline for each Notion annotations in Databases. It distinguishes the provider-defined underline state or classification for the Notion annotation.

Enables: Filter Databases by whether underline in databases.NotionAnnotations.underline; count true, false, and missing results separately.
Interpretation: Notion reports underline as a boolean on each Notion annotation; a missing field is unknown, not false.

Href

Developer identifier: databases.description.hrefHref. URL of any link. It locates the provider resource or path associated with the Notion rich text.

Enables: Associate each Notion rich text with the resource identified by href in databases.NotionRichText.href; verify the link resolves to the expected Notion object.
Interpretation: Notion reports href as a resource locator for each Notion rich text; access still depends on viewer permissions and the URL may expire or change.

Plain Text

Developer identifier: databases.description.plain_textPlain Text. Plain text content without annotations. It defines the content surface available for this database.

Enables: Locate Notion rich text records by plain text in databases.NotionRichText.plain_text; attribute each text match to its parent database and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Type

Developer identifier: databases.description.typeType. Type of rich text: ‘text’, ‘mention’, ‘equation’. It supplies the returned type text needed to understand the Notion rich text in context.

Enables: Segment Notion rich text entries in Databases by type in databases.NotionRichText.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion rich text; preserve unknown labels rather than mapping them by assumption.

Icon

Developer identifier: databases.iconIcon. Icon of the database (emoji or file). It preserves the nested context needed to interpret the parent database.

Enables: Attribute icon in databases.icon to the parent database; identify parent records where that nested icon object is absent.
Interpretation: Notion reports icon as a nested object on each database; optional children may be absent from a valid response.

Emoji

Developer identifier: databases.icon.emojiEmoji. The provider-reported emoji for each Notion icon in Databases. It distinguishes the provider-defined emoji state or classification for the Notion icon.

Enables: Filter Databases by the exact Notion-defined emoji in databases.NotionIcon.emoji and preserve unknown values as distinct categories.
Interpretation: Notion supplies emoji from its own taxonomy on each Notion icon; preserve unknown and newly introduced labels.

External

Developer identifier: databases.icon.externalExternal. The structured external details attached to each Notion icon in Databases. It preserves the nested context needed to interpret the parent database.

Enables: Attribute external in databases.NotionIcon.external to the parent database; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each Notion icon; optional children may be absent from a valid response.

File

Developer identifier: databases.icon.fileFile. The structured file details attached to each Notion icon in Databases. It preserves the nested context needed to interpret the parent database.

Enables: Attribute file in databases.NotionIcon.file to the parent database; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each Notion icon; optional children may be absent from a valid response.

Type

Developer identifier: databases.icon.typeType. The provider-reported type for each Notion icon in Databases. It distinguishes the provider-defined type state or classification for the Notion icon.

Enables: Segment Notion icon entries in Databases by type in databases.NotionIcon.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion icon; preserve unknown labels rather than mapping them by assumption.

Developer identifier: databases.idID. Unique identifier for the data source (UUID format with hyphens). It provides the reference needed to connect the database to the corresponding provider object.

Enables: Match repeated database entries on ID in databases.id; collapse only entries that share this declared transform key.
Interpretation: Notion reports ID as an identifier in its database namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key.

In Trash

Developer identifier: databases.in_trashIn Trash. Whether the database is in the trash. It distinguishes the provider-defined in trash state or classification for the database.

Enables: Filter Databases by whether the database is in the trash in databases.in_trash; count true, false, and missing results separately.
Interpretation: Notion reports the database is in the trash as a boolean on each database; a missing field is unknown, not false.

Is Inline

Developer identifier: databases.is_inlineIs Inline. Whether the database is an inline database. It distinguishes the provider-defined is inline state or classification for the database.

Enables: Filter Databases by whether the database is an inline database in databases.is_inline; count true, false, and missing results separately.
Interpretation: Notion reports the database is an inline database as a boolean on each database; a missing field is unknown, not false.

Last Edited By

Developer identifier: databases.last_edited_byLast Edited By. User who last edited the database. It preserves the nested context needed to interpret the parent database.

Enables: Attribute last edited by in databases.last_edited_by to the parent database; identify parent records where that nested last edited by object is absent.
Interpretation: Notion reports last edited by as a nested object on each database; optional children may be absent from a valid response.

Last Edited Time

Developer identifier: databases.last_edited_timeLast Edited Time. ISO 8601 timestamp when the database was last edited. It anchors the database on the provider’s reported timeline.

Enables: Order Databases by last edited time in databases.last_edited_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports last edited time as a timestamp on each database; timezone and precision follow this API field, and absence is not an inferred event time. A connector directive uses this field to order records for latest-state or incremental processing.

Object

Developer identifier: databases.objectObject. Always ‘data_source’ for data source objects returned by search under Notion-Version 2025-09-03+. It distinguishes the provider-defined object state or classification for the database.

Enables: Filter Databases by the exact Notion-defined object in databases.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each database; preserve unknown and newly introduced labels.

Parent

Developer identifier: databases.parentParent. Immediate parent reference; for data sources this identifies the containing database_id. It preserves the nested context needed to interpret the parent database.

Enables: Attribute parent in databases.parent to the parent database; identify parent records where that nested parent object is absent.
Interpretation: Notion reports parent as a nested object on each database; optional children may be absent from a valid response.

Properties

Developer identifier: databases.propertiesProperties. Schema definition of database properties (columns) is a NotionDatabaseProperty. It preserves the nested context needed to interpret the parent database.

Enables: Attribute properties in databases.properties to the parent database; identify parent records where that nested properties object is absent.
Interpretation: Notion reports properties as a nested object on each database; optional children may be absent from a valid response.

Public URL

Developer identifier: databases.public_urlPublic URL. Public URL if the database is published to the web. It locates the provider resource or path associated with the database.

Enables: Associate each database with the resource identified by public URL in databases.public_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports public URL as a resource locator for each database; access still depends on viewer permissions and the URL may expire or change.

Title

Developer identifier: databases.titleTitle. Title of the database as an array of rich text objects. It preserves the nested context needed to interpret the parent database.

Enables: Search the returned title content in databases.title while preserving element order and attribution to the parent database.
Interpretation: Notion returns title as ordered content or provider-generated content metadata on each database; truncation, omission, and inaccessible source media can limit completeness.

URL

Developer identifier: databases.urlURL. URL to the database in the Notion UI. It locates the provider resource or path associated with the database.

Enables: Associate each database with the resource identified by URL in databases.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each database; access still depends on viewer permissions and the URL may expire or change.

Pages

Developer identifier: pagesPages. Pages in the workspace.

Enables: Inventory page metadata and properties, then connect each page to its parent and content-block traversal.
Scope: Reads the records selected by Notion’s /v1/search operation as a snapshot stream using incremental synchronization. This stream is opt-in. Only pages and databases explicitly shared with the Notion integration, plus their reachable children, are visible. Page records contain metadata and properties; ordered page body content is represented by the separate block stream, and file bytes are not downloaded. Removal is recognized from the provider’s tombstone state rather than absence alone.

Archived

Developer identifier: pages.archivedArchived. Whether the object has been archived (soft-deleted). It distinguishes the provider-defined archived state or classification for the page.

Enables: Filter Pages by whether the object has been archived (soft-deleted) in pages.archived; count true, false, and missing results separately.
Interpretation: Notion reports the object has been archived (soft-deleted) as a boolean on each page; a missing field is unknown, not false.

Cover

Developer identifier: pages.coverCover. Cover image for the page or database, or null if none. It preserves the nested context needed to interpret the parent page.

Enables: Attribute cover in pages.cover to the parent page; identify parent records where that nested cover object is absent.
Interpretation: Notion reports cover as a nested object on each page; optional children may be absent from a valid response.

External

Developer identifier: pages.cover.externalExternal. External file details, present when type is ‘external’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute external in pages.NotionFile.external to the parent page; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each Notion file; optional children may be absent from a valid response. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: pages.cover.external.urlURL. URL of the external file. It locates the provider resource or path associated with the Notion external file.

Enables: Associate each Notion external file with the resource identified by URL in pages.NotionExternalFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion external file; access still depends on viewer permissions and the URL may expire or change. This stream treats the file or attachment as metadata and references; binary bytes are not included.

File

Developer identifier: pages.cover.fileFile. Notion-hosted file details, present when type is ‘file’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute file in pages.NotionFile.file to the parent page; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each Notion file; optional children may be absent from a valid response. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Expiry Time

Developer identifier: pages.cover.file.expiry_timeExpiry Time. ISO 8601 expiration time for the signed URL. It anchors the page on the provider’s reported timeline.

Enables: Order Pages by expiry time in pages.NotionHostedFile.expiry_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports expiry time as a timestamp on each Notion hosted file; timezone and precision follow this API field, and absence is not an inferred event time. This stream treats the file or attachment as metadata and references; binary bytes are not included.

URL

Developer identifier: pages.cover.file.urlURL. Temporary signed URL for the Notion-hosted file. It locates the provider resource or path associated with the Notion hosted file.

Enables: Associate each Notion hosted file with the resource identified by URL in pages.NotionHostedFile.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion hosted file; access still depends on viewer permissions and the URL may expire or change. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Type

Developer identifier: pages.cover.typeType. File hosting type: ‘external’ or ‘file’. It distinguishes the provider-defined type state or classification for the Notion file.

Enables: Segment Notion file entries in Pages by type in pages.NotionFile.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion file; preserve unknown labels rather than mapping them by assumption. This stream treats the file or attachment as metadata and references; binary bytes are not included.

Created By

Developer identifier: pages.created_byCreated By. Partial user object representing who created this object. It preserves the nested context needed to interpret the parent page.

Enables: Attribute created by in pages.created_by to the parent page; identify parent records where that nested created by object is absent.
Interpretation: Notion reports created by as a nested object on each page; optional children may be absent from a valid response.

Avatar URL

Developer identifier: pages.created_by.avatar_urlAvatar URL. URL of the user’s avatar image. It locates the provider resource or path associated with the Notion partial user.

Enables: Associate each Notion partial user with the resource identified by avatar URL in pages.NotionPartialUser.avatar_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports avatar URL as a resource locator for each Notion partial user; access still depends on viewer permissions and the URL may expire or change.

Bot

Developer identifier: pages.created_by.botBot. Bot-specific details, present when type is ‘bot’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute bot in pages.NotionPartialUser.bot to the parent page; identify parent records where that nested bot object is absent.
Interpretation: Notion reports bot as a nested object on each Notion partial user; optional children may be absent from a valid response.

Owner

Developer identifier: pages.created_by.bot.ownerOwner. Owner of the bot integration. It preserves the nested context needed to interpret the parent page.

Enables: Attribute owner in pages.NotionBotDetail.owner to the parent page; identify parent records where that nested owner object is absent.
Interpretation: Notion reports owner as a nested object on each Notion bot detail; optional children may be absent from a valid response.

Type

Developer identifier: pages.created_by.bot.owner.typeType. Owner type: ‘workspace’ or ‘user’. It distinguishes the provider-defined type state or classification for the Notion bot owner.

Enables: Segment Notion bot owner entries in Pages by type in pages.NotionBotOwner.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion bot owner; preserve unknown labels rather than mapping them by assumption.

User

Developer identifier: pages.created_by.bot.owner.userUser. User owner if the bot is user-level. It preserves the nested context needed to interpret the parent page.

Enables: Attribute user in pages.NotionBotOwner.user to the parent page; identify parent records where that nested user object is absent.
Interpretation: Notion reports user as a nested object on each Notion bot owner; optional children may be absent from a valid response.

Workspace

Developer identifier: pages.created_by.bot.owner.workspaceWorkspace. True if the bot is workspace-level. It distinguishes the provider-defined workspace state or classification for the Notion bot owner.

Enables: Filter Pages by whether true if the bot is workspace-level in pages.NotionBotOwner.workspace; count true, false, and missing results separately.
Interpretation: Notion reports true if the bot is workspace-level as a boolean on each Notion bot owner; a missing field is unknown, not false.

Workspace Name

Developer identifier: pages.created_by.bot.workspace_nameWorkspace Name. Name of the workspace the bot belongs to. It gives the Notion bot detail a human-readable provider label while its identifier remains the stable reference.

Enables: Label each Notion bot detail with workspace name from pages.NotionBotDetail.workspace_name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports workspace name as display text for each Notion bot detail; names are mutable and are not stable identities.

Developer identifier: pages.created_by.idID. UUID of the user. It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each Notion partial user in Pages to the referenced Notion partial user through pages.NotionPartialUser.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its Notion partial user namespace; it is not a universal identity outside Notion.

Name

Developer identifier: pages.created_by.nameName. Display name of the user (may not be present in partial references). It gives the Notion partial user a human-readable provider label while its identifier remains the stable reference.

Enables: Label each Notion partial user with name from pages.NotionPartialUser.name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports name as display text for each Notion partial user; names are mutable and are not stable identities.

Object

Developer identifier: pages.created_by.objectObject. Always ‘user’. It distinguishes the provider-defined object state or classification for the Notion partial user.

Enables: Filter Pages by the exact Notion-defined object in pages.NotionPartialUser.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each Notion partial user; preserve unknown and newly introduced labels.

Person

Developer identifier: pages.created_by.personPerson. Person-specific details, present when type is ‘person’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute person in pages.NotionPartialUser.person to the parent page; identify parent records where that nested person object is absent.
Interpretation: Notion reports person as a nested object on each Notion partial user; optional children may be absent from a valid response.

Developer identifier: pages.created_by.person.emailEmail. Email address of the person. It supplies the provider-reported address or location facet for the Notion person detail, not a residency determination.

Enables: Attribute each Notion person detail to a person or account by the exact email in pages.NotionPersonDetail.email; identify addresses that do not match the Notion directory.
Interpretation: Notion reports email as an address on each Notion person detail; aliases, casing, and unverified addresses can prevent a one-to-one person match.

Type

Developer identifier: pages.created_by.typeType. Type of user: ‘person’ or ‘bot’. It distinguishes the provider-defined type state or classification for the Notion partial user.

Enables: Segment Notion partial user entries in Pages by type in pages.NotionPartialUser.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion partial user; preserve unknown labels rather than mapping them by assumption.

Created Time

Developer identifier: pages.created_timeCreated Time. ISO 8601 timestamp when the object was created. It anchors the page on the provider’s reported timeline.

Enables: Order Pages by created time in pages.created_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports created time as a timestamp on each page; timezone and precision follow this API field, and absence is not an inferred event time.

Description

Developer identifier: pages.descriptionDescription. Description rich text array (present on database objects). It preserves the nested context needed to interpret the parent page.

Enables: Search the returned description content in pages.description while preserving element order and attribution to the parent page.
Interpretation: Notion returns description as ordered content or provider-generated content metadata on each page; truncation, omission, and inaccessible source media can limit completeness.

Annotations

Developer identifier: pages.description.annotationsAnnotations. Styling annotations applied to this text segment. It preserves the nested context needed to interpret the parent page.

Enables: Attribute annotations in pages.NotionRichText.annotations to the parent page; identify parent records where that nested annotations object is absent.
Interpretation: Notion reports annotations as a nested object on each Notion rich text; optional children may be absent from a valid response.

Bold

Developer identifier: pages.description.annotations.boldBold. Whether the text is bold. It distinguishes the provider-defined bold state or classification for the Notion annotation.

Enables: Filter Pages by whether the text is bold in pages.NotionAnnotations.bold; count true, false, and missing results separately.
Interpretation: Notion reports the text is bold as a boolean on each Notion annotation; a missing field is unknown, not false.

Code

Developer identifier: pages.description.annotations.codeCode. Whether the text is displayed as inline code. It distinguishes the provider-defined code state or classification for the Notion annotation.

Enables: Filter Pages by whether the text is displayed as inline code in pages.NotionAnnotations.code; count true, false, and missing results separately.
Interpretation: Notion reports the text is displayed as inline code as a boolean on each Notion annotation; a missing field is unknown, not false.

Color

Developer identifier: pages.description.annotations.colorColor. Text color or background color name (e.g., ‘default’, ‘red’, ‘blue_background’). It supplies the returned color text needed to understand the Notion annotation in context.

Enables: Search the returned color text in pages.NotionAnnotations.color and attribute each match to its parent page and reported author when available.
Interpretation: Notion supplies color as returned text on each Notion annotation; truncation, formatting, and access boundaries can limit completeness.

Italic

Developer identifier: pages.description.annotations.italicItalic. Whether the text is italic. It distinguishes the provider-defined italic state or classification for the Notion annotation.

Enables: Filter Pages by whether the text is italic in pages.NotionAnnotations.italic; count true, false, and missing results separately.
Interpretation: Notion reports the text is italic as a boolean on each Notion annotation; a missing field is unknown, not false.

Strikethrough

Developer identifier: pages.description.annotations.strikethroughStrikethrough. Whether the text has strikethrough. It distinguishes the provider-defined strikethrough state or classification for the Notion annotation.

Enables: Filter Pages by whether the text has strikethrough in pages.NotionAnnotations.strikethrough; count true, false, and missing results separately.
Interpretation: Notion reports the text has strikethrough as a boolean on each Notion annotation; a missing field is unknown, not false.

Underline

Developer identifier: pages.description.annotations.underlineUnderline. Whether the text is underlined. It distinguishes the provider-defined underline state or classification for the Notion annotation.

Enables: Filter Pages by whether the text is underlined in pages.NotionAnnotations.underline; count true, false, and missing results separately.
Interpretation: Notion reports the text is underlined as a boolean on each Notion annotation; a missing field is unknown, not false.

Equation

Developer identifier: pages.description.equationEquation. Equation details, present when type is ‘equation’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute equation in pages.NotionRichText.equation to the parent page; identify parent records where that nested equation object is absent.
Interpretation: Notion reports equation as a nested object on each Notion rich text; optional children may be absent from a valid response.

Expression

Developer identifier: pages.description.equation.expressionExpression. The KaTeX expression string. It must be interpreted with the enclosing provider field name, type, or custom schema for the Notion equation.

Enables: Interpret pages.NotionEquation.expression with the enclosing custom field name, declared type, and provider schema; compare only records that share that contract.
Interpretation: Notion reports expression under the enclosing custom or typed field contract on each Notion equation; compare it only with values from the same provider key and type.

Href

Developer identifier: pages.description.hrefHref. URL link if the text is a hyperlink, or null. It locates the provider resource or path associated with the Notion rich text.

Enables: Associate each Notion rich text with the resource identified by href in pages.NotionRichText.href; verify the link resolves to the expected Notion object.
Interpretation: Notion reports href as a resource locator for each Notion rich text; access still depends on viewer permissions and the URL may expire or change.

Mention

Developer identifier: pages.description.mentionMention. Mention details, present when type is ‘mention’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute mention in pages.NotionRichText.mention to the parent page; identify parent records where that nested mention object is absent.
Interpretation: Notion reports mention as a nested object on each Notion rich text; optional children may be absent from a valid response.

Database

Developer identifier: pages.description.mention.databaseDatabase. Mentioned database reference. It preserves the nested context needed to interpret the parent page.

Enables: Attribute database in pages.NotionMention.database to the parent page; identify parent records where that nested database object is absent.
Interpretation: Notion reports database as a nested object on each Notion mention; optional children may be absent from a valid response.

Developer identifier: pages.description.mention.database.idID. UUID of the mentioned page. It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each Notion mention object in Pages to the referenced Notion mention object through pages.NotionMentionObject.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its Notion mention object namespace; it is not a universal identity outside Notion.

Date

Developer identifier: pages.description.mention.dateDate. Date value, present when type is ‘date’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute date in pages.NotionMention.date to the parent page; identify parent records where that nested date object is absent.
Interpretation: Notion reports date as a nested object on each Notion mention; optional children may be absent from a valid response.

End

Developer identifier: pages.description.mention.date.endEnd. End date (ISO 8601 date or datetime), or null for single dates. It anchors the page on the provider’s reported timeline.

Enables: Filter Pages by end in pages.NotionDateValue.end; pair that boundary with the corresponding start before measuring elapsed time.
Interpretation: Notion reports end as a timestamp on each Notion date value; timezone and precision follow this API field, and absence is not an inferred event time.

Start

Developer identifier: pages.description.mention.date.startStart. Start date (ISO 8601 date or datetime). It anchors the page on the provider’s reported timeline.

Enables: Filter Pages by start in pages.NotionDateValue.start; pair that boundary with the corresponding end before measuring elapsed time.
Interpretation: Notion reports start as a timestamp on each Notion date value; timezone and precision follow this API field, and absence is not an inferred event time.

Time Zone

Developer identifier: pages.description.mention.date.time_zoneTime Zone. IANA time zone if the date includes a time component. It is needed to interpret companion dates and times for the Notion date value in the provider’s intended zone.

Enables: Apply the zone in pages.NotionDateValue.time_zone when converting the page’s companion start, end, or scheduled timestamps; do not infer it from locale.
Interpretation: Notion reports time zone as a timezone identifier for each Notion date value; supported IANA or provider-specific names and daylight-saving behavior must be preserved.

Link Preview

Developer identifier: pages.description.mention.link_previewLink Preview. Link preview details. It preserves the nested context needed to interpret the parent page.

Enables: Attribute link preview in pages.NotionMention.link_preview to the parent page; identify parent records where that nested link preview object is absent.
Interpretation: Notion reports link preview as a nested object on each Notion mention; optional children may be absent from a valid response.

URL

Developer identifier: pages.description.mention.link_preview.urlURL. URL being previewed. It locates the provider resource or path associated with the Notion link preview.

Enables: Associate each Notion link preview with the resource identified by URL in pages.NotionLinkPreview.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion link preview; access still depends on viewer permissions and the URL may expire or change.

Page

Developer identifier: pages.description.mention.pagePage. Mentioned page reference. It preserves the nested context needed to interpret the parent page.

Enables: Attribute page in pages.NotionMention.page to the parent page; identify parent records where that nested page object is absent.
Interpretation: Notion reports page as a nested object on each Notion mention; optional children may be absent from a valid response.

Template Mention

Developer identifier: pages.description.mention.template_mentionTemplate Mention. Template mention details. It preserves the nested context needed to interpret the parent page.

Enables: Attribute template mention in pages.NotionMention.template_mention to the parent page; identify parent records where that nested template mention object is absent.
Interpretation: Notion reports template mention as a nested object on each Notion mention; optional children may be absent from a valid response.

Template Mention Date

Developer identifier: pages.description.mention.template_mention.template_mention_dateTemplate Mention Date. Template date keyword like ‘today’ or ‘now’. It anchors the page on the provider’s reported timeline.

Enables: Order Pages by template mention date in pages.NotionMentionTemplateMention.template_mention_date and isolate records inside an exact provider reporting window.
Interpretation: Notion reports template mention date as a calendar date on each Notion mention template mention; its grain is one day and no time of day should be inferred.

Template Mention User

Developer identifier: pages.description.mention.template_mention.template_mention_userTemplate Mention User. Template user keyword like ‘me’. It supplies the template mention user profile facet used to reconcile or attribute the Notion mention template mention.

Enables: Reconcile the page’s template mention user in pages.NotionMentionTemplateMention.template_mention_user with its provider profile or directory identity; confirm ambiguous matches with the stable provider ID.
Interpretation: Notion reports template mention user as a mutable profile or directory attribute on each Notion mention template mention; it may be absent, shared, or non-unique.

Type

Developer identifier: pages.description.mention.template_mention.typeType. Template mention type: ‘template_mention_date’ or ‘template_mention_user’. It distinguishes the provider-defined type state or classification for the Notion mention template mention.

Enables: Segment Notion mention template mention entries in Pages by type in pages.NotionMentionTemplateMention.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion mention template mention; preserve unknown labels rather than mapping them by assumption.

Type

Developer identifier: pages.description.mention.typeType. Mention type: ‘user’, ‘page’, ‘database’, ‘date’, ‘link_preview’, ‘template_mention’. It distinguishes the provider-defined type state or classification for the Notion mention.

Enables: Segment Notion mention entries in Pages by type in pages.NotionMention.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion mention; preserve unknown labels rather than mapping them by assumption.

User

Developer identifier: pages.description.mention.userUser. Mentioned user, present when type is ‘user’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute user in pages.NotionMention.user to the parent page; identify parent records where that nested user object is absent.
Interpretation: Notion reports user as a nested object on each Notion mention; optional children may be absent from a valid response.

Plain Text

Developer identifier: pages.description.plain_textPlain Text. Plain text content without annotations. It defines the content surface available for this page.

Enables: Locate Notion rich text records by plain text in pages.NotionRichText.plain_text; attribute each text match to its parent page and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Text

Developer identifier: pages.description.textText. Text content details, present when type is ‘text’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute text in pages.NotionRichText.text to the parent page; identify parent records where that nested text object is absent.
Interpretation: Notion reports text as a nested object on each Notion rich text; optional children may be absent from a valid response.

Content

Developer identifier: pages.description.text.contentContent. The actual text content. It defines the content surface available for this page.

Enables: Locate Notion text content records by content in pages.NotionTextContent.content; attribute each text match to its parent page and, when present, its reported author.
Interpretation: Notion returns the visible rich-text or block representation; external and uploaded file bytes are not embedded by this field.

Link

Developer identifier: pages.description.text.linkLink. Link object if the text contains a hyperlink, or null. It preserves the nested context needed to interpret the parent page.

Enables: Attribute link in pages.NotionTextContent.link to the parent page; identify parent records where that nested link object is absent.
Interpretation: Notion reports link as a nested object on each Notion text content; optional children may be absent from a valid response.

URL

Developer identifier: pages.description.text.link.urlURL. URL of the link. It locates the provider resource or path associated with the Notion text content link.

Enables: Associate each Notion text content link with the resource identified by URL in pages.NotionTextContentLink.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each Notion text content link; access still depends on viewer permissions and the URL may expire or change.

Type

Developer identifier: pages.description.typeType. Type of rich text: ‘text’, ‘mention’, or ‘equation’. It distinguishes the provider-defined type state or classification for the Notion rich text.

Enables: Segment Notion rich text entries in Pages by type in pages.NotionRichText.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion rich text; preserve unknown labels rather than mapping them by assumption.

Icon

Developer identifier: pages.iconIcon. Icon for the page or database (emoji or file), or null if none. It preserves the nested context needed to interpret the parent page.

Enables: Attribute icon in pages.icon to the parent page; identify parent records where that nested icon object is absent.
Interpretation: Notion reports icon as a nested object on each page; optional children may be absent from a valid response.

Emoji

Developer identifier: pages.icon.emojiEmoji. Emoji character, present when type is ‘emoji’. It distinguishes the provider-defined emoji state or classification for the Notion icon.

Enables: Filter Pages by the exact Notion-defined emoji in pages.NotionIcon.emoji and preserve unknown values as distinct categories.
Interpretation: Notion supplies emoji from its own taxonomy on each Notion icon; preserve unknown and newly introduced labels.

External

Developer identifier: pages.icon.externalExternal. External file details, present when type is ‘external’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute external in pages.NotionIcon.external to the parent page; identify parent records where that nested external object is absent.
Interpretation: Notion reports external as a nested object on each Notion icon; optional children may be absent from a valid response.

File

Developer identifier: pages.icon.fileFile. Notion-hosted file details, present when type is ‘file’. It preserves the nested context needed to interpret the parent page.

Enables: Attribute file in pages.NotionIcon.file to the parent page; identify parent records where that nested file object is absent.
Interpretation: Notion reports file as a nested object on each Notion icon; optional children may be absent from a valid response.

Type

Developer identifier: pages.icon.typeType. Icon type: ‘emoji’, ‘external’, or ‘file’. It distinguishes the provider-defined type state or classification for the Notion icon.

Enables: Segment Notion icon entries in Pages by type in pages.NotionIcon.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion icon; preserve unknown labels rather than mapping them by assumption.

Developer identifier: pages.idID. Unique identifier for the page or database (UUID format). It provides the reference needed to connect the page to the corresponding provider object.

Enables: Match repeated page entries on ID in pages.id; collapse only entries that share this declared transform key.
Interpretation: Notion reports ID as an identifier in its page namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key.

In Trash

Developer identifier: pages.in_trashIn Trash. Whether the object is in the trash. It distinguishes the provider-defined in trash state or classification for the page.

Enables: Filter Pages by whether the object is in the trash in pages.in_trash; count true, false, and missing results separately.
Interpretation: Notion reports the object is in the trash as a boolean on each page; a missing field is unknown, not false.

Is Inline

Developer identifier: pages.is_inlineIs Inline. Whether the database is inline (embedded within a page) rather than full-page. It distinguishes the provider-defined is inline state or classification for the page.

Enables: Filter Pages by whether the database is inline (embedded within a page) rather than full-page in pages.is_inline; count true, false, and missing results separately.
Interpretation: Notion reports the database is inline (embedded within a page) rather than full-page as a boolean on each page; a missing field is unknown, not false.

Last Edited By

Developer identifier: pages.last_edited_byLast Edited By. Partial user object representing who last edited this object. It preserves the nested context needed to interpret the parent page.

Enables: Attribute last edited by in pages.last_edited_by to the parent page; identify parent records where that nested last edited by object is absent.
Interpretation: Notion reports last edited by as a nested object on each page; optional children may be absent from a valid response.

Last Edited Time

Developer identifier: pages.last_edited_timeLast Edited Time. ISO 8601 timestamp when the object was last edited. It anchors the page on the provider’s reported timeline.

Enables: Order Pages by last edited time in pages.last_edited_time and isolate records inside an exact provider reporting window.
Interpretation: Notion reports last edited time as a timestamp on each page; timezone and precision follow this API field, and absence is not an inferred event time. A connector directive uses this field to order records for latest-state or incremental processing.

Object

Developer identifier: pages.objectObject. Object type: ‘page’, ‘database’, or ‘data_source’. It distinguishes the provider-defined object state or classification for the page.

Enables: Segment page entries in Pages by object in pages.object; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports object as a label from its own taxonomy on each page; preserve unknown labels rather than mapping them by assumption.

Parent

Developer identifier: pages.parentParent. Parent reference indicating where this object lives in the hierarchy. It preserves the nested context needed to interpret the parent page.

Enables: Attribute parent in pages.parent to the parent page; identify parent records where that nested parent object is absent.
Interpretation: Notion reports parent as a nested object on each page; optional children may be absent from a valid response.

Block ID

Developer identifier: pages.parent.block_idBlock ID. UUID of the parent block, if type is ‘block_id’. It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each Notion parent in Pages to the referenced block through pages.NotionParent.block_id; flag block ID values that do not resolve in that provider namespace.
Interpretation: Notion reports block ID as an identifier in its block namespace; it is not a universal identity outside Notion.

Data Source ID

Developer identifier: pages.parent.data_source_idData Source ID. UUID of the parent data source, if type is ‘data_source_id’ (2026 Notion API). It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each Notion parent in Pages to the referenced data source through pages.NotionParent.data_source_id; flag data source ID values that do not resolve in that provider namespace.
Interpretation: Notion reports data source ID as an identifier in its data source namespace; it is not a universal identity outside Notion.

Database ID

Developer identifier: pages.parent.database_idDatabase ID. UUID of the parent database, if type is ‘database_id’. It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each Notion parent in Pages to the referenced database through pages.NotionParent.database_id; flag database ID values that do not resolve in that provider namespace.
Interpretation: Notion reports database ID as an identifier in its database namespace; it is not a universal identity outside Notion.

Page ID

Developer identifier: pages.parent.page_idPage ID. UUID of the parent page, if type is ‘page_id’. It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each Notion parent in Pages to the referenced page through pages.NotionParent.page_id; flag page ID values that do not resolve in that provider namespace.
Interpretation: Notion reports page ID as an identifier in its page namespace; it is not a universal identity outside Notion.

Type

Developer identifier: pages.parent.typeType. Type of parent: ‘database_id’, ‘page_id’, ‘workspace’, or ‘block_id’. It distinguishes the provider-defined type state or classification for the Notion parent.

Enables: Segment Notion parent entries in Pages by type in pages.NotionParent.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each Notion parent; preserve unknown labels rather than mapping them by assumption.

Workspace

Developer identifier: pages.parent.workspaceWorkspace. True if the parent is the workspace root. It distinguishes the provider-defined workspace state or classification for the Notion parent.

Enables: Filter Pages by whether true if the parent is the workspace root in pages.NotionParent.workspace; count true, false, and missing results separately.
Interpretation: Notion reports true if the parent is the workspace root as a boolean on each Notion parent; a missing field is unknown, not false.

Properties

Developer identifier: pages.propertiesProperties. Page properties (title, status, assignee, dates, etc.) or database property schema definitions. Keys are property names, values are property value or definition objects. Is NotionPropertyValue. It preserves the nested context needed to interpret the parent page.

Enables: Attribute properties in pages.properties to the parent page; identify parent records where that nested properties object is absent.
Interpretation: Notion reports properties as a nested object on each page; optional children may be absent from a valid response.

Public URL

Developer identifier: pages.public_urlPublic URL. Public URL if the page is published to the web, or null. It locates the provider resource or path associated with the page.

Enables: Associate each page with the resource identified by public URL in pages.public_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports public URL as a resource locator for each page; access still depends on viewer permissions and the URL may expire or change.

Request ID

Developer identifier: pages.request_idRequest ID. Request ID returned by the API for tracing. It provides the reference needed to connect the page to the corresponding provider object.

Enables: Connect each page in Pages to the referenced request through pages.request_id; flag request ID values that do not resolve in that provider namespace.
Interpretation: Notion reports request ID as an identifier in its request namespace; it is not a universal identity outside Notion.

Title

Developer identifier: pages.titleTitle. Title rich text array (present on database objects). It preserves the nested context needed to interpret the parent page.

Enables: Search the returned title content in pages.title while preserving element order and attribution to the parent page.
Interpretation: Notion returns title as ordered content or provider-generated content metadata on each page; truncation, omission, and inaccessible source media can limit completeness.

URL

Developer identifier: pages.urlURL. URL to the page or database in Notion. It locates the provider resource or path associated with the page.

Enables: Associate each page with the resource identified by URL in pages.url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports URL as a resource locator for each page; access still depends on viewer permissions and the URL may expire or change.

Users

Developer identifier: usersUsers. Workspace users.

Enables: Reconcile Notion people and bots to their identifiers, names, account type, email when visible, and bot-owner context.
Scope: Reads the records selected by Notion’s /v1/users operation as a snapshot stream using full synchronization. Only pages and databases explicitly shared with the Notion integration, plus their reachable children, are visible. The stream does not include records the credential, parent traversal, configured filters, or provider API omits. A later complete read can treat a previously seen record that is absent as removed.

Avatar URL

Developer identifier: users.avatar_urlAvatar URL. URL of the user’s avatar image, or null if not set. It locates the provider resource or path associated with the user.

Enables: Associate each user with the resource identified by avatar URL in users.avatar_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports avatar URL as a resource locator for each user; access still depends on viewer permissions and the URL may expire or change.

Bot

Developer identifier: users.botBot. Bot-specific details. Present only when type is ‘bot’. It preserves the nested context needed to interpret the parent user.

Enables: Attribute bot in users.bot to the parent user; identify parent records where that nested bot object is absent.
Interpretation: Notion reports bot as a nested object on each user; optional children may be absent from a valid response.

Owner

Developer identifier: users.bot.ownerOwner. Information about who owns the bot. It preserves the nested context needed to interpret the parent user.

Enables: Attribute owner in users.BotDetails.owner to the parent user; identify parent records where that nested owner object is absent.
Interpretation: Notion reports owner as a nested object on each bot detail; optional children may be absent from a valid response.

Type

Developer identifier: users.bot.owner.typeType. The type of owner: ‘workspace’ or ‘user’. It distinguishes the provider-defined type state or classification for the bot owner.

Enables: Segment bot owner entries in Users by type in users.BotOwner.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each bot owner; preserve unknown labels rather than mapping them by assumption.

User

Developer identifier: users.bot.owner.userUser. The user who owns this bot. Present when type is ‘user’. It preserves the nested context needed to interpret the parent user.

Enables: Attribute user in users.BotOwner.user to the parent user; identify parent records where that nested user object is absent.
Interpretation: Notion reports user as a nested object on each bot owner; optional children may be absent from a valid response.

Avatar URL

Developer identifier: users.bot.owner.user.avatar_urlAvatar URL. URL of the owning user’s avatar image. It locates the provider resource or path associated with the bot owner user.

Enables: Associate each bot owner user with the resource identified by avatar URL in users.BotOwnerUser.avatar_url; verify the link resolves to the expected Notion object.
Interpretation: Notion reports avatar URL as a resource locator for each bot owner user; access still depends on viewer permissions and the URL may expire or change.

Developer identifier: users.bot.owner.user.idID. Unique identifier of the owning user. It provides the reference needed to connect the user to the corresponding provider object.

Enables: Connect each bot owner user in Users to the referenced bot owner user through users.BotOwnerUser.id; flag ID values that do not resolve in that provider namespace.
Interpretation: Notion reports ID as an identifier in its bot owner user namespace; it is not a universal identity outside Notion.

Name

Developer identifier: users.bot.owner.user.nameName. Display name of the owning user. It gives the bot owner user a human-readable provider label while its identifier remains the stable reference.

Enables: Label each bot owner user with name from users.BotOwnerUser.name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports name as display text for each bot owner user; names are mutable and are not stable identities.

Object

Developer identifier: users.bot.owner.user.objectObject. Always ‘user’ for user objects. It distinguishes the provider-defined object state or classification for the bot owner user.

Enables: Filter Users by the exact Notion-defined object in users.BotOwnerUser.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each bot owner user; preserve unknown and newly introduced labels.

Person

Developer identifier: users.bot.owner.user.personPerson. Person details of the owning user, if applicable. It preserves the nested context needed to interpret the parent user.

Enables: Attribute person in users.BotOwnerUser.person to the parent user; identify parent records where that nested person object is absent.
Interpretation: Notion reports person as a nested object on each bot owner user; optional children may be absent from a valid response.

Developer identifier: users.bot.owner.user.person.emailEmail. Email address of the person user. It supplies the provider-reported address or location facet for the person detail, not a residency determination.

Enables: Attribute each person detail to a person or account by the exact email in users.PersonDetails.email; identify addresses that do not match the Notion directory.
Interpretation: Notion reports email as an address on each person detail; aliases, casing, and unverified addresses can prevent a one-to-one person match. A connector directive maps this field to a person’s email identity.

Type

Developer identifier: users.bot.owner.user.typeType. The type of the owning user (typically ‘person’). It distinguishes the provider-defined type state or classification for the bot owner user.

Enables: Segment bot owner user entries in Users by type in users.BotOwnerUser.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each bot owner user; preserve unknown labels rather than mapping them by assumption.

Workspace

Developer identifier: users.bot.owner.workspaceWorkspace. True if the bot is owned by the entire workspace. Present when type is ‘workspace’. It distinguishes the provider-defined workspace state or classification for the bot owner.

Enables: Filter Users by whether true if the bot is owned by the entire workspace in users.BotOwner.workspace; count true, false, and missing results separately.
Interpretation: Notion reports true if the bot is owned by the entire workspace as a boolean on each bot owner; a missing field is unknown, not false.

Workspace Name

Developer identifier: users.bot.workspace_nameWorkspace Name. Name of the workspace the bot belongs to. Present for workspace-level bots. It gives the bot detail a human-readable provider label while its identifier remains the stable reference.

Enables: Label each bot detail with workspace name from users.BotDetails.workspace_name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports workspace name as display text for each bot detail; names are mutable and are not stable identities.

Developer identifier: users.idID. Unique identifier for the user (UUIDv4). It provides the reference needed to connect the user to the corresponding provider object.

Enables: Match repeated user entries on ID in users.id; collapse only entries that share this declared transform key.
Interpretation: Notion reports ID as an identifier in its user namespace; it is not a universal identity outside Notion. The connector explicitly marks this field as a transform deduplication key. A connector directive maps this field to account identity.

Name

Developer identifier: users.nameName. Display name of the user. It gives the user a human-readable provider label while its identifier remains the stable reference.

Enables: Label each user with name from users.name; distinguish records that share that display name but have different Notion identifiers.
Interpretation: Notion reports name as display text for each user; names are mutable and are not stable identities. A connector directive maps this field to a person’s display name.

Object

Developer identifier: users.objectObject. Always ‘user’ for user objects. It distinguishes the provider-defined object state or classification for the user.

Enables: Filter Users by the exact Notion-defined object in users.object and preserve unknown values as distinct categories.
Interpretation: Notion supplies object from its own taxonomy on each user; preserve unknown and newly introduced labels.

Person

Developer identifier: users.personPerson. Person-specific details. Present only when type is ‘person’. It preserves the nested context needed to interpret the parent user.

Enables: Attribute person in users.person to the parent user; identify parent records where that nested person object is absent.
Interpretation: Notion reports person as a nested object on each user; optional children may be absent from a valid response.

Developer identifier: users.person.emailEmail. Email address of the person user. It supplies the provider-reported address or location facet for the person, not a residency determination.

Enables: Attribute each person to a person or account by the exact email in users.person.email; identify addresses that do not match the Notion directory.
Interpretation: Notion reports email as an address on each person; aliases, casing, and unverified addresses can prevent a one-to-one person match. A connector directive maps this field to a person’s email identity.

Request ID

Developer identifier: users.request_idRequest ID. Request ID returned by the API for tracing purposes. It provides the reference needed to connect the user to the corresponding provider object.

Enables: Connect each user in Users to the referenced request through users.request_id; flag request ID values that do not resolve in that provider namespace.
Interpretation: Notion reports request ID as an identifier in its request namespace; it is not a universal identity outside Notion.

Type

Developer identifier: users.typeType. Whether the user is a ‘person’ or ‘bot’. It distinguishes the provider-defined type state or classification for the user.

Enables: Segment user entries in Users by type in users.type; compare counts only within the same Notion taxonomy.
Interpretation: Notion reports type as a label from its own taxonomy on each user; preserve unknown labels rather than mapping them by assumption.

Error	Meaning	Solution
`unauthorized`	Invalid token	Verify token is correct
`object_not_found`	No access to object	Share the page/database with the connection
`restricted_resource`	Insufficient capabilities	Enable required capability in connection settings
`rate_limited`	Too many requests	Implement backoff

Common Issues

Connection can’t find pages

Content must be explicitly shared with the connection. Go to the page → ••• → Add connections → select Parable.

Missing user emails

Ensure Read user information including email addresses is enabled in connection capabilities.Notion API — Official API referenceIntegration Guide — Getting started guide

​Pages & Databases

​Users

​Data streams

​API token

​What You’ll Need

​Step 1: Create Connection

​Step 2: Configure Capabilities

​Step 3: Copy Token

​Step 4: Share Content with Connection

​Step 5: Enter values in the form

​Common Issues

​Connection can’t find pages

​Missing user emails

Pages & Databases

Users

Data streams

API token

What You’ll Need

Step 1: Create Connection

Step 2: Configure Capabilities

Step 3: Copy Token

Step 4: Share Content with Connection

Step 5: Enter values in the form

Common Issues

Connection can’t find pages

Missing user emails