Google Drive| Hitchhikers Platform

Use the Google Drive Connector to pull in your Google Drive files.

Operations

Fetch Files

Use this operation to fetch files from your linked Google Drive account.

This source uses the Google API endpoints to

  1. List all Files (https://developers.google.com/drive/api/v3/reference/files/list)
  2. Export each File (https://developers.google.com/drive/api/v3/reference/files/export)

The metadata for each file will be part of the response. For Google Drive Documents and Slides, specifically, the text content will also be ingested as a body field in the response.

See Fields below for a list of the fields returned in the JSON response (in addition to body , where present).


Authentication

Select the Google Drive account to fetch your data from. This account must exist as Linked Account under the Google Built-in Provider.

If you have not already done so, you can add a linked account directly from the Connector Settings page (in the dropdown to select a Linked Account), or from Knowledge Graph Configuration > Linked Accounts > Google Page here in your account.

  • When you click Add Linked Account, select the following scope: https://www.googleapis.com/auth/drive.readonly. Then click Link and continue through the Google OAuth flow.
    • This is the only required scope for this operation, which grants Yext permission to access your drive)
  • Once the authentication setup is complete, you’ll need to provide a specific name and ID for your Linked Account. You may want to use the email you linked as the Name, with the email preceded by the google. for the Linked Account ID. For example, you might name your Linked Account radler@gmail.com, with the ID google.radler@gmail.com.


File Scope

Using the File Scope setting, designate the source from which to fetch files. Options include:

  • User
    • Files created by, opened by, or shared directly with the user will be included
  • Domain
    • Files shared to the user’s domain will be included
light bulb
Note
The scope is specified in the API request by passing the chosen value as the corpora query param. See Google’s documentation for more information.


Limits & Other Info

  • The maximum file size that can be ingested is 1MB. If a file is above that threshold, the body content will not be ingested.
  • Trashed Items will not be returned in the response

Fields

  1. id
  2. name
  3. mimeType
  4. starred
  5. trashed
  6. webContentLink
  7. webViewLink
  8. createdTime
  9. modifiedTime
  10. owners[]
    1. displayName
    2. permissionId
    3. emailAddress
  11. lastModifyingUser
    1. displayName
    2. permissionId
    3. emailAddress
  12. shared
  13. permissions[]
  14. originalFilename
  15. size
  16. imageMediaMetadata
  17. videoMediaMetadata
  18. permissionIds[]
  19. exportLinks
  20. driveId
Feedback