find the instruction that changed in a confluence runbook
find the instruction that changed before someone follows the old runbook on call. a confluence bot can read page versions, open inline comments and tasks from the space you choose.
ask it for the old instruction and its replacement in dusk chat. keep the page id and version numbers beside the answer.

what a bot can do in Confluence
use a stable page id for a recurring review. a title search helps you find the right runbook the first time. the version history then tells you which revisions to open. changes to the instructions matter more than a new version number alone.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| Search Pages | read | locate the runbook by title inside its space |
| Get Page Versions | read | find the revisions on either side of a handoff |
| Get Page by ID | read | read the available page body at a particular version |
| Get Child Pages | read | list the procedures directly under a handbook page |
| Get Page Inline Comments | read | read unresolved questions attached to the procedure |
| Get Tasks | read | gather unfinished action items from a page or space |
| Create Inline Comment | send: asks first | ask the owner a reviewed question on the selected passage |
composio, the connection service behind dusk bot's apps, lists 75 Confluence actions (version 20261116_01, read 20 november 20264). dusk bot treats 42 as reads, 2 as sends and 31 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like create footer comment, and waits for your Allow unless you set a daily amount.
connect Confluence
- open Connected apps in the sidebar.
- pick Confluence and sign in on Confluence's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Confluence.
- ask in plain words. reading and drafting happen freely; sending asks you first.
give the bot the space and one runbook title. connect confluence, grant reading access and ask which matching page you mean. open the result once to confirm its id. put that id in the bot’s job so later reviews follow the same document.
routines to copy
choose the part of the handbook your team uses under pressure. these prompts look for a changed instruction, an outstanding question or an unfinished task. each gives the reader a place to act.
what changed for the on-call shift
every monday at 8, read the version history of our on-call runbook. compare the current body with the version in use a week ago. quote changed operational steps here with both version numbers. skip spelling changes. if either body is missing, name the version you could not read.mondays at 8 am · old and new steps for the shift lead
questions in the procedure margins
each wednesday at noon, list the direct child pages under our support handbook. read unresolved inline comments on those pages. collect questions about missing steps. give me the page title, question and surrounding instruction where available. leave all comments open.wednesdays at noon · editorial questions tied to individual procedures
unfinished meeting actions
at 3 each friday, list incomplete confluence tasks on our weekly operations notes page. group them by named assignee here. put unassigned tasks in their own group. include the task wording and page id. never mark anything complete.fridays at 3 pm · open actions to bring back to the meeting
what it asks you first
choose between a question in dusk and a comment on the shared page. creating an inline comment asks first by default. editing the runbook body is a write and can go ahead without a prompt. keep review access read only or add “ask me before you change anything” to an editing routine.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
what it cannot do
- get a full page tree in one child-page call. it lists direct children. to include another level, use each child as the next parent.
- compare two versions when one body is missing. page metadata alone shows a revision exists. it cannot tell the reader what an instruction used to say.
- anchor a new inline comment to a title alone. a top-level comment needs the text selection on the page.
who decides which instruction is correct
take disputed instructions to the runbook owner. give them the two passages and the revision numbers. a newer edit can still be wrong. if you need to decide whether a recovery step is safe during an incident, ask the person running the response.
what it looks like
a fictional example.
before
marion reed takes the weekend shift. two versions of the restart procedure use different names for the queue to drain.after the bot
version 8 says “drain intake.” version 9 says “drain dispatch.” ask the runbook owner which queue is correct before using the new step.an illustration with made-up names and numbers.
questions
can i look up a page without knowing its id?
start with the title and space. page search can return several matches. compare titles and space details before saving the id for regular reviews.
can i see open tasks without giving the bot edit permission?
use the task list action with read-only access. narrow it by page, space or assignee. results can span several pages, so ask for the complete list.
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].
a jira bot that shows what changed in your sprint
find the decision halfway down a teams thread
a notion bot that keeps the next step easy to find
add new airtable rows without rewriting existing records
turn your notes into a comment on the right asana task
ask what an asana task actually says