- Home
- Resources
- Integrations
- Google Cloud Storage
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 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.
How do you connect Google Cloud Storage to Make?
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Watch Objects
triggerIn the docs onlyWatch 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.
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.
Modules index
Buckets
5 modulesNote: 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:
Create a Bucket
ActionIn the docs onlyCreate 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.
Get a Bucket
ActionIn the docs onlyGet 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.
List Buckets
SearchIn the docs onlyList 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.
Update a Bucket
ActionIn the docs onlyUpdate 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.
Delete an Empty Bucket
ActionIn the docs onlyDelete 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.
Objects
7 modulesNote: The maximum size is 5 TB.
Upload an Object
ActionIn the docs onlyUpload 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.
Merge Objects
ActionIn the docs onlyMerge 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.
Get an Object
ActionIn the docs onlyGet 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.
Search Objects
SearchIn the docs onlySearch 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.
Clone an Object
ActionIn the docs onlyClone 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.
Update an Object
ActionIn the docs onlyUpdate 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.
Delete an Object
ActionIn the docs onlyDelete 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.
Bucket ACLs
5 modulesCreate a Bucket ACL
ActionIn the docs onlyCreate 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.
Get a Bucket ACL
ActionIn the docs onlyGet a Bucket ACL reads a single access rule on a bucket, for one precise entity, and returns what it allows. Read only: nothing changes.
List Bucket ACLs
SearchIn the docs onlyList 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.
Update a Bucket ACL
ActionIn the docs onlyUpdate a Bucket ACL raises or lowers what an existing entity may do on a bucket, without removing that entity from the list.
Delete a Bucket ACL
ActionIn the docs onlyDelete 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.
Bucket Default Object ACLs
4 modulesCreate a Bucket's Default Object ACL
ActionIn the docs onlyCreate 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.
Get a Bucket's Default Object ACLs
ActionIn the docs onlyGet 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.
Update a Bucket's Default Object ACL
ActionIn the docs onlyUpdate 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.
Delete a Bucket's Default Object ACL
ActionIn the docs onlyDelete 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.
Object ACLs
5 modulesCreate an Object ACL
ActionIn the docs onlyCreate 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.
Get an Object ACL
ActionIn the docs onlyGet 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.
List Object ACLs
SearchIn the docs onlyList 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.
Update an Object ACL
ActionIn the docs onlyUpdate 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.
Delete an Object ACL
ActionIn the docs onlyDelete an Object ACL takes back one access rule from a file. The file stays, the person loses that access.
Other
1 moduleMake an API Call
ActionIn the docs onlyMake 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.
Need help automating Google Cloud Storage with Make?
A person reads every message.