Notion

Search pages and databases, and read a page down to its blocks.

Notion
Notion
Notion

What did we agree about implementation, and where is it written down.

A scene playing on a loop. Somebody says: What did we agree about implementation, and where is it written down.. The run reaches notion, which returns search_pages, 4; then notion, which returns get_page; then notion, which returns get_block_children. The delivery decision, and the page it sits on. Nothing edited.
Authorised by
A Notion integration token, scoped to the pages you share with it.
Reads
  • get_identity
  • search_pages
  • search_databases
  • query_database
  • get_page
  • get_block_children
Writes
  • create_page
  • append_block

These are the rows it can call, and there are no others. Across 8 connectors, 14 capability rows write anything.

Where it stops

It can add a page and append blocks to one. It rewrites nothing already written and archives nothing. It sees only what you share with the integration, which is Notion’s boundary rather than one we impose, and its search and query calls are POSTs that change nothing.

Finish the client call with the work already mapped.

Send one recent client meeting. Leave with the actions, follow-ups and exceptions a person can approve.