The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jul 7, 2026 8:47pm

PR Summary

Medium Risk
Touches many Notion workflow paths and changes legacy block output shapes by operation, which could affect existing workflows that relied on missing or generic outputs; changes are largely additive fixes with no OAuth scope changes.

Overview
This PR tightens the Notion integration so tools, blocks, and docs match the live API and workflows can use operations that were previously half-wired.

New and exposed capabilities: Adds notion_retrieve_block / _v2 (GET /v1/blocks/{id}) and wires it through the block dropdown, registry, and docs. notion_update_page is now usable in the UI (operation, page picker, JSON properties) instead of only being registered in tool config. startCursor pagination is supported on query database and search in tools, advanced block fields, and integration docs.

Reliability and UX fixes: Notion IDs used in request URLs are .trim()’d across read/write/create/update and related tools to avoid copy-paste whitespace failures. Create page no longer requires content in the block (title-only pages). Legacy NotionBlock outputs are split by operation so block/comment/user/block ops expose flat fields (id, results, block, has_children, etc.), not only content/metadata; Notion v2 output conditions are aligned similarly.

Cleanup: Removes dead/unused type helpers in types.ts and drops a shadow NotionReadDatabaseParams interface.

^{Reviewed by Cursor Bugbot for commit 040d6e7. Configure here.}

Greptile Summary

This PR closes a set of alignment gaps between the Notion integration's UI, tool registry, and live API docs: notion_update_page was registered but unreachable, nine operations were missing outputs in the legacy block, and there was no tool to fetch a single block's content (GET /v1/blocks/{id}).

• notion_retrieve_block / notion_retrieve_block_v2 — new tools covering the missing GET /v1/blocks/{id} endpoint; correctly trimmed, wired into both legacy and V2 blocks with full output conditions (id, type, has_children, archived, block).
• Legacy NotionBlock overhaul — notion_update_page added to the dropdown with its properties sub-block and output conditions; nine previously output-less operations (add_row, append/retrieve/update/delete block, comments, users) now expose the correct flat output fields with per-operation conditions.
• Whitespace hardening & pagination — .trim() added to all ID params used in request URLs across eight tool files; startCursor pagination param added to query_database and search.

Confidence Score: 5/5

Safe to merge — changes are additive fixes to the Notion integration with no breaking API surface changes.

All changes are additive: new tools, new output conditions, and whitespace guards. The legacy block and V2 block are both correctly wired, the tool registry is updated, and the V2 versioned-selector pattern is followed consistently. The only finding is a documentation inaccuracy in the newly added docs section that does not affect runtime behavior.

apps/docs/content/docs/en/integrations/notion.mdx — the notion_retrieve_block output table lists all shared outputs rather than just what the tool returns.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User selects operation in Notion Block] --> B{Block version?}
    B -- Legacy NotionBlock --> C[getTool switch → notion_retrieve_block]
    B -- NotionV2Block --> D[createVersionedToolSelector\n operation + '_v2'\n → notion_retrieve_block_v2]
    C --> E[notionRetrieveBlockTool\nGET /v1/blocks/blockId.trim]
    D --> F[notionRetrieveBlockV2Tool\nshares request + transformResponse]
    E --> G[transformResponse\nsuccess: response.ok\noutput: id, type, has_children,\narchived, block]
    F --> G
    G --> H[Block outputs conditioned on\n'notion_retrieve_block'\nid · type · has_children\narchived · block]

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[User selects operation in Notion Block] --> B{Block version?}
    B -- Legacy NotionBlock --> C[getTool switch → notion_retrieve_block]
    B -- NotionV2Block --> D[createVersionedToolSelector\n operation + '_v2'\n → notion_retrieve_block_v2]
    C --> E[notionRetrieveBlockTool\nGET /v1/blocks/blockId.trim]
    D --> F[notionRetrieveBlockV2Tool\nshares request + transformResponse]
    E --> G[transformResponse\nsuccess: response.ok\noutput: id, type, has_children,\narchived, block]
    F --> G
    G --> H[Block outputs conditioned on\n'notion_retrieve_block'\nid · type · has_children\narchived · block]

_{Reviews (4): Last reviewed commit: "fix(notion): document type-specific cont..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review

@greptile