Google Drive folders that file and share themselves
Upload, copy, move, share and search Google Drive files from a workflow, react to new files in a folder, and gate deletes behind an approval. One click.
- Category
- Productivity
- Connect
- Connect with one click (OAuth) · managing connections
- Operations
- 9
- Triggers
- none yet
Google Drive is the filing cabinet, and MadMax makes it one that files itself. A workflow can find files with a Drive query (name contains 'report', '<folder id>' in parents), pull one down, build a folder tree for a new client, copy templates into it, share it with the right people, and move or delete what has gone stale, with an approval in front of the share or the delete when a person should decide. There are no Drive push events, so "new file in a folder" is the watch trigger polling list with a folder query and firing once per unseen file id, baselining what is already there first. For reading document contents with AI, the file upload trigger plus an extract task is the documented path, and Drive is where the file gets filed afterwards. Describe it in plain English and MadMax builds the workflow, runs it on a real document, and previews every upload, move and share before anything in your Drive changes.
What teams build
- A hosted file upload page receives an invoice, an AI extract step pulls vendor, invoice number, total and due date with confidences, a store upsert keeps a row per invoice, and
uploadputs the PDF in the Processed folder named<vendor>-<number>.pdf. - A form collects a new client's name and contact email, the run calls
create_folder, copies the proposal and kickoff templates into it withcopy, andsharegrants the contact reader access before a send email step sends the welcome note with the folder link. - A watch trigger polls
'<Contracts folder id>' in parentsevery 15 minutes, an approval emails legal the file name and link with one-click approve or reject, and on approve the file is shared with the finance group and moved to Approved while a reject moves it to Rejected.
How it connects
One click. Press Connect on the Google Drive card in Settings → connectors and approve the Drive permission on Google's consent screen. MadMax stores the grant encrypted, refreshes the access token before it lapses, and never displays it again; a revoked grant shows a reconnect button that re-authorizes the same connection, so no step needs rewiring. Connections are per workspace, private to you or shared with the team, and each Drive step picks which account it uses. See managing connections.
Related
Every Google Drive operation MadMax can run
Straight from the integration's manifest, so this list is what the steps on the canvas can actually do today.
| Operation | What it does |
|---|---|
| copy | Copy a file. Optionally rename it and place it in `parents`. |
| create folder | Create a folder. `parents` is an optional JSON array of parent folder ids. |
| delete | Permanently delete a file or folder by id. |
| download | Download a file's contents. Returns base64-encoded bytes plus the content type. |
| get | Fetch a file's metadata (id, name, type, size, link). |
| list | Search/list files with a Drive query (e.g. `name contains 'report'`). Returns matching files. |
| move | Move a file between folders. Provide both add_parents and remove_parents (JSON arrays). |
| share | Grant a permission on a file (e.g. give a user reader/writer access). |
| upload | Upload a file. `parents` is an optional JSON array of folder ids; omit for My Drive root. |
Works with
Describe the workflow. MadMax builds it and tests it on your data.
Free to start, no card. Connect your apps, say what should happen in plain English, and watch each step run against real data before anything goes live.