Notion AI · Practical walkthrough

What a Notion Agent can change, and how to review the result

You asked Notion Agent to update the project page from this morning's meeting. It did, and it also tidied up a line nobody discussed.

Task by Task12 min read + practice

What you'll make

a project page updated by Notion Agent from your meeting notes, with every change checked and anything extra undone.

What you'll need

Notion Agent (included on Business and Enterprise plans), edit access to the project page, the meeting notes and about fifteen minutes. New to Notion AI? Start with the beginner’s guide.

Example result.

Office move: Floor 4
Status: At risk (lift booking not confirmed)   ← changed
Owner: Ines Duarte                              ← changed
Next milestone: furniture delivery, 19 November ← changed
Move-day briefing: optional for all staff       ← unchanged

What Notion Agent can change

Notion Agent has the same permissions you do. If you can edit it, so can the Agent. It can:

create and edit pages;
create and edit databases, views and properties, including relations;
read comments and search version history;
search connected apps such as Slack, and post in Slack once you’ve connected your own account.

It can’t share pages, change permission levels, write comments, create reminders or database automations, or change workspace settings such as roles and billing. Notion’s Agent guide has the current list.

That’s why a small page job needs a clear source and a clear target: your access usually covers far more than the job.

1. Ask for a plan before any edits

Open the page you want updated. Click the Agent’s face at the bottom of Notion. @-mention the meeting notes page so the Agent reads the right source, then ask for a plan only.

Don't edit anything yet. Using only @[meeting notes], plan the updates to this page's Status, Owner and Next milestone. For each, show the current text, the proposed text and the line in the notes that supports it. List anything the notes leave unclear. Don't propose changes to any other part of the page.

[meeting notes] is the notes page you @-mention.

Why this works: a plan with the supporting line for each change lets you catch a wrong owner or date before it lands on the page.

What you should see: three proposed changes, each with a quote from the notes, and a short list of anything unclear. If the Agent edits anyway, undo the change (step 3) and ask again, starting with “Do not edit.”

2. Apply only the changes you checked

Read the plan against the notes. Fix anything wrong in your reply, then ask the Agent to apply it.

Apply only the three changes in your plan, with my corrections: [corrections]. Leave every other block on this page exactly as it is. Don't edit other pages or databases, and don't post anywhere. When you're done, list each block you changed.

[corrections] is anything you changed in the plan, or “none”.

Why this works: naming what stays the same gives the Agent a clear edge to the job, and the list of changed blocks tells you where to look.

What you should see: a reply listing three changed blocks, and the page showing those three changes.

3. Check the page, not the reply

The Agent’s summary is what it meant to do. The page is what it did. Read the whole page, not just the three lines you asked about.

If something changed that shouldn’t have, open ••• › Version history at the top of the page. Compare the latest version with the one from before the Agent’s edit. Notion keeps page history for 7 days on Free, 30 on Plus, 90 on Business and indefinitely on Enterprise. You need edit access to see it.

Why this works: version history shows every change, including the ones the Agent didn’t mention.

What you should see: the three changes you approved and nothing else.

Check the result

Status, Owner and Next milestone match the notes, word for word where it matters.
Every other block is unchanged when you compare with the earlier version.
Nothing unclear in the notes has been filled in with a guess.
No other page or database was touched.

The usual failure: the Agent makes the changes you asked for, plus one it thought was helpful. A wording tweak, a “tidied” line, an optional item made required. The reply often doesn’t mention it. You’ll find it by comparing the page with its version history.

You also changed [block] from "[old text]" to "[new text]". That wasn't part of the job. Put that block back exactly as it was. Keep the three changes we agreed. If other people have edited the page since, don't overwrite their work; tell me instead. Then list every block that now differs from the version before your first edit.

[block] is the line that changed; [old text] and [new text] are its before and after wording.

Worked example: the briefing that became compulsory

Fictional example. The Floor 4 office move page before the meeting:

Status: On track
Owner: Sam Whitlock
Next milestone: furniture delivery, 12 November
Move-day briefing: optional for all staff

Meeting notes: “Sam hands over to Ines Duarte from Monday. Supplier moved delivery to 19 Nov. Lift booking still not confirmed, so flag as at risk.”

The Agent’s reply said “Updated Status, Owner and Next milestone.” The page also said:

Move-day briefing: required for all staff

The failure. Nobody discussed the briefing. The Agent turned “optional” into “required”, and its reply didn’t mention the change.
How it was spotted. ••• › Version history showed four changed blocks, not three.
The repair. The repair prompt with “Move-day briefing”, “optional for all staff” and “required for all staff” restored the line. The Agent then listed three changed blocks, which matched the history.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Optional training: Keep a review record for repeat jobs

If you ask the Agent to update the same kind of page every week, keep a short record for each run. It makes the check quicker and shows if the same extra edit keeps coming back.

Source:
Target page and blocks:
Changes agreed:
Changes found in version history:
Extra edits undone:

If you save the request as a skill for Notion Agent, keep the target page and “leave every other block as it is” in each run. A saved instruction tells the Agent what to do; it doesn’t limit what your access allows.

Optional training: Keep connected apps out of a page job

Once you’ve connected Slack, the Agent can post messages and reply in threads as you. For a page update, that’s a side effect you don’t want. Say “don’t post anywhere” in the request, as in step 2, and check your Slack activity afterwards if the Agent’s reply mentions a message. If you want the update shared, post it yourself once the page is right.

Optional training: Undo without losing other people's work

Restoring an older version of a page brings back everything from that moment, so it can wipe edits colleagues made after the Agent ran. If others have edited since, put back only the one block, by asking the Agent (the repair prompt) or by copying the old wording from version history. Restores in Notion can themselves be reversed, so a mistaken restore isn’t final.