Google Docs Connector¶

Summary¶

The Jitterbit Harmony Google Docs Connector establishes access to Google Docs.

The Google Docs connector provides an interface for creating a Google Docs connection, the foundation used for generating instances of Google Docs activities. These activities, once configured, interact with Google Docs through the connection.

The Google Docs connector is accessed from the design component palette's Connections tab (see Design Component Palette).

Connector Overview¶

This connector is used to first configure a Google Docs connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Google Docs connection and its activities are referred to as a Google Docs endpoint:

• Create Docs: Creates documents in Google Docs and is intended to be used as a target in an operation.

• Update Docs: Updates documents in Google Docs and is intended to be used as a target in an operation.

• Get Docs: Retrieves documents from Google Docs and is intended to be used as a source in an operation.

Prerequisites and Supported API Versions¶

The Google Docs connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Google Docs connector uses the Google Docs API v1. Refer to the API documentation for information on the schema nodes and fields.

To use the Google Docs connector, you must have a Google service account for your project with appropriate permissions set, and certain credentials obtained from the service account as described in Google Docs Prerequisites.

Troubleshooting¶

If you experience issues with the Google Docs connector, these troubleshooting steps are recommended:

1. Ensure the Google Docs connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

2. Check the operation logs for any information written during execution of the operation.

3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

4. If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

   <logger name="org.jitterbit.connector.docs" level="DEBUG"/>
   

5. If using Private Agents, you can check the agent logs for more information.