# Introduction This collection is intended to create buckets and upload files to buckets on the Google Cloud Storage platform. # Prerequisites This collection requires that you have Google OAuth2 set up for your project ([learn more about Google OAuth2 here](https://learning.postman.com/docs/developer/intro-api/)). ## Automation To automate retrieval of the OAuth2 token, here are some resources that will allow you to create this functionality: - [https://community.postman.com/t/how-can-i-auto-refresh-oauth-2-0-token-once-the-token-expires/20062/4](https://community.postman.com/t/how-can-i-auto-refresh-oauth-2-0-token-once-the-token-expires/20062/4) - [https://allenheltondev.medium.com/how-to-automate-oauth2-token-renewal-in-postman-864420d381a0](https://allenheltondev.medium.com/how-to-automate-oauth2-token-renewal-in-postman-864420d381a0) #### Forking Collections In order to use this integration, you will need to fork this collection. You can do this by left clicking on a collection and pressing create a fork. You will also need to fork the environment named ***Google Cloud Storage*** ([learn more about forking collections and environments here](https://learning.postman.com/docs/collaborating-in-postman/version-control-for-collections/#forking-a-collection)). # Monitors In the integration, a monitor is used to automatically check to update the changes made to a collection once a day. In order to make this monitor, input the desired Monitor Name, select the ***Google Cloud Storage Integration*** collection as the Collection. Select the ***Google Cloud Storage*** environment as the environment and select how often you want it to be run to check if your collection has been updated (we recommend once a day). Then, your monitor should be created ([learn more about creating a monitor here](https://learning.postman.com/docs/designing-and-developing-your-api/monitoring-your-api/setting-up-monitor/#:~:text=When%20you%20open%20a%20workspace,Started%2C%20then%20Create%20a%20monitor.)). # Mocks If you would like to see example responses and run and interact with the collection without having to input valid credentials, you will need to create a mock server. You can do this by left clicking on your forked version of this integration and selecting ***Mock Collection*** ([learn more about creating a mock server here](https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/setting-up-mock/)). Then you will also need to fork the ***[MOCK] Google Cloud Storage*** environment. Copy the mock server url and assign it to the environment variable ***mockUrl***. If you run the collection with the mock environment selected, it will show you what a successful request looks so long as you fill out the environment variables with the correct variable type. # Workflow Diagram  # Environment Setup To use this collection, the following environment variables must be defined: | Key | Description | |---|---| | `clientId` | Your OAuth2 client ID ([learn more about creating a client ID and client secret here](https://developers.google.com/adwords/api/docs/guides/authentication#create_a_client_id_and_client_secret)) | | `clientSecret` | Your OAuth2 client secret ([learn more about creating a client ID and client secret here](https://developers.google.com/adwords/api/docs/guides/authentication#create_a_client_id_and_client_secret)) | | `projectId` | Your project ID ([learn more about creating and managing projects here](https://cloud.google.com/resource-manager/docs/creating-managing-projects)) | | `apiKey` | Your Google Cloud API key ([learn more about creating a Google Cloud API key here](https://cloud.google.com/docs/authentication/api-keys?authuser=4#creating_an_api_key)) | | `bucketName` | The name of the bucket you would like to create or upload files to | | `fileName` | The name you would like your uploaded file to have |

Versori has established itself as the third generation of Integration Platform as a Service (iPaaS). Versori builds custom integrations for its customers using an intuitive visual user interface.

Versori’s connector engine means there is no dependency on an existing library of apps, all you need to start is the documentation of the app or system you want to integrate to.