dusk bot
integrationstrello

dusk botintegrations

a trello bot that spots unfinished handoffs

**the card reached the print queue.

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

did the proof get there too?** a trello bot can read a production board and flag jobs with missing attachments, unfinished steps or overdue dates. give it the lists your crew actually uses. get the card link and the question to ask before the next shift.

pixel art: a pink pixel bot and a blue pixel bot beside the trello mark on a white tile and a signpost, on a sandy path in front of green terraced fields, one saying "ready for print"

what a bot can do in Trello

look inside the card before calling the job late. the list tells you where it sits. the due date, members and last move tell you who can help. an attached proof and a completed signoff are different pieces of evidence.

actiondusk bot treats it aswhat you would use it for
Get board's listsreadmap the current list names to stages on the shop floor
Get cards by board IDreadfind open cards with due dates before this shift
Get card membersreadsee who is on the job when a deadline slips
Get card checklists by IDreadread the proof signoff item on a job in the print queue
Get card attachmentsreadlook for the proof file named in your handoff rule
Get card actions by idreadfind the most recent move into the waiting list

composio, the connection service behind dusk bot's apps, lists 336 Trello actions (version 20261116_01, read 20 november 20263). dusk bot treats 150 as reads, 2 as sends and 184 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 delete org invite restriction, and waits for your Allow unless you set a daily amount.

connect Trello

  1. open Connected apps in the sidebar.
  2. pick Trello and sign in on Trello'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 Trello.
  4. ask in plain words. reading and drafting happen freely; sending asks you first.

pick the board by its link. a copy from last season can have exactly the same list names. give the bot read access. tell it which list means finished, which means waiting, and what your crew calls a signed proof.

routines to copy

start with the shift you run. these messages assume a production board with print and waiting lists. substitute your list names once. the questions then work against the cards that move through them.

overdue at shift change

every weekday at 7, find open cards on my production board with a past due date. skip completed dates and our finished list. put the earliest deadline first. give me the card link, the due date and everyone on the card. put unassigned jobs on their own line.

weekdays at 07:00 · a shift list ordered by missed deadline

proofs for the press

at 2 each weekday, read the cards in ready for print. look for a proof pdf attachment and a completed proof signoff item. bring me the card link and whichever piece is missing. leave the cards in place.

weekdays at 14:00 · print jobs missing a file, a signoff or both

waiting on a decision

every thursday at 3, open each card in waiting. find its last move into that list and the question in its description. list cards waiting over a week here. if the move is missing from history, write date unknown. don't treat an unrelated edit as a fresh move.

thursdays at 15:00 · old questions with the date each job entered waiting

what it asks you first

keep the shift report read only. the bot can tell you which card needs attention without moving it. changing a due date or moving a card is an edit. if you give it either action, write “ask me before you change anything” in that routine.

what it cannot do

  • recover every old card move. trello can omit very old actions. the earliest visible edit might be well after the job arrived.
  • tell who approved a proof from an attachment alone. a file called final can still be awaiting signoff.
  • move a job with these read actions. the report gives the shift lead the link. they decide where the card belongs.

when a glance at the board is enough

skip the bot if the whole answer is on the face of one card. it earns its place when a shift lead must open each card to compare an attachment, a due date and a signoff. name the missing piece so the crew knows what to bring.

what it looks like

an example from a print board.

before

ruben's menu cards sit in ready for print. the proof pdf is attached. the proof signoff item is still open.

after the bot

menu cards | proof attached | signoff missing
ask ruben for signoff before the print run.

an illustration with made-up names and numbers.

questions

does every member on a trello card own the deadline?

the member list shows who's on the card. if your crew names the owner somewhere else, give the bot that rule. leave ownership open when the evidence is missing.

what about jobs with no due date?

give undated work its own queue. ask for cards in the active list with no due date. mixing them with overdue work makes the shift report harder to act on.

sources

  1. dusk bot docs: connected apps
  2. dusk bot docs: routines
  3. composio, Trello toolkit (catalog version 20261116_01), 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].