spot the monday.com item marked ready too soon
catch the deliverable marked ready while the proof underneath it still needs approval. a monday.com bot can read parent items, subitem columns and update replies.
ask it to bring the mismatch into dusk chat with the item id. the board owner can then ask for a signoff or correct the status.

what a bot can do in monday.com
work from the board’s actual labels. give the bot the board id, status column and the label your team uses for a handoff. a different board can use the same word for a different stage of work.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| List groups | read | locate the delivery group and distinguish it from archived groups |
| List items by column values | read | find parent items carrying the exact handoff label |
| Get items by IDs | read | confirm the names and groups for a set of item ids |
| List subitems by parent | read | read child status values beneath each matching parent |
| Get item updates | read | open the conversation on a deliverable |
| Get update replies | read | look for a signoff underneath the original update |
| Change simple column value | change | apply an agreed status using a label already on the board |
composio, the connection service behind dusk bot's apps, lists 126 Monday actions (version 20261101_00, read 20 november 20263). dusk bot treats 29 as reads, 1 as sends and 96 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 publish object, and waits for your Allow unless you set a daily amount.
connect monday.com
- open Connected apps in the sidebar.
- pick monday.com and sign in on monday.com'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 monday.com.
- ask in plain words. reading and drafting happen freely; sending asks you first.
choose a real deliverable with at least one subitem. connect monday.com and let your operations bot read it. give the bot the board id and item id. tell it which subitem stands for final signoff and what the finished label says.
routines to copy
run these before someone hands work to the client. put your board’s group and label names in the bot’s job. the same prompts then work each week without guessing which board you meant.
ready parents with unfinished work
at 2 every weekday, find items marked ready for delivery on our client board. read their subitems with status values. list each ready parent with an unfinished required subitem. show both ids here. if a required value is blank, flag it as missing.weekdays at 2 pm · parent and child items that disagree about readiness
proof signoffs
each thursday at 11, find items marked awaiting signoff on our client board. read their updates and replies. pick out approvals that name a proof version. give me the item id, version and exact approval wording. list unclear versions separately. do not change status.thursdays at 11 am · proof approvals tied to the version the client reviewed
handoff details for production
each friday at 1, read items marked ready for production in our delivery group. pull the requested quantity and delivery address from their update threads. flag conflicting instructions with the item id. return the packing notes here and leave missing details blank.fridays at 1 pm · packing notes with conflicts for the production lead
what it asks you first
a status edit can change the board without asking. use read only for these routines. if you later enable a column edit, add “ask me before you change anything” to the job. have it show the item, column and existing label before it writes.
what it cannot do
- look up subitems by a board-wide status search alone. the subitem action needs parent item ids. select the parents first.
- use a simple column edit for every field. that action handles text, status and dropdown values. people and timeline fields need the item update action.
- rely on the status editor to reject a typo. the simple column action can create missing labels by default. turn label creation off when using an existing label.
what counts as a signoff
ask the bot to find the version number next to the approval. a client may love the first proof and request a correction to the next one. if your only task is moving a label on an item you already reviewed, do it on the board.
what it looks like
a fictional example.
before
louis ford marks a print job ready. the proof subitem still says waiting for signoff. the latest reply approves version one.after the bot
hold for proof review. the delivery item says ready, but approval names version one. confirm which version will go to print.an illustration with made-up names and numbers.
questions
what if two groups have the same name?
use the group id and board id. the group list includes ids and archive status. confirm which group still holds active work.
can the bot leave our board exactly as it found it?
give it access only to the reading actions. the mismatch list and production notes can both stay in dusk. nobody has to undo an automatic status change.
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].
prepare a client onboarding brief before kickoff
an asana assistant for the work between tasks
take the decisions out of a miro workshop frame
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