Resources · Zapier integration

Google Drive Zapier integrationAutomate Google Drive with Zapier.

The Google Drive Zapier integration gives you 26 operations in the editor: 5 triggers, 17 actions and 4 searches. This page says what each one does, what it costs in tasks, and what breaks, before you open Zapier for the first time.

See the 26 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Google Drive Zapier integration actually does

It means Zapier can watch your Drive and act on it without you. You pick the event that starts things off, you pick what happens next, and the editor does the wiring between the two. Nothing gets installed inside Drive, nothing is written in code. You get 26 ready-made operations and you assemble them.

Three things people build with it. An intake folder that empties itself: New File in Folder (Realtime) catches the file, Move File puts it where it belongs, and nobody drags anything. A client space that builds itself: New Folder starts it off, Create Folder adds the subfolders, Create File From Text drops the starting note inside. A document ready to hand over: Export File turns a Doc into a PDF, Add File Sharing Preference gives back the link to send.

Now what it will not do. A Zap only reacts to what happens after you switch it on, so the files already sitting in that folder stay exactly where they are, and shifting the backlog is a separate job. Export File works on Google Docs, Sheets and Slides, not on whatever you happened to upload last week. And none of the 26 operations edits the inside of an existing document: Replace File swaps the whole file, which is not the same thing at all.

The same folder work runs on other editors. The Google Drive n8n integration covers the same ground, and Make vs Zapier puts the two side by side on price and on shape.

Vocabulary

Zapier in eight words

Eight words come back on every screen of the editor. One line each, and we never explain them again.

Zap
The automation itself: one trigger, then the actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits there and waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you.
Task
The unit Zapier bills. One action your Zap completes successfully is one task, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval, keeping only what it has not seen.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What it really costs in tasks

The trigger is free. However often Zapier goes and looks, and whatever it brings back, nothing is counted until an action goes through. The grid below is that looking rhythm, plan by plan, and an instant trigger never waits for it.

  • Trigger0 tasks, however often Zapier checks
  • Action that works1 task each
  • Action that fails0 tasks
  • Free plan100 tasks a month, unlimited Zaps, two steps per Zap
  • Filter or search stepmakes the Zap multi-step, paid plan

Each action that completes counts as one task, and each counts on its own: the same file moved, renamed and shared eats three, not one. An action that fails is not counted. The free plan gives 100 tasks a month and as many Zaps as you like, but each Zap is two steps, one trigger and one action. Add a second action, a filter or a search step and you have a multi-step Zap, which needs a paid plan. A few apps and a few actions count more than one task when they finish.

Connect

Connect your Google account once

  1. 01

    Open the connections page

    From your Zapier account, open Apps and click + Add connection. This is where every app you plug in lives, and a connection made here is reused by every Zap step that needs Drive.

  2. 02

    Pick Google Drive

    Type the name in the dialog that opens, pick Google Drive in the list, then click Add connection. A Google tab opens on top of Zapier, which is normal.

  3. 03

    Sign in and allow access

    Sign in to the Google account that holds the files, then grant Zapier access to it. Back in the editor, the connection is listed and ready for any step. One Google account with Drive on it is all this integration asks for.

First Zap

Your first Google Drive Zap

GoalEvery signed document dropped in the intake folder lands in the client folder, with a sharing link ready to send.

  1. 01

    Start the Zap

    In the editor, pick Google Drive as the app that starts things off, then New File in Folder (Realtime) as the event. The first card of a Zap is always a trigger, never an action.

  2. 02

    Set the trigger

    Choose the connection you just made, then the folder to watch. Test it: Zapier brings back the three most recent files of that account, so the rest of the Zap gets mapped against a real one.

  3. 03

    Add the move

    Add a step, Google Drive again, Move File. In the file field, take the file the trigger sent, then choose the folder it should end up in. Test it and go look: the file has moved.

  4. 04

    Add the sharing link

    A third card, Add File Sharing Preference, on the same file, and you choose who it opens for. Two actions make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back before moving on. When the three cards answer properly, hit Publish. From that second on, and only from then, new files get picked up.

Triggers

The 5 triggers, one by one

5 events start a Zap when something happens in Google Drive, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New File

Polling trigger

In Zapier“Triggers when any new file is added (inside of any folder).”

The widest of the five: any new file added to your Drive starts the Zap, whatever folder it lands in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when the files you care about are scattered and you would rather sort them out inside the Zap than watch one folder.
Watch out
everything means everything, so a Zap built on it fires on files you never meant to touch, and every action it runs costs a task.
2

New File in Folder

Polling trigger

In Zapier“Triggers when a new file is created within, moved to, or uploaded directly to a specific folder. You can optionally include files from its subfolders.”

Same idea, narrowed to one folder: a file created in it, moved into it or uploaded straight to it sets the Zap off. A setting decides whether the folders inside it count too.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
for an intake folder people drop things into, when the rest of the Drive should stay out of it.
Watch out
leave the subfolder setting off and a file dropped one level down goes unnoticed.
3

New File in Folder (Realtime)

Instant trigger

In Zapier“Triggers when a file is added to a chosen folder or shared drive.”

The realtime version of that same watch: a file added to a folder you choose, or to a shared drive, and the Zap is off. Of the five triggers here it is the only instant one, which is the most useful thing on this page: it reacts straight away even on a free plan, where the other four wait for the next check.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
whenever waiting is the problem, a document someone is expecting, a photo to publish.
Watch out
the subfolder setting applies to a folder you pick; a shared drive already carries its own.
4

New Folder

Polling trigger

In Zapier“Triggers when a new folder is added directly to a specific folder (but not its subfolders).”

This one watches folders, not files. A folder created directly inside the one you picked starts the Zap, and a folder created deeper down does not.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a new client, a new case, a new shoot: one folder appears and the Zap builds the whole tree behind it.
Watch out
because it ignores subfolders, a Zap that creates folders inside the new one will not set itself off again.
5

Updated File

Polling trigger

In Zapier“Triggers when a file is updated in a specific folder (but not its subfolders).”

Instead of waiting for something new, it reacts when a file already in the folder changes. Only the folder you pick is watched, not the folders under it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a sheet the team keeps editing, a contract that picks up a signature, anything whose latest state matters more than its arrival.
Watch out
a Zap that writes back into the folder it watches sets itself off again, and again, and burns tasks doing it.
Actions

The 17 actions

Google Drive gives you 17 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Copy File

Action

In Zapier“Create a copy of the specified file.”

Duplicates the file you point it at, by its ID, and can ask Google to turn the copy into an editable document on the way through.

When to use it
to keep the original untouched while the Zap works on the copy, or to hand someone a version they can scribble on.
2

Delete File (Permanent)

Action

In Zapier“Permanently delete a file from Google Drive. This action cannot be undone.”

Deletes a file for good. Not to the bin, not recoverable, and the step makes you tick a confirmation box before it will run at all.

When to use it
on files your own Zap produced and no longer needs, a temporary export, a working copy.
Watch out
there is no undo, and nothing asks you twice once the Zap is live.
3

Export File

Action

In Zapier“Export Google Workspace files (Docs, Sheets, Slides) to different formats like PDF, Word, Excel, etc.”

Takes a Google Workspace file, a Doc, a Sheet or a Slides deck, and produces it in another format, PDF, Word, Excel and so on.

When to use it
whenever what leaves your Drive should not be editable, a quote to send out, a report to archive.
Watch out
it only works on Google Workspace files, and the formats on offer depend on which one you feed it.
4

Upload File

Action

In Zapier“Copies an existing file from another service to Google Drive.”

Takes a file that came from another service further up the Zap and copies it into Drive. The same conversion option is there if you want an editable document out of it.

When to use it
an attachment, an invoice, an export made by an earlier step, this is how it reaches the right folder.
Watch out
several files dropped into that field at once come out as one zip archive.
5

Create Folder

Action

In Zapier“Create a new, empty folder.”

Creates an empty folder under the name you give it, inside the parent you pick.

When to use it
right after a trigger that announces a new client or a new project, to open its space before a single file arrives, and to hand that folder on to the steps that follow.
6

Move File

Action

In Zapier“Move a file from one folder to another.”

Moves a file from one folder to another. The file itself, not a copy of it.

When to use it
the classic second card behind an intake folder: the file arrives, the Zap reads where it should go and files it, and the drop folder stays empty.
7

Create File From Text

Action

In Zapier“Create a new file from plain text.”

Turns plain text into a file in Drive: you give the name and the content, the Zap writes it. An option converts it into an editable document instead of leaving it as text.

When to use it
a brief, a summary, a call note, anything an earlier step produced as text that someone will open in Drive.
8

Remove File Permission

Action

In Zapier“Remove specific user access to a file in Google Drive. Requires either email address or permission ID.”

Takes one person's access to a file away, and wants either their email address or the permission ID to know whose access to cut.

When to use it
the day somebody leaves, or when a document has finished doing its round outside the team.
9

Replace File

Action

In Zapier“Upload a file to Drive, that replaces an existing file.”

Uploads a file over an existing one: the target keeps its place and what came in takes over its content. The conversion option applies here too.

When to use it
for a document whose link is already going around, a price list, a menu, a schedule, where a new file would mean sending a new link.
10

Create Shared Drive

Action

In Zapier“Create a new shared drive (also known as Team Drive) in Google Drive.”

Opens a new shared drive, also called a Team Drive, under the name you pass it: a space the team owns rather than one person.

When to use it
rare, but real, when a new brand or a new department deserves its own drive instead of a folder buried inside yours.
11

Add File Sharing Preference

Action

In Zapier“Adds a sharing scope to the sharing preference of a file. Does not remove existing sharing settings. Provides a sharing URL.”

Adds a sharing scope to a file and hands back a sharing URL. It adds, it never removes: whatever was already shared stays shared.

When to use it
at the end of a Zap that produced a document somebody outside your Drive has to open.
Watch out
sharing with a whole organization is only valid on a G Suite account.
12

Create Shortcut

Action

In Zapier“Create a shortcut to a file.”

Puts a shortcut to a file somewhere else, so the same document shows up in two places without a second copy going off to live its own life.

When to use it
when a file has to be visible to another team without leaving the folder it belongs in.
13

Update File or Folder Metadata

Action

In Zapier“Update file or folder metadata including name, description, starred status, folder color, and custom properties.”

Changes what surrounds a file rather than the file itself: name, description, starred status, folder color, custom properties.

When to use it
to color a client folder, to star what needs a human look, to leave a description saying where the thing came from.
14

Update File/Folder Name

Action

In Zapier“Update the name of a file or folder.”

Renames a file, or a folder when you flip the setting that says so.

When to use it
to force a naming convention the second a file lands, date first, client second, so nobody has to remember it or apply it by hand.
15

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

The escape hatch: it sends a raw request to Google Drive through the connection you already made, for something the other sixteen actions do not cover. A setting decides whether the Zap stops or carries on when Google answers with an error.

When to use it
last resort, and only when you know the request you want.
Watch out
requests only go to domains tied to this app.
16

Delete File

Action

In Zapier“This action will delete a file in Google Drive. You will need to provide the file ID.”

The other way to delete: this one works from the file ID alone, with no picker and no confirmation box in the step.

When to use it
when an earlier step already carries the ID of the file to remove and you would rather not pick anything by hand.
17

Retrieve Files from Google Drive

Action

In Zapier“This action sends a GET request to the Google Drive API to retrieve a list of files based on specific query parameters.”

Asks the Google Drive API, the interface that lets two pieces of software talk to each other, for a list of files matching the query parameters you set, and hands that list to the rest of the Zap.

When to use it
when one file is not enough and the Zap has to work from several at once.
Searches

The 4 searches

4 search steps look for data that already exists in Google Drive, so a later step can use it.

In the editor the searches sit at the bottom of the Action event list, under their own SEARCH heading. Some action fields also carry a + Add search step button, which slips one in just above the current step and wires what it finds into the field on its own. Whether a search wants the exact value or something close is Google's call, not Zapier's.

1

Retrieve File or Folder by ID

Search

In Zapier“Get a file or folder by its ID.”

Fetches one file or one folder from its ID, and nothing else will do: the ID has to come from a step before it.

When to use it
in the middle of a longer Zap, to pull the full record of something an earlier step only named.
2

Get File Permissions

Search

In Zapier“List all users who have access to a file.”

Lists everyone who currently has access to a file, from the file ID or from a list you pick in.

When to use it
just before a step that removes an access, or on a monthly look at who can still open what.
3

Find a File

SearchFind or create

In Zapier“Search for a specific file by name.”

Looks a file up by name and hands back what it found. The editor also shows a Find or Create File line: same search with the create box ticked, not an extra operation.

When to use it
when the Zap knows the name of a document but nothing about where it lives.
4

Find a Folder

SearchFind or create

In Zapier“Search for a specific folder by name.”

Same by name, for folders. Its twin in the list, Find or Create Folder, is that same search with the box ticked, so it opens the folder when there is none.

When to use it
to drop a file into the folder of the month and let the Zap create it the first time.

The three settings every search exposes

  1. Successful if no search results are found?
    Left alone, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Tick it and the search turns into a find or create: the setting above stops being offered and Zapier asks for the fields it needs to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When it breaks

Two rules first, because they explain most of what goes wrong. A Zap only ever reacts to what happens after you publish it, so nothing already sitting in the folder gets picked up. And a Zap that writes into the very folder its trigger watches sets itself off again, and again.

The rest is Google's side of the deal, plus two error messages worth meeting here rather than at the worst moment. If a Zap of yours is already stuck, Zapier troubleshooting walks through the usual suspects.

  • Rate limits

    The Google Drive API has its own rate limits, and going past them comes back as a 429 error. A Zap firing on every file of a bulk import is the usual way to get there.

  • 750 GB a day

    A Google Workspace account can upload 750 GB a day, My Drive and shared drives together. Files a Zap uploads count against that like any other.

  • The file went missing

    Required field "file" (file is missing) means the step ran without the file it was pointed at. The mapping between that field and the step before it is the first thing to look at.

  • Nothing came back

    Nothing could be found for the search is a search step that matched nothing. Either the value it looked for was wrong, or the setting that lets a Zap carry on empty-handed is still off.

  • New File in Folder has its own rules

    That trigger follows rules of its own about when it goes off. Worth knowing before you decide the Zap is broken, because it is not always the Zap.

  • Several files become one archive

    Drop more than one file into a File field and Zapier compresses them into a single archive. Expect one zip at the other end, not three separate files.

  • A sudden flood

    A trigger that comes back with a huge batch, after a bulk import or a migration, can be held back by Zapier's flood protection. On the polling side Zapier does remember what it has already seen, so the same file will not start the Zap twice.
Need help

Need help automating Google Drive with Zapier?

A person reads every message.

FAQ

The questions people ask before building

01Is the Google Drive Zapier integration free?
Yes, on the free plan, with two limits that matter. Google Drive is not one of the apps Zapier reserves for paid plans, so you can connect it and build on it straight away. The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap is two steps: one trigger and one action. Add a second action, a filter or a search step and it becomes a multi-step Zap, which needs a paid plan. A folder watch with a single action behind it stays inside the free plan.
02How many tasks does a Google Drive Zap use?
One task per action that works. The trigger never costs anything, whatever pace it checks at, and an action that fails is not counted either. In a Zap with several actions each one counts on its own, so the same file moved, renamed and shared eats three tasks rather than one. A few apps and a few actions count more than one task when they finish. On 100 free tasks a month, it is a busy intake folder that empties the count, never the looking.
03Is Google Drive real time on Zapier?
One of the five triggers is, the other four are not. New File in Folder (Realtime) is an instant trigger: the app tells Zapier the moment a file lands, so the Zap starts right away whatever your plan. New File, New File in Folder, New Folder and Updated File are polling triggers, which means Zapier goes and looks at regular intervals and how often depends on your plan: every 15 minutes on the free one, 2 minutes on Professional, 1 minute on Team and Enterprise. Whether a trigger is instant is decided by Google's API and cannot be changed from the editor.
04What do you need to connect the account?
A Google account with Drive on it, and nothing else on Zapier's side. Open Apps in your Zapier account, click + Add connection, pick Google Drive, sign in to Google and grant access. The connection is made once and reused by every step of every Zap. The part people miss is access rights: for a file or folder you do not own, you need read or write access on it before a Zap can touch it. The connection gets created anyway, and the step touching that file fails later, which makes it look like a Zapier problem.
05Why does a Zap ignore the files already in the folder?
Because a Zap only reacts to what happens after it is published. Anything sitting in the folder before you switched the Zap on is never picked up, and moving that backlog is a separate job. The same logic explains the opposite complaint. A Zap that writes into the folder its own trigger watches sets itself off again and again and burns through the task count doing it, so the folder people drop into and the folder the Zap writes to should never be the same one.
06What if the operation you need is not in the list?
Look at API Request (Beta) before giving up on it. That action sends a raw request to Google Drive through the connection you already made, so something the other sixteen actions do not cover can still be reached, as long as you know the request you want. Requests only go to domains tied to this app, and a setting decides whether the Zap stops or carries on when Google answers with an error. If that sounds like more work than the job deserves, the same thing is sometimes simpler on another editor.
07Zapier, Make or n8n for Google Drive?
It depends on three things, and a ranking would be dishonest. Zapier fits when the people who will maintain the Zap are not technical: the editor asks for a trigger, an action and the mapping between them, and nothing else. Make and n8n fit better when a scenario branches a lot, or when the volume makes a per-task count the wrong unit to pay in. Look at how the same folder work is done on each tool before choosing, because the operations on offer are not the same from one to the next, and that decides more than the price does.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations