Notion

You describe what you remember of the title, it searches, and then it reads whichever result you pick and tells you what is in it. Nothing is changed by asking, and finding the page was always the hard part.

What you end up with. The page you were hunting for, plus a summary of what it actually says.

Start with it bringing you the information and you deciding.

Never without. Remember that Notion search only returns what has been shared with the connection, and its index lags behind recent changes. A page missing from the results is not proof it does not exist.

Built on: Search Notion pages and databases / Retrieve page / Get page markdown

It pulls the whole page as markdown in a single call, or walks the nested blocks when the detail is in sub-pages. You get an answer about the content rather than a link telling you to go read it.

What you end up with. A plain summary of a long page, with the parts that matter quoted back.

Start with it bringing you the information and you deciding.

Never without. Check the summary against the page before you forward it to anyone. Summaries drop the caveats first, and the caveats are often why the page was written.

Built on: Get page markdown / Fetch Notion Block Children / Fetch All Notion Block Contents

It creates the page under the parent you name and adds the content as real blocks with markdown formatting preserved. Text over Notion's two thousand character block limit is split automatically rather than failing.

What you end up with. A finished notes page in the right place, formatted, with no copy and paste.

Start with it doing the work and checking with you.

Never without. Name the parent page yourself. Left to choose, it puts the page somewhere defensible and you spend longer finding it than you would have spent writing it.

Built on: Create Notion page / Add multiple content blocks (bulk, user-friendly) / Search Notion pages and databases

Yes, and it fetches the database schema first so each part of your sentence lands in a property of the right type. You say what happened and it works out which column that belongs in, whether that means a new row or setting properties on one that already exists. Finding the existing row is a filtered query rather than a guess, so it changes the row you meant.

What you end up with. A tracker that matches what you just said, with rows added or their properties set, and the row it touched named back to you.

Start with it doing the work and checking with you.

Never without. Have it name the row and the exact property it is about to change before it changes anything. A property name that does not match exactly gets rejected outright, but a value that lands in the wrong column does not, and an update overwrites the previous value with page history as the only route back to it.

Built on: Fetch Database / Insert Row From Natural Language / Insert row database / Query database with filter / Update Database Row (Page)

Upserting matches each incoming item against a filter you define, updates the row when it finds one, and creates the row when it does not. That is the difference between syncing a list and ending up with two of everything.

What you end up with. A database that matches your source list, with no duplicate rows.

Start with it doing the work and checking with you.

Never without. Test the matching filter on a handful of rows first. A filter that matches nothing turns every update into a new row, and one that matches too much overwrites rows you meant to keep.

Built on: Upsert database rows / Query database with filter / Fetch Database

There is an action for exactly this. It deletes the page's existing child blocks and then appends the new ones in batches. Notion offers no transaction around that sequence, so a run that fails part way leaves the page half rebuilt. The action can take a backup first.

What you end up with. A rebuilt page, plus a backup copy of the content it replaced.

Start with it doing the work and checking with you.

Never without. Always take the backup, and never point a rebuild at a page other people are editing. The existing blocks are deleted before the new ones are written, and an interrupted run leaves the page in a partial state.

Built on: Replace page content (with backup) / Get page markdown / Add multiple content blocks (bulk, user-friendly)

Comments are readable through the connection, and it fetches the unresolved ones for a page so you get what is actually still open rather than the whole thread history. It can pull any single comment in full, read the page they are about so the question has its context, and look up who left each one. Replying is a write into an existing discussion, so the answer lands in the thread the person is watching.

What you end up with. The open comments on a page with who asked what, and your replies posted into the threads they belong to.

Start with it doing the work and checking with you.

Never without. Read every reply before it posts. A comment is addressed to a named colleague and appears under your name, and the connector cannot start a new inline thread on a block, so a reply that misses the point lands in the wrong discussion with no way to move it.

Built on: Fetch comments / Retrieve Comment / Retrieve page / List users / Create comment

Notion databases are creatable through the connection, with the columns and their types defined up front, and an existing one's schema can be changed afterward. So the shape of the tracker is something you can describe rather than click together, and the assistant can read a property back to check what type it ended up as. The database is created as a subpage of a parent page you name.

What you end up with. A Notion database with the columns you described, typed, sitting under the parent page you chose.

Start with it doing the work and checking with you.

Never without. Name the parent page yourself, because the new database is created underneath it and inherits that page's sharing. Keep schema changes off a database people already use until you have read the current properties back, since retyping or removing a column changes what every existing row holds and the connector shows you no preview.

Built on: Create Notion Database / Update database schema / Fetch Database / Retrieve Database Property / Search Notion pages and databases