dusk bot
integrationsmiro

dusk botintegrations

take the decisions out of a miro workshop frame

recover what the workshop decided while the sticky notes still make sense. give a miro bot in dusk the board and frame that hold the agreed actions.

by the dusk bot team · checked · how we made this

it can read the notes, follow their tags and trace connectors between items. ask for the original item ids beside each finding so the facilitator can return to the board.

pixel art: a lime pixel bot, a green pixel bot and a pink pixel bot beside a tile saying Miro and a folded map, on a sandy path in front of white cliffs with a waterfall, one saying "follow the arrows"

what a bot can do in Miro

use frame membership to set the boundary. a busy board can hold last month’s workshop next to today’s. give the bot a frame id to collect its child items. use board-wide reads only when the question genuinely spans frames.

actiondusk bot treats it aswhat you would use it for
Get Board Itemsreadlocate the named frames and page through board items
Get Items Within Framereadread the items that actually belong to the decision frame
Get Sticky Note Itemreadrecover the exact wording from a workshop note
Get Item Tagsreaddistinguish a research quote from an interpretation using your tags
Get Connectorsreadfind the arrows on a process map
Get Specific Itemreadread the item at either end of an arrow
Share Boardsend: asks firstinvite a recipient to the board with the role you chose

composio, the connection service behind dusk bot's apps, lists 89 Miro actions (version 20261113_00, read 20 november 20264). dusk bot treats 33 as reads, 1 as sends and 55 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 share board, and waits for your Allow unless you set a daily amount.

connect Miro

  1. open Connected apps in the sidebar.
  2. pick Miro and sign in on Miro's own page, so your password goes to them and never to a bot.
  3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Miro.
  4. ask in plain words. reading and drafting happen freely; sending asks you first.

choose a finished frame that the facilitator recognizes. connect miro, allow your workshop bot to read it and give it the board id. ask it to list the frame names and ids. pick the decision frame and define the tags your team uses there.

routines to copy

preserve a trail back to the board. a tidy summary loses its value if nobody can find the note it came from. each prompt keeps an item id, a frame or a pair of endpoints.

decisions after the workshop

every thursday at 4, read the stickies inside our decisions frame on the workshop board. separate agreed actions from questions using our tags. copy any owner and due date written on each action. return the sticky ids here. flag decisions without owners. leave the layout alone.

thursdays at 4 pm · actions and open questions from the decision frame

interview evidence

every friday at noon, collect stickies tagged customer quote in our research frame. group them by the problem described. retain the exact wording and item id for one example per group. put interpretations with no customer quote aside. give me the groups here.

fridays at noon · research themes grounded in the tagged quotes

arrows across a handoff

each monday at 2, read the connectors on our order process board. follow arrows between items in the sales and fulfillment frames. list the label at each end here. flag any endpoint you cannot identify. do not infer a handoff just because two shapes sit close together.

mondays at 2 pm · handoffs with their source and destination items

what it asks you first

keep the board private while preparing the recap. sharing a board sends an email invitation and asks first by default. choose the recipient and role before approving. moving a sticky or changing its text is a write. read-only access keeps those actions out of a workshop review.

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

  • find a sticky in a frame by appearance alone. the frame lookup returns items nested under that frame id. a nearby note may belong elsewhere.
  • create a connector that ends in empty space. the create action needs an existing item at both ends.
  • start a recap from a miro board event through this connector. schedule it for the end of the workshop or ask for it in chat.

when to go back to the canvas

keep spatial disagreements on the board. if the facilitator appears to have moved an idea between groups, look at the canvas together. the bot is useful for collecting labeled choices and tracing actual arrows. it is the wrong pick for deciding what an unlabeled gap meant to the room.

what it looks like

a fictional example.

before

edith shaw keeps a sticky about a packaging trial near the decisions frame. the actual decision inside the frame names a smaller sample run.

after the bot

agreed action: prepare the sample run. the nearby packaging idea is outside the decision frame. leave it out of the commitments.

an illustration with made-up names and numbers.

questions

will collecting the workshop notes move our stickies?

grant the bot only the read actions. the action list and research themes come back in dusk. the facilitator keeps the arrangement everyone saw.

can a miro ai assistant tell who owns an action?

use the name written on the sticky or a tag your team defined. the person who typed a note might have been taking minutes. leave ownership open when nobody accepted the work.

sources

  1. dusk bot docs: files and apps
  2. dusk bot docs: routines
  3. dusk bot docs: sending permissions
  4. composio, Miro toolkit (catalog version 20261113_00), checked 20 november 2026

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].