a google drive assistant that finds the right file

what a bot can do in Google Drive

give the bot a folder or a file description, then ask it to return evidence you can recognise: name, folder and last-changed date. a file with the newest date is only a candidate for the current version until your naming or approval rule confirms it.

composio, the connection service dusk bot uses for apps, lists 105 Google Drive actions (catalog version 20261104_00, read 12 november 2026⁴). dusk bot treats 44 of them as reads, 4 as sends and the other 57 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like create comment: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Google Drive

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

connect the google account that holds the files, then tell the bot the folder or file to start from. work and personal accounts can have separate labels, with up to five accounts per app. use the label in your request so a search stays in the intended account. begin with read-only permission.

routines to copy

each routine narrows the search before drawing a conclusion. tell the bot which folder belongs to the job and what your team considers an approved file. the result should make a decision easier, not quietly reorganise drive.

every monday at 8, find candidate files for this week's steering meeting in the drive folder i named. return names and available modification details. use my approved-file naming rule and flag ambiguity rather than choosing silently. do not move or rename files.

each thursday at 11, inspect the returned permissions for the drive files in the handover list i supplied. compare them with the access list we agreed. show differences and failed lookups without changing permissions or creating share links.

every friday at 2, find the files in our intake folder that match the naming rules i gave you. propose destination folders and list anything ambiguous. do not create folders or move files; bring the plan here for my review.

what it asks you first

file searches and permission reviews can stay read only. that permission blocks folder creation, moves and sharing changes before they reach google drive. a filing proposal in your chat does not require access to perform the moves.

if you enable file moves later, write "ask me before you change anything" into the routine. moving a file or changing its sharing is not documented as asking first automatically. comments and replies on files count as sends and follow your sending setting (a bot on Full access with no sending rule may send up to 25 a day without asking, so set Ask every time for it). moving files and changing sharing don't ask.³ use a precise action allowance for a bot that only needs one kind of change.

read and write access also lets a bot delete files, empty the trash or share a file with anyone, without asking. for filing work, give it an exact action list with only Move File and Create a folder.

what it cannot do

• treat read permission as permission to move, rename or share files. the first reviews here are intended to run without those capabilities.
• export a google doc, sheet or slide while read only. dusk counts that export as a change, so allow just that one action if you need it.
• assume a found file is the approved one just because its title or date looks right. require your approval rule and return ambiguous candidates for you to choose.
• run an unattended filing review when your own computer sleeps or dusk bot is closed. dusk cloud can keep scheduled work running while the local computer is off.

find first, organise second

begin with a list of candidates and ask what would happen to each file. use a naming rule you can read, such as which folder receives signed documents. unknown cases should stay in the review list. see file organisation for a broader routine.

if the job is about rows and formulas rather than file location, use the separate google sheets integration. for cell edits, use the dedicated sheets connection; drive also has spreadsheet-value actions, so keep those off a filing bot's action list.

explain what current means

tell the bot how you mark a document ready for use: a specific folder, a naming rule, or a list you provide. revisions and modification details can help investigate a file, but neither proves a document was approved. ask the bot to preserve that distinction in every meeting packet review.