Google Drive Make integrationAutomate Google Drive with Make.

Finds files or folders that match your criteria, like a name or a location, and returns them to the next module. It answers the question "does this already exist?" before your scenario creates a duplicate.

Pulls the actual content of a Drive file into the scenario, so another app can receive the file itself rather than a link. Think of it as the bridge between a Drive document and an email attachment or an upload elsewhere.

Turns plain text built in your scenario into a new file saved in Drive. You assemble the content from earlier modules (a form answer, a summary, a log line) and Make writes it as a document in the folder you pick.

Opens a new folder where you tell it to, with a name that can come from any earlier data. Your folder structure then follows one naming rule, whoever triggers it.

Places a shortcut to an existing file or folder somewhere else in Drive, without making a copy. The original stays in one place, and people find it from several folders.

Sends a file coming from another module into a Drive folder. It is the module that archives attachments, exports and downloads from your other tools, the most common destination in a Drive scenario.

Changes an existing file, either its details such as the name, or its content, or both. The file stays where it is, which matters when others already work from it.

Gives an existing folder a new name. Small action, but it keeps your structure readable when a status changes and the folder name should say so.

Sends a file or a folder to the Drive trash, where it can still be restored. It is the careful way to clean up, with a safety net if the scenario picked the wrong item.

Erases a file or folder for good, skipping the trash. It only works on items that the connected user owns, so shared files owned by someone else stay untouched.

Duplicates an existing file, which makes it the natural tool for templates: one master document, one fresh copy per case. The original is never touched.

Relocates a file or folder to another place in Drive. Paired with a trigger, it sorts a messy inbox folder into the right subfolders without anyone dragging files around.

Returns a link to a file or folder that you can pass to any other app. Your scenario can then send the link by email, post it in chat or store it next to a record in your CRM.

Adjusts the access someone already has on a file or folder, for example turning an editor into a viewer. It lets permissions follow the life of a project instead of staying as they were on day one.

Removes a person's access to a file or folder. Paired with an event from your HR or project tool, it closes doors that people tend to forget to close by hand.

Lists the shared drives of your Google Workspace that match your query. Admins use it to loop through every shared drive and apply the same check or the same update to each one.

Creates a new shared drive, the team space where files belong to the organization rather than to one person. Automating it keeps names consistent across departments or clients.

Fetches the details of one shared drive from its ID, so later modules can use its name and settings. It is a lookup step, not a change.

Changes the settings of an existing shared drive. The documentation marks it as a module for admins only, which fits its role: keeping the organization's team spaces in order.

Removes a shared drive that holds no content. It closes the loop on spaces created for a project or a client that never took off, or that you already emptied.

Returns the history of versions saved for a file, one bundle per revision. It shows who changed a document over time and gives the IDs the other revision modules need.

Retrieves one specific revision of a file, identified by its ID. You reach back to a precise version instead of the current one.

Edits an existing revision of a file. It is a niche module for teams that manage version history carefully, such as legal or quality documents that must keep an exact trace.

Removes one revision from a file's history while keeping the file itself. It helps when an old version should no longer be reachable, for example a draft with outdated figures.

Converts a readable folder path into the folder ID that other modules expect. Your scenario can then work with paths such as /Clients/2026 instead of IDs nobody remembers.

Does the reverse trip: from an ID, it gives back the full path of a file or folder. Handy for messages and logs that humans read.

Calls any endpoint of the Google Drive API with the connection you already set up. It covers what the ready modules leave out, as long as the API offers it.