Overview

The Jitterbit Harmony Google Drive Connector is accessed from the Connectivity tab of the design component palette:

This connector is used to first configure a Google Drive connection, establishing access to an account on the Google Drive server, and then used to configure one or more Google Drive activities associated with that connection as either a source or target within an operation:

• Get File: A Google Drive Get File activity retrieves a file from a Google Drive connection and is used as a source in an operation.

• Create File: A Google Drive Create File activity creates a file in a Google Drive connection and is used as a target in an operation.

• Update File: A Google Drive Update File activity updates a file in a Google Drive connection and is used as a target in an operation.

• Delete File: A Google Drive Delete File activity deletes a file in a Google Drive connection and is used as a target in an operation.

The Google Drive connector uses the Google Drive API v3. Refer to the API documentation for information on the schema fields.

The Google Drive connector requires the use of an agent version 10.1 or later.

Together, a specific Google Drive connection and its activities are referred to as a Google Drive endpoint. Once a connection is configured, activities associated with the endpoint are available from the Endpoints filter:

Google Drive Registration

As the connection will be an application that interfaces with Google Drive, you will need a Project ID, Client Email, and Private Key to access the Google Drive API. To obtain these, you need to create a service account from a Google account. See Google Registration for details.

Known Issues

When configuring Google Drive activities, you should be aware of these current known issues:

• Google Drive: Filtering a search on some fields isn’t working

  • Summary: Due to a limitation when using service account credentials, you may not receive a complete list of files.

  • Additional Info: If you choose Domain as the Drives to search parameter, the Query parameter cannot know which value can be used successfully.

  • Workaround: Use the Drive option or use the Google Drive API until this issue is resolved.

• Google Drive: List Files activity fails without a request transformation

  • Summary: Operations configured with a List Files activity must include a request transformation to succeed and return the correct response.

  • Additional Info: This occurs only in an operation with the Google Drive List Files activity.

  • Workaround: Provide a request transformation and run the operation again.