Google Cloud Storage
With Google Cloud Storage modules in Make, you can manage the buckets and objects in your Google Cloud Storage account.
To use the Google Cloud Storage modules, you must have a Google account, and a Google Cloud Storage project created in your Google Console. You can create an account at accounts.google.com. You need to add Make as an authorized data source in Google Cloud Storage.
Refer to the Google Cloud Storage API documentation for a list of available endpoints.
Note
Make's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy.
Connect Google Cloud Storage to Make
To establish the connection, you must:
Create and configure a Google Cloud Console project for Google Cloud Storage
Before you establish the connection in Make, you must create and configure a project in the Google Cloud Console to obtain your client credentials.
Create a Google Cloud Console project for Google Cloud Storage
To create a Google Cloud Console project:
Log in to the Google Cloud Console using your Google credentials.
In the top menu, click Select a project > New project.
Enter a Project name and select the Location for your project.
Click Create.
In the top menu, check if your new project is selected in the Select a project dropdown. If not, select the project you just created.
Enable APIs for Google Cloud Console
To enable the required APIs:
Open the left navigation menu and go to APIs & Services > Library.
Search for and enable the following APIs: Cloud Resource Manager API, Cloud Pub/Sub API (only for the Watch Objects module).
Configure your OAuth consent screen for Google Cloud Console
To configure your OAuth consent screen:
In the left sidebar, click OAuth consent screen.
Under User Type, select External.
For more information regarding user types, refer to Google's Exceptions to verification requirements documentation.
Click Create.
Fill in the required fields with your information.
In the Authorized domains section, add
make.comandintegromat.com.Click Save and continue.
In the Scopes page, click Add or remove scopes, add the following scopes, and click Update.
https://www.googleapis.com/auth/devstorage.read_writehttps://www.googleapis.com/auth/devstorage.full_controlhttps://www.googleapis.com/auth/devstorage.read_onlyhttps://www.googleapis.com/auth/cloud-platform.read-onlyhttps://www.googleapis.com/auth/cloud-platform
Click Save and continue.
Optional: If your project will remain in the Testing publishing status, add test user emails on the Test users page, then click Save and continue.
Note
Testing: If you keep your project in the Testing status, you will be required to reauthorize your connection in Make every week. To avoid weekly reauthorization, update the project status to In production.
In production: If you update your project to the In production status, you will not be required to reauthorize the connection weekly. To update your project's status, go to the OAuth consent screen and click Publish app. If you see the notice Needs verification, you can choose whether to go through the Google verification process for the app or to connect to your unverified app. Currently, connecting to unverified apps works in Make, but we cannot guarantee the Google will allow connections to unverified apps for an indefinite period.
For more information regarding publishing statuses, refer to the Publishing status section of Google's Setting up your OAuth consent screen help.
Create your Google Cloud Storage client credentials
To create your client credentials:
In the left sidebar, click Credentials.
Click + Create Credentials > OAuth client ID.
In the Application type dropdown, select Web application.
Update the Name of your OAuth client. This will help you identify it in the console.
In the Authorized redirect URIs section, click + Add URI and enter the following redirect URI:
https://www.integromat.com/oauth/cb/google-custom.Click Create.
Copy your Client ID and Client secret values and store them in a safe place.
You will use these values in the Client ID and Client Secret fields in Make.
Establish the connection with Google Cloud Storage in Make
To establish the connection in Make:
Log in to your Make account, add a Google Cloud Storage module to your scenario, and click Create a connection.
Note: If you add a module with an
instanttag, click Create a webhook, then Create a connection.Optional: In the Connection name field, enter a name for the connection.
In the Client ID and Client Secret fields, enter the values you copied in the Create your Google Cloud Storage client credentials section above.
Optional: Switch on the Show advanced settings toggle and add the needed scopes.
Click Sign in with Google.
If prompted, authenticate your account and confirm access.
You have successfully established the connection. You can now edit your scenario and add more Google Cloud Storage modules. If your connection requires reauthorization at any point, follow the connection renewal steps here.
Build Google Cloud Storage Scenarios
After connecting the app, you can perform the following actions:
Create a Bucket
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, anddelta, and apply theteam:alpha,team:beta, andteam:deltalabels 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:
authenticatedRead: Project team owners getOWNERaccess, andallAuthenticatedUsersgetREADERaccess.private: Project team owners getOWNERaccess.projectPrivate: Project team members get access according to their roles.publicRead: Project team owners getOWNERaccess, andallUsersgetREADERaccess.publicReadWrite: Project team owners getOWNERaccess, andallUsersgetWRITERaccess.
In the Predefined Default Object ACL field, select a predefined set of default object access controls for this bucket:
authenticatedRead: Object owner getsOWNERaccess, andallAuthenticatedUsersgetREADERaccess.bucketOwnerFullControl: Object owner getsOWNERaccess, and project team owners getOWNERaccess.bucketOwnerRead: Object owner getsOWNERaccess, and project team owners getREADERaccess.private: Object owner getsOWNERaccess.projectPrivate: Object owner getsOWNERaccess, and project team members get access according to their roles.publicRead: Object owner getsOWNERaccess, andallUsersgetREADERaccess.
Get a Bucket
List Buckets
Update a Bucket
Delete an Empty Bucket
Watch Objects
Note
This app uses webhooks to trigger a scenario when an event occurs instantly. All webhook modules have an
instanttag next to their name.When you create a Google Cloud Storage webhook in Make, it is attached automatically.
To use this module, you must:
Enable Cloud Pub/Sub API
Assign a Pub/Sub Owner IAM role. To do it, in Google Cloud Console go to IAM & Admin > IAM.
Upload an Object
Note: The maximum size is 5 TB.
Merge Objects
Get an Object
Search Objects
Clone an Object
Update an Object
Delete an Object
Create a Bucket ACL
Get a Bucket ACL
List Bucket ACLs
Update a Bucket ACL
Delete a Bucket ACL
Create a Bucket's Default Object ACL
Get a Bucket's Default Object ACLs
Update a Bucket's Default Object ACL
Delete a Bucket's Default Object ACL
Create an Object ACL
Get an Object ACL
List Object ACLs
Update an Object ACL
Delete an Object ACL
Make an API Call