Resources · Make integration

Google Cloud Storage Make integrationAutomate Google Cloud Storage with Make.

Can Make copy, share and clean up your Google Cloud Storage files without code? Yes. The Google Cloud Storage Make integration brings 28 modules, one scheduled trigger included. This guide helps ops and dev teams connect the account and ship a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Cloud Storage Make integration do for you?

The Google Cloud Storage Make integration links your Google Cloud buckets (the containers that hold your files) to Make, a no-code tool where you build a scenario: the automation itself, a chain of steps. Each step is a module. Here, one trigger watches objects, Google's word for the files themselves, and the other modules create, copy, merge, search, delete or share buckets and objects.

Back up every new file. Watch Objects spots new objects, and Clone an Object copies each one into a second bucket. A quiet safety net for a design team whose client deliverables land in storage.

Hand a file to a client, then take access back. Create an Object ACL, an access rule on one single file, opens it to a given reader, and Delete an Object ACL closes it when the project ends. No console, no forgotten open file.

Feed storage from your other tools. A scenario can start in another app, a form or a CRM, and push the file with Upload an Object. Merge Objects then stitches several parts into one.

One honest caveat: Make's doc lists these modules by name only, so the roles on this page are read from their names; check each one with Run once before relying on it. What Make will not stretch: the doc caps an object at 5 TB, and anything the 28 modules miss goes through Make an API Call. Google Cloud Storage also has an n8n node, covered on the Google Cloud Storage n8n integration page, and the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect Google Cloud Storage to Make?

  1. 01

    Prepare your Google Cloud project

    Make reaches Google Cloud Storage through a project in Google Cloud Platform. Sign in with your Google account, create a project for Google Cloud Storage and configure it by following the Make doc for this app.

  2. 02

    Authorize Make on the Google side

    The doc asks you to add Make as an authorized data source in Google Cloud Storage. Do it inside the project you just prepared, so Make is allowed to reach your buckets when you connect.

  3. 03

    Create the connection in Make

    In a scenario, add any Google Cloud Storage module and click Create a connection. A connection is your account linked to Make once; every other Google Cloud Storage module reuses it, so you do this one time.

First scenario

Your first scenario: back up each new object

GoalWhen a new object appears in Google Cloud Storage, Make copies it into a backup bucket with Clone an Object.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Search for Google Cloud Storage and pick Watch Objects, the module that starts the flow.

  2. 02

    Link your account

    Click Create a connection and choose the Google account tied to your Google Cloud project. Once linked, Make lists what it can read, so you pick instead of typing names.

  3. 03

    Add the copy step

    Click the + on the right of Watch Objects and choose Clone an Object. Map the object from the previous module, Tip: send the copy to another bucket than the watched one, so the scenario never picks up its own copies.

  4. 04

    Test with Run once

    Add a test file, then click Run once. Make runs the scenario one time and shows the bundles each module received: a bundle is one item passed along, here one object.

  5. 05

    Schedule and switch on

    Open the clock on Watch Objects: a new scenario checks every 15 minutes by default. Switch the scenario on. Each module run on a bundle is an operation, the unit Make counts on your plan.

Triggers

What starts a Google Cloud Storage scenario?

1 module starts a scenario when something happens in Google Cloud Storage. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Cloud Storage as soon as it happens.

Google Cloud Storage1Watch Objects

Watch Objects

triggerIn the docs only

Watch Objects picks up objects that show up in your Google Cloud Storage and hands each one to the next module as a bundle, one file per bundle. Make's doc gives it no description, so its role and its type below are read from its name.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and down to 1 minute on a paid plan. A new file simply waits for the next check.
When to use it
a partner drops exports in a bucket and each export should be copied, logged or announced without anyone opening the console.
Watch out
send whatever the scenario writes to a bucket Watch Objects does not watch, so it never picks up its own output.
Modules

Everything the Google Cloud Storage app can do in Make

Google Cloud Storage gives you 27 modules in 6 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Buckets

5 modules

Note: Refer to Google documentation to learn more about buckets name.

In the Labels field, specify key-value metadata pairs that allow you to group your buckets along with other Google Cloud resources such as virtual machine instances and persistent disks. For example, you can use labels to create a team key that has values alpha, beta, and delta, and apply the team:alpha, team:beta, and team:delta labels to different buckets in order to indicate which team is associated with those buckets. You can create a maximum of 64 labels.

In the Predefined ACL field, select a predefined set of access controls for this bucket:

In the Predefined Default Object ACL field, select a predefined set of default object access controls for this bucket:

Google Cloud Storage1

Create a Bucket

ActionIn the docs only

Create a Bucket sets up a new storage container in your project from inside a scenario, with its name, its labels and its access settings. Handy when every new client or project deserves its own space.

When to use it
a deal closes in your CRM and the client's delivery bucket should exist before the kickoff call.
Watch out
Google has its own naming rules for buckets, linked from the Make doc, so read them before mapping a client name into the field.
Google Cloud Storage2

Get a Bucket

ActionIn the docs only

Get a Bucket reads the settings of one bucket you already know by name and returns them as a single bundle. Nothing changes on the Google side, it only looks.

When to use it
before you touch a bucket, check how it is set today, for example to compare its labels with your project sheet.
Watch out
it needs one precise bucket; to browse all of them, List Buckets fits better.
Google Cloud Storage3

List Buckets

SearchIn the docs only

List Buckets returns every bucket the connection can see, one bundle per bucket, so the rest of the scenario runs once for each. Zero buckets means zero bundles, and the scenario simply stops.

When to use it
building an inventory in a spreadsheet so finance sees which team owns which storage, thanks to the labels.
Watch out
every bucket that flows on costs operations in the modules placed after it.
Google Cloud Storage4

Update a Bucket

ActionIn the docs only

Update a Bucket changes the settings of an existing bucket, such as its labels, those key and value tags that group resources by team or project. The bucket and its objects stay where they are.

When to use it
a project moves to another team and the team label should follow, with no one digging through the console.
Watch out
try it with Run once on a bucket that does not matter before pointing it at a shared one.
Google Cloud Storage5

Delete an Empty Bucket

ActionIn the docs only

Delete an Empty Bucket removes a bucket, and the name states the condition: no object may be left inside. That rule works as a small safety catch against wiping live data.

When to use it
closing a finished project, after Search Objects and Delete an Object have cleared its content.
Watch out
a deletion does not come back, so keep this module at the very end of a scenario you have already tested.

Objects

7 modules

Note: The maximum size is 5 TB.

Google Cloud Storage6

Upload an Object

ActionIn the docs only

Upload an Object puts a file from an earlier module into Google Cloud Storage, whether it came from an email attachment, a form or a generated report. The doc sets the ceiling at 5 TB per object.

When to use it
a scenario starts in another app, say a signed contract in an e-signature tool, and a copy must land in your bucket.
Watch out
on the Free plan Make handles files up to 5 MB, far below what the bucket accepts.
Google Cloud Storage7

Merge Objects

ActionIn the docs only

Merge Objects stitches several objects already stored in a bucket into a single new one. Think of a process that writes its results in pieces and a reader who wants one file.

When to use it
an export tool drops a report in several parts and your analyst should receive the assembled version.
Watch out
the order of the parts shapes the result, so open the merged object after a Run once before going live.
Google Cloud Storage8

Get an Object

ActionIn the docs only

Get an Object brings back one object you can point to, so the next module can work with it. It is the bridge between your bucket and any tool that should receive the file.

When to use it
right after Watch Objects, to pass a fresh upload to a chat channel, an email or an AI tool.
Watch out
Make's Free plan stops at 5 MB per file, so check your plan before routing large media this way.
Google Cloud Storage9

Search Objects

SearchIn the docs only

Search Objects looks through your storage and returns every matching object as its own bundle, so whatever follows runs once per file. Zero, one or many results are all normal outcomes.

When to use it
gather all the files of one client before archiving, sharing or deleting them.
Watch out
a broad search can return a lot of bundles, each one costing operations downstream; narrow it before chaining a delete.
Google Cloud Storage10

Clone an Object

ActionIn the docs only

Clone an Object makes a copy of an object and leaves the original where it was. It is the backbone of any backup or handoff scenario on this app.

When to use it
a finished deliverable should also live in an archive bucket that only managers read.
Watch out
point the copy at a bucket Watch Objects does not watch, so the scenario never picks up its own copies.
Google Cloud Storage11

Update an Object

ActionIn the docs only

Update an Object changes the details of an object already stored, without creating a new file next to it. The object keeps its place in the bucket.

When to use it
a file moves from draft to approved in your project tool, and the object in storage should carry that change too.
Watch out
check the result with Run once on a test object before pointing it at real files.
Google Cloud Storage12

Delete an Object

ActionIn the docs only

Delete an Object removes one object from its bucket. Paired with Search Objects, it clears a batch of files in one pass; alone, it deletes the exact file you map.

When to use it
a client asks for their documents to be erased at the end of a contract.
Watch out
there is no undo in Make; keep a Clone an Object step before it if you might need the file later.

Bucket ACLs

5 modules
Google Cloud Storage13

Create a Bucket ACL

ActionIn the docs only

Create a Bucket ACL adds an access rule to a whole bucket. An ACL, short for access control list, says who may read or change what; this module grants that right to one more person or team.

When to use it
a freelancer joins a project and needs access to its bucket.
Watch out
a rule on the bucket covers every file inside; for a single document, Create an Object ACL is narrower.
Google Cloud Storage14

Get a Bucket ACL

ActionIn the docs only

Get a Bucket ACL reads a single access rule on a bucket, for one precise entity, and returns what it allows. Read only: nothing changes.

When to use it
before an audit call, check what a former contractor can still do on a sensitive bucket.
Watch out
it answers about one rule; to see everyone at once, go for List Bucket ACLs instead.
Google Cloud Storage15

List Bucket ACLs

SearchIn the docs only

List Bucket ACLs returns every access rule of a bucket, one bundle per rule. It gives a quick picture of who holds the keys to that storage.

When to use it
feed a security review sheet, with one line per person or group that can reach client data.
Watch out
each rule becomes a bundle, so an action placed after it runs once per rule and counts that many operations.
Google Cloud Storage16

Update a Bucket ACL

ActionIn the docs only

Update a Bucket ACL raises or lowers what an existing entity may do on a bucket, without removing that entity from the list.

When to use it
a partner moves from active production to a review role once the campaign is live, and should only look from now on.
Watch out
the rule must already exist; for a newcomer, start with Create a Bucket ACL.
Google Cloud Storage17

Delete a Bucket ACL

ActionIn the docs only

Delete a Bucket ACL withdraws one access rule from a bucket, so that person or group loses what the rule granted. The bucket and its content stay intact.

When to use it
offboarding, when an employee leaves and your HR tool records the departure.
Watch out
removing the wrong rule can cut off a live integration; test on a spare bucket before plugging it into a real flow.

Bucket Default Object ACLs

4 modules
Google Cloud Storage18

Create a Bucket's Default Object ACL

ActionIn the docs only

Create a Bucket's Default Object ACL sets a rule the bucket gives by default to the objects stored in it. Instead of opening each new file one by one, the bucket handles it for you.

When to use it
a shared press kit bucket where every new visual should be readable by the comms team.
Watch out
a default rule spreads to many files, so check who it names before switching the scenario on.
Google Cloud Storage19

Get a Bucket's Default Object ACLs

ActionIn the docs only

Get a Bucket's Default Object ACLs shows the default rules a bucket hands to its objects, so you know what a new file will inherit before you drop it in.

When to use it
as a check before Upload an Object, when confidential files must not land in a bucket open to a wide audience.
Watch out
it only reads; any fix goes through the Update or Delete module of the same group.
Google Cloud Storage20

Update a Bucket's Default Object ACL

ActionIn the docs only

Update a Bucket's Default Object ACL adjusts one default rule of a bucket, so the files that inherit it get a different access level. Useful when a bucket changes role over its life.

When to use it
an internal drafts bucket becomes the source of a client portal, and its default rule has to follow.
Watch out
test on a bucket holding a single throwaway file before touching one shared across teams.
Google Cloud Storage21

Delete a Bucket's Default Object ACL

ActionIn the docs only

Delete a Bucket's Default Object ACL removes one default rule, so the bucket stops handing that access to its objects. The other default rules remain in place.

When to use it
a partnership ends and the partner's group should no longer inherit access to new files.
Watch out
check the files already inside too, with List Object ACLs, since each object can carry rules of its own.

Object ACLs

5 modules
Google Cloud Storage22

Create an Object ACL

ActionIn the docs only

Create an Object ACL grants access to one single object rather than a whole bucket. It is the finest grain of sharing the app offers in Make.

When to use it
a signed quote goes to one client contact, who should read that file and nothing else.
Watch out
access given this way stays until something removes it; pair it with Delete an Object ACL at the end of the project.
Google Cloud Storage23

Get an Object ACL

ActionIn the docs only

Get an Object ACL reads one access rule set on one object and tells you what it allows. Handy as a guard before sending a file to anyone.

When to use it
your support team wants to confirm a customer can open the invoice file before replying to the ticket.
Watch out
it looks at one rule for one entity; for the full list of who can open the file, List Object ACLs is the right pick.
Google Cloud Storage24

List Object ACLs

SearchIn the docs only

List Object ACLs returns all the access rules of one object, each rule in its own bundle. A clear view of who can open a given file.

When to use it
a legal review asks, file by file, who can open a contract, and the answer should go into a sheet.
Watch out
placed after Search Objects, the rules pile up quickly, one bundle per rule per file.
Google Cloud Storage25

Update an Object ACL

ActionIn the docs only

Update an Object ACL modifies an existing rule on a file, changing what that person or group may do with it, while the rule itself stays in place.

When to use it
a reviewer has finished commenting on a draft and should now only read the final version.
Watch out
there is nothing to update if the rule does not exist yet; Create an Object ACL comes first.
Google Cloud Storage26

Delete an Object ACL

ActionIn the docs only

Delete an Object ACL takes back one access rule from a file. The file stays, the person loses that access.

When to use it
a deal is marked lost in your CRM and the proposal shared with the prospect should close again.
Watch out
other rules on the same object, or on its bucket, may still let that person in; list them before calling the file private.

Other

1 module
Google Cloud Storage27

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Google Cloud Storage API with the connection you already set up. It covers what the other modules leave aside.

When to use it
you need an operation the list above lacks and the Google Cloud Storage API documentation describes it.
Watch out
here you write the request yourself from Google's API reference, so keep it for the gaps; the ready-made modules stay simpler to read.
Need help

Need help automating Google Cloud Storage with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Google Cloud Storage Make integration free?
Yes. Google Cloud Storage is a standard app in Make, so its modules work from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module run on a bundle.
02What does it take to connect Google Cloud Storage to Make?
A Google account and a Google Cloud Storage project in Google Cloud Platform. The Make doc for this app asks you to create and configure that project first, and to add Make as an authorized data source in Google Cloud Storage. Only then do you open Make, add a Google Cloud Storage module and click Create a connection. The connection is saved once and reused by all 28 modules. Make also states that data it receives from Google APIs is handled under the Google API Services User Data Policy.
03Does the Google Cloud Storage trigger react in real time?
No. Watch Objects, the only trigger of the app, works as a scheduled trigger, a type read from its name since the doc gives no description: Make checks Google Cloud Storage on the scenario's schedule instead of being called the moment a file lands. A new scenario checks every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans go down to 1 minute. If a short delay matters, set the clock on Watch Objects to the smallest interval your plan allows. The doc lists no instant trigger for this app.
04What if a module is missing or a limit gets in the way?
Use Make an API Call. It calls any endpoint of the Google Cloud Storage API with the connection you already created, so there is no second login to set up. The 28 modules cover buckets, objects and three layers of access rules, and the API call fills the rest. Keep two fixed limits in mind: the doc sets 5 TB as the maximum object size, and the Free plan of Make handles files up to 5 MB, so check your plan before routing heavy media.
05Make or n8n for Google Cloud Storage?
It depends on where the rest of your automations live. Both tools talk to Google Cloud Storage: Make through the 28 modules on this page, n8n through its own node, described on the dedicated n8n page of this site. On the Make side you get one trigger, ready-made modules for buckets, objects and access rules, and Make an API Call for the rest. The fairest test is to build the same small flow in each tool, for instance the backup scenario above, and keep the one your team reads more easily.