dusk botput a notion page under its new parent
put the finished brief where your team will look for it. a bot moves an existing notion page under another page or into a database, keeping its contents intact.
give it the source link and destination link. you get the original page in its new home, without a second copy to keep in sync.
move page, in plain words
two pages called archive are a good reason to paste the link. links settle which page moves and where it belongs. the bot can search notion by name to find candidates.
a database destination works differently from a parent page. say which you mean. the move changes the page’s home and leaves the writing alone.
a routine to copy
paste this into a chat with your bot
on the first friday of each month at 13:45, read event briefs under the events page i linked. find briefs whose event date has passed.
- show each source link and proposed destination under the linked archive
- ask me before you change anything
- move only the pages i choose
never move a database or rewrite a brief. never choose a destination from its title alone.- when
- first friday of the month at 13:45
- needs
- notion connected with read and write; access to source pages and the destination
what comes back looks like this (an example)
event briefs proposed for archive
rookhaven winter fair brief: event date passed
from: events
to: events archive / winter fairs
proposed move: this brief only, to the winter fairs archive.good jobs for it
- file a finished event brief. move it under the right annual archive.
- bring a stray note home. place it in the agreed project database.
- repair the handbook’s structure. move the onboarding page without rewriting it.
before it runs
dusk bot counts Move 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.
the permissions Notion asks for to run it: update_content.
how to start
- allow a move deliberately. connect notion with read and write for this bot.
- give both links. say whether the destination is a page or database.
- approve the route. ask the bot to show source and destination links before it moves the page.
- open its new home. confirm the first brief is there. pause the routine when monthly filing is finished.
limits worth knowing
- database moves need a database destination. tell the bot if it treated one as a page.
- use links to tell copies apart. open the source and destination before approving the route.
- make the bot wait for your go-ahead. moves use write access and bypass the email sending setting. the routine above adds the pause.
the details it works from
| input | required | what it is |
|---|---|---|
parent | yes | Parent destination for the page. |
page_id | yes | The ID of the page to move. |
from composio's catalog for Notion (action NOTION_MOVE_PAGE, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- copy the source page link
- copy the destination link and say page or database
- ask for a move preview without changing anything
- open both links before allowing the move
what it looks like
invented example: felix files a finished event brief.
before
the winter fair brief sits under events. two other pages also have "archive" in their names.after the bot
felix gives the exact archive link. the bot shows the source and destination, waits, then moves only that brief.an illustration with made-up names and numbers.
mistakes people make
giving only the word "archive"
paste the destination link so the bot can distinguish copies.
expecting send approval to stop a move
require your go-ahead in the move request. sending approval covers a different action.
questions
can it move a page into a database?
yes, give the database link. the bot must use that database’s destination rather than treat it as a parent page.
does moving also rewrite the contents?
no, this action relocates the page. ask for any rewrite as a separate job.
sources
read next
turn a clear request into a notion database rowyour notes, in the right database fields.
a notion bot that keeps the next step easy to findclearer notes, with a smaller edit scope.
add a batch of notes to an existing notion pageadd the notes where they belong.
leave a useful notion comment where it belongsa review note in its intended discussion.
give new notion notes a proper homenew notes, under the parent you chose.
ask for the notion records that match your conditionsthe matching rows, with their criteria clear.
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].