dusk botreview a notion rewrite before replacing its blocks
see the whole rewrite before the old checklist goes. this action replaces a notion page's child blocks and offers a dry run first. it can also make a backup.
some blocks and nested content stay out of that backup, and a staged replacement can fail halfway. use the preview to decide whether a full rewrite is worth it.
replace page content (with backup), in plain words
use replacement when the old body really should go. give the bot the page and new text. a dry run shows what it would remove and add without doing it.
it normally archives the old children, then adds the new ones in batches. an optional backup isn't a complete copy of every page structure. inspect complex pages before trusting this route.
a routine to copy
paste this into a chat with your bot
on the last wednesday of each month at 14:35, read the cinderbrook equipment checklist in notion. compare it with the latest file in the approved checklists project folder. if the contents match, stay quiet. otherwise run a dry preview and report the blocks affected here. ask me before you change anything. stop if nested content, toggles or sub-pages make the backup incomplete. after i approve, make a backup and replace only that page. report partial failures and never retry blindly.- when
- last wednesday of the month at 14:35
- needs
- access to the approved checklists project folder; notion read and write for inspecting, previewing and replacing the chosen page
what comes back looks like this (an example)
cinderbrook checklist preview
- current body: flat checklist blocks
- proposed body: new opening and closing checks
- backup: required before an approved replacement
dry run only. existing page unchanged.good jobs for it
- equipment checks: replace a flat checklist with the new version you approved.
- event instructions: update a simple page after the venue agrees to the procedure.
- a rewrite decision: preview the full replacement and decide if small additions would do.
before it runs
dusk bot counts Replace page content (with backup) 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.
the permissions Notion asks for to run it: insert_content, read_content, update_content.
how to start
- limit the access. allow notion read and write for this replacement job.
- read before rewriting. link the page and have the bot inspect its current contents.
- require a dry run. read the proposed removals and additions. tell it to wait before making a backup or replacement.
- inspect both copies. after an approved run, read the new page and backup side by side. pause at any partial failure.
limits worth knowing
- a half-finished rewrite needs inspection. old text can go before all the new text arrives. stop, look at what remains and avoid a blind retry.
- keeping old children adds alongside them. turn off archiving only when that is the result you want.
the details it works from
| input | required | what it is |
|---|---|---|
page_id | yes | The unique identifier (UUID) of the page whose content will be replaced. |
new_children | yes | Array of block objects to append to the page after clearing existing content. |
dry_run | no | If True, returns what would be deleted and appended without making any changes. |
backup_parent | no | Parent specification for backup page creation. |
create_backup | no | Whether to create a backup page with the current content before replacing it. |
backup_title_suffix | no | Suffix to append to the original page title when creating a backup page. |
from composio's catalog for Notion (action NOTION_REPLACE_PAGE_CONTENT, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- link one simple notion page
- give the replacement text from a file
- request a dry run only
- read the proposed removals and what the backup leaves out
quick checklist
- the right page is open
- the preview shows the intended removals and additions
- nested content will not disappear unnoticed
- i understand the backup limits
- partial failure means stop and inspect
mistakes people make
treating backup as a full restore
inspect nested content and unsupported blocks first.
retrying a half-finished replacement
open the page and identify what remains before another write.
questions
can i see what would change without rewriting the page?
yes. ask for a dry run. it previews removals and additions while leaving the page alone.
does a backup guarantee a full restore?
a backup covers only the content this action can copy. unsupported blocks and nested content need another plan. leave a complex page alone if losing those parts would break it.
sources
read next
add a batch of notes to an existing notion pageadd the notes where they belong.
give new notion notes a proper homenew notes, under the parent you chose.
a notion bot that keeps the next step easy to findclearer notes, with a smaller edit scope.
leave a useful notion comment where it belongsa review note in its intended discussion.
turn a clear request into a notion database rowyour notes, in the right database fields.
put a notion page under its new parentmove the page, with a clear destination.
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].