[Feat] Add positioned Notion content tools - #1434
Merged
Merged
Conversation
Contributor
Contributor
Author
mrubens
marked this pull request as ready for review
August 17, 2026 16:18
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 17, 2026 16:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
notion-insert-blockswith only the currentpositionschema for start, end, and after-block placementnotion-fetchand content edits innotion-update-pageinstead of exposing duplicate Markdown-specific toolsnotion-move-pagesand async operation polling throughnotion-get-async-taskafterinput, compatibility branches, and migration-oriented behaviorWhy this change was made
Agents could previously append blocks only at the end of Notion content, which prevented workflows that place new material at the top. The current Notion public API supports positioning newly created blocks, but explicitly does not support moving or reordering existing blocks while preserving their identity.
Impact
Deployment-wide Notion connections gain a smaller official-style tool surface for content placement and page editing without changing the existing internal-integration authorization model. Existing connections do not require OAuth reauthorization; administrators only need to enable Insert content for positioned block creation and Update content for Markdown updates and page moves in Notion when those capabilities are not already enabled.