example

Create a webhook to receive notifications of changes with a Google Drive

Create a new file with content and metadata

Create a webhook to receive notifications of changes for a file or folder

Stop a webhook channel from sending notifications

Gets information about the user's Drive, and system capabilities 

Get the information and metadata of the user that is currently logged in

Gets a file's metadata and content by ID.

List changes made to files in your Google Drive since the last time this step ran (up to 1000)

The first time this action runs, it takes note of the current `pageToken` returned by Google, and returns no changes.
Subsequent runs of this step use that `pageToken` to determine what has changed since the last time this step ran.


example.png

List the available export types of a file by ID.

Lists all available files and directories

The Google Drive component authenticates requests through the Google Cloud Platform (GCP) OAuth 2.0 service.
You'll need to create a GCP OAuth 2.0 app so your integration can authenticate and perform Google Drive tasks on your customers' behalf.

To create a Google Drive OAuth 2.0 app, first make sure you have a Google Developer account - you can sign up at [https://console.cloud.google.com/](https://console.cloud.google.com/).
Then:

1. Open up the Google Drive API console - [https://console.cloud.google.com/apis/api/drive.googleapis.com](https://console.cloud.google.com/apis/api/drive.googleapis.com)
1. Click **CREATE PROJECT** if you would like to create a new GCP project, or select an existing project.
1. You will be prompted to enable **Google Drive API** for your project. Click **ENABLE**.
1. On the sidebar, select **Credentials**.
1. An OAuth 2.0 app includes a "Consent Screen" (the page that asks "Do you want to allow (Your Company) to access Google Drive on your behalf?"). Click **CONFIGURE CONSENT SCREEN**.
   1. Your app will be externally available to your customers, so choose a **User Type** of **External**.
   1. Fill out the OAuth consent screen with an app name (your company or product's name), support email, app logo, domain, etc.
   1. You can ignore domains for now.
   1. On the next page, add the scope `https://www.googleapis.com/auth/drive`.
   1. Enter some **test users** for your testing purposes.
      Your app will only work for those testing users until it is "verified" by Google.
      When you are ready for verification (they verify your privacy policy statement, etc), click **PUBLISH APP** on the **OAuth consent screen**.
      That'll allow your customers to authorize your integration to access their Google Drive.
1. Once your "Consent Screen" is configured open the **Credentials** page from the sidebar again.
1. Click **+CREATE CREDENTIALS** and select **OAuth client ID**.
   1. Under **Application type** select **Web application**.
   1. Under **Authorized redirect URIs** enter Prismatic's OAuth 2.0 callback URL: `https://oauth2.prismatic.io/callback`
   1. Click **CREATE**.
1. Take note of the **Client ID** and **Client Secret** that are generated.

:::info
Make sure to **publish** your OAuth 2.0 app after you've tested it so users outside of your _test users_ can authorize your integration to interact with Google Drive on their behalf.
:::

Now that you have a **Client ID** and **Client Secret**, add Google Drive step to your integration in Prismatic.
Open the **Configuration Wizard Designer** by clicking **Configuration Wizard**, select your **Google Drive Connection** and enter your client ID and secret.
You will probably want to keep the default [Google Drive scope](https://developers.google.com/identity/protocols/oauth2/scopes#drive), `https://www.googleapis.com/auth/drive`.


[Google Drive](https://www.google.com/drive/) is Google's cloud storage for work and home.
This component allows you to create, copy, download, update, list, and delete files stored in a Google Drive Account.


Checks for new and updated files in any folder on a configured schedule.

Test Customer

Test Flow Name

Test Instance

Test Integration

Test User

Receive and validate webhook requests from Google Drive for webhooks you configure.

Action Name	Action Description
Get About	Gets information about the user's Drive, and system capabilities
Get File	Gets a file's metadata and content by ID.
Create File	Create a new file with content and metadata
List Files	Lists all available files and directories
Copy File	Copy a file by file id
Update File	Updates a file's content by file id
Delete File	Delete a file by file id
Empty Trash	Empty the trash of deleted files
Create Folder	Create a directory file
List Folders	Lists all available directories
Raw Request	Send raw HTTP request to Google Drive
Search Folders	Search for an existing directory by Name
List File's Export Types	List the available export types of a file by ID.
Search Files	Search for an existing file by Name
List Drives	List all drives
List Changes	List changes made to files in your Google Drive since the last time this step ran (up to 1000)
Create Webhook for Drive	Create a webhook to receive notifications of changes with a Google Drive
Create Webhook for File or Folder	Create a webhook to receive notifications of changes for a file or folder
Delete Webhook	Stop a webhook channel from sending notifications
Get Current User	Get the information and metadata of the user that is currently logged in
Move File	Move a file by file ID

Trigger Name	Trigger Description
Push Notification Webhook	Receive and validate webhook requests from Google Drive for webhooks you configure.
New and Updated Files	Checks for new and updated files in any folder on a configured schedule.

Google Drive Connector

Integrate with customers’ other SaaS apps, fast

About the Google Drive Connector

Actions

Triggers

Ready to get started?