change a notion page property without rewriting its text
mark the reviewed work ready without rewriting its notes. a bot can update a notion page's properties, icon, cover or archive state. body text uses a separate action.
it first reads your database's field names and valid statuses. capital letters must match too. ask for old and new values before it writes.

update page, in plain words
get the tracker to reflect the work you've approved. paste the page link or let the bot search by name. it reads the row and database for the real field names and allowed choices.
this action changes page details, including icon, cover and archive state. body paragraphs need a content action. keep the routine focused on the property you chose.
a routine to copy
paste this into a chat with your bot
every thursday at 10:50, read the catalogue review tracker in notion. find entries with an approval date in the past week and a linked catalogue page. fetch each page and its database fields.
propose changing only review status to ready, if ready is an existing choice. skip pages already ready. show old and new values here and ask me before changing anything. report the titles you changed afterward. never edit body text, add a status choice or archive pages.- when
- thursdays at 10:50
- needs
- notion read and write for tracker reads, page and database reads, and property updates
what comes back looks like this (an example)
review-status proposal
- lio's ceramic vessels: in review to ready
- marsh reed prints: skipped; no ready choice in its database
one status to approve. body text and archive state stay as they are.good jobs for it
- mark a reviewed catalogue item ready. use the status that already exists in its database.
- correct a misspelled title. target the known page rather than searching by the mistaken spelling alone.
- change the project icon. use the symbol your team chose.
- restore an archived database page. do that only when you ask for restoration.
before it runs
dusk bot counts Update Page as a change: it alters something in Notion, and the sending setting does not cover it. a bot you allow only to read can never call it.
how to start
- allow the property update. connect notion with read and write for this bot.
- inspect one page first. ask for its actual fields and the valid status choices.
- name the one change. request the old and new values before it writes.
- open the saved field in notion. schedule upkeep after that trial. pause if it proposes unrelated edits.
limits worth knowing
- status names differ across workspaces. guessed fields or wrong capital letters can fail, even when the name looks familiar.
- archiving is a real change. workspace-level pages can restrict it. leave archive state out of ordinary status upkeep.
- your review rule covers property edits. they do not wait for sending approval.
the details it works from
| input | required | what it is |
|---|---|---|
page_id | yes | Identifier for the Notion page to be updated. |
icon | no | Page icon object. |
cover | no | Page cover image. |
archived | no | Set to true to archive (trash) the page, false to restore. |
properties | no | Dictionary mapping property names to property value objects. |
from composio's catalog for Notion (action NOTION_UPDATE_PAGE, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- paste one notion page link
- ask for its current properties and status choices
- choose one field and ask for a preview
- allow the change, then inspect that field
mistakes people make
guessing every database has a ready status
read its choices first. skip entries where ready does not exist.
letting a status bot archive old work
tell it to leave archive state alone. that is a different decision.
questions
can it rewrite the paragraphs on the page?
no. this changes properties, icon, cover or archive state. the body needs a separate content action.
why does a status change fail with an invalid option?
that database must already have the choice. ask the bot to read its fields and use the exact name.
can i change the icon without touching the status?
yes. ask for the icon alone and tell it to leave other properties as they are.
sources
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
ask for the notion records that match your conditions
a notion bot that keeps the next step easy to find
add a batch of notes to an existing notion page
leave a useful notion comment where it belongs
give new notion notes a proper home
turn a clear request into a notion database row