dusk bot
integrationsdropbox

dusk botintegrations

a dropbox bot for files that arrive out of order

a folder full of final files still leaves someone guessing which one to deliver. point a dusk bot at your dropbox intake folder.

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

give it the client folder names and ask for proposed moves in chat. it can also look up a file's revisions or pull the deadline from an open file request.

pixel art: a blue pixel bot, a cyan pixel bot and a mint pixel bot beside the dropbox mark on a white tile and a folder of papers, on a lilac hill in front of sand dunes by the sea, one saying "where does this go"

what a bot can do in Dropbox

use the whole path to identify the file. two clients can submit a file with the same name. listing the folder gives you each location. reading revisions answers a different question about what happened to one file.

actiondusk bot treats it aswhat you would use it for
List files in folderreadinventory the files immediately inside the intake folder
List folder continuereadfinish the inventory when dropbox returns another page
Get file or folder metadatareadconfirm that a proposed destination path points to a folder
List file revisionsreadinspect earlier versions under one delivery path
List file requestsreadfind requests owned by the connected account
Get file request detailsreadread the status and deadline on one request
Move file or folderchangemove the chosen file to the exact approved destination

composio, the connection service behind dusk bot's apps, lists 178 Dropbox actions (version 20261116_00, read 20 november 20263). dusk bot treats 93 as reads, 2 as sends and 83 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 send team member welcome email, and waits for your Allow unless you set a daily amount.

connect Dropbox

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

give it a real folder path and a filing rule. name the intake folder, destination folders and how your filenames identify a client. start with the listing actions. review one proposed move against the actual file before enabling moves.

routines to copy

decide what counts as evidence for filing. a client code at the start of a filename can be enough. a familiar first name usually isn't. for the revision routine, give the bot a specific delivery path.

sort the intake tray

every weekday at noon, list the files directly inside my intake folder. continue to the end of the listing. match the client prefix to my destination list. give me source and destination paths in chat. set aside unknown prefixes and existing destination names. ask me before you change anything.

weekdays at 12:00 · a move list with ambiguous files held aside

which revision did we deliver

every friday at 3, read the revision history for <delivery file path>. list revisions from this week with their ids and times. mark the newest one returned. if there were no changes, give me one line. don't restore any files.

fridays at 15:00 · a dated record for one delivery file

requests near their deadline

each monday at 9, list my open dropbox file requests. look up the deadlines. bring me the requests due this week, earliest first, with the destination folder. put requests without a deadline in a separate count. leave every request open.

mondays at 09:00 · an intake calendar for the person collecting assets

what it asks you first

approve the path pair before allowing a move. dropbox moves change files without a sending prompt. a read-only bot can prepare the filing plan. if you enable moves, keep the ask-first line and review each collision. renaming a file to make it fit can hide a second submission.

what it cannot do

  • see the entire intake from the first results alone. when dropbox offers a continuation cursor, more entries remain.
  • identify the chosen design from a revision timestamp. the history tells you which file changed last. your approval record tells you which version the client accepted.
  • list another person's requests as yours. the request listing covers the connected user's own requests. choose the account that collected the files.

when the filenames give you nothing

sort unmarked submissions with the person who received them. if the same artwork appears under several names, the bot needs a delivery rule or an approval record. for a single disputed proof, opening the artwork with the client is the shorter job.

what it looks like

an example from a studio intake.

before

veronica receives maple-cover.pdf and cover-final.pdf in the same intake folder. only the first has a known client prefix.

after the bot

maple-cover.pdf → maple/artwork/maple-cover.pdf
cover-final.pdf → hold. which client sent this cover?

an illustration with made-up names and numbers.

questions

can the bot sort dropbox without moving anything?

yes. let it list folders and read metadata. get a proposed source and destination for each file. unknown clients stay in the intake report.

can i ask for previous versions of a whole folder?

choose the file first. the revision action takes a file path. list the folder to find its contents, then inspect the specific delivery.

sources

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