dusk botintegrationsgoogle drive
move the exact drive file into its agreed folder
put the signed agreement where the team will look for it. give the bot the google drive file and destination folder.
it removes the old folder placement and adds the new one, leaving one copy. moves skip sending approval, so tell it to show the proposed move and ask before acting.

what it does
give it the file link and the folder link. that's the whole handoff. if you only know the name, ask for candidates first. the action finds the current folder itself.
a drive file lives in one folder at a time. use a shortcut for another placement. shared-drive roles and rules can block a move, even with the right file and destination.
when you would use it
- file a signed agreement in its chosen project folder
- move a finished photography brief out of intake
- return a misfiled document to the folder its owner confirmed
- move a shared-drive file after checking your role and destination
try it
paste this into a chat with your bot
at 11:30 on the last wednesday of each month, inspect my google drive contract intake folder. find signed agreement files added this month. match each to an existing project folder using the project name in its filename. show each file, current folder and proposed destination here.
ask me before you change anything. move only the files i approve, then return their new folder links. leave unclear matches alone. never rename, delete or copy files. stop if shared-drive rules block a move.- when
- last wednesday of the month at 11:30
- needs
- google drive with read and write; allow file lookups and moves only
what comes back looks like this (an example)
move proposal
- lucy, windlass studio: signed agreement
- from: contract intake
- to: windlass studio signed agreements
move this agreement to the project folder?set it up
- connect google drive. allow read and write for moves and the lookups they need.
- give the file and destination links. ask the bot to show the current folder.
- review the proposed move before agreeing. sending settings do not cover folder moves.
- open the new folder after your first move. Pause the routine when destination names need work.
what it needs from you
| input | required | what it is |
|---|---|---|
file_id | yes | The ID of the file to move. |
add_parents | no | The ID of the single destination folder (e.g., '1FmTIJYwTENUDXOKyNJp7OmcRBvP_6DmT'). |
ocr_language | no | A language hint for OCR processing during image import (ISO 639-1 code). |
include_labels | no | A comma-separated list of IDs of labels to include in the `labelInfo` part of the response. |
remove_parents | no | A comma-separated list of current parent folder IDs to remove. |
supports_all_drives | no | Whether the request supports both My Drive and shared drives. |
from composio's catalog for Google Drive (action GOOGLEDRIVE_MOVE_FILE, read 12 november 20264). your bot fills these in from what you tell it.
how dusk bot handles it
dusk bot counts Move File as a change: it alters something in Google Drive, and the sending setting does not cover it. a bot you allow only to read can never call it.
the permissions Google Drive asks for to run it: drive, drive.file, drive.appdata, drive.metadata.
where it stops
- a move leaves one folder placement. use a shortcut if people need to find the file in two folders.
- shared drives have their own rules. your role there decides which moves you can make.
- keep own-drive folders out of shared-drive moves. drive cannot move a folder from your own drive into a shared drive. stop rather than retry.
try it in 2 minutes
- give the bot one file link and one destination folder link
- ask it to show the current folder and proposed move
- agree to that move, then open the new folder
quick checklist
- the file link points to the signed copy
- the project folder already exists and matches
- the move has your agreement
- the saved location matches the proposal
mistakes people make
moving the first file with a matching name
compare the file link and current folder before choosing.
expecting a move to leave a copy behind
ask for a shortcut when two folders need an entry.
questions
do i have to tell it which folder to remove the file from?
no. give the destination. the action checks and removes the old folder placement itself.
can it keep the same file in both folders?
use a shortcut for that. a drive file has one parent folder. moving replaces that placement.
will the move wait for an approval card?
put the ask-first step in your instruction. file moves sit outside sending approval. the routine above asks before moving.
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].
a google drive assistant that finds the right file
find a drive file from more than its filename
put a new google drive folder in the right place
claude connectors: connect the job you actually need
give a named person google drive access with ai
get a portable copy of a google workspace file