Google Docs Integration with Orkes Conductor
- v5.3.0 and later
Integrating Google Docs with Orkes Conductor lets you build workflows that interact with your Google Docs using the following operations:
- Create Document
- Update Document
- Get Document
- Replace Text
- Append Text
This guide explains how to set up and use the integration. Here’s an overview:
- Get the required credentials from Google Console.
- Configure a new Google Docs integration in Orkes Conductor.
- Use Google Docs integration in workflows.
Step 1: Get the Google Console credentials
To integrate Google Docs with Orkes Conductor, retrieve the OAuth client ID and secret from the Google console, and enable the Google Docs API.
Get OAuth Client credentials
To get the credentials:
- Go to the Google Cloud Console.
- Select your project or create a new one.
- In the left navigation menu, go to APIs & Services > Credentials
- Select + Create credentials > OAuth client ID.

- Choose your application type as Web application, and enter a Name.
- In Authorized redirect URIs, select +Add URI and enter your redirect URI in the format
https://<YOUR-CONDUCTOR-CLUSTER-NAME>/integrations/oauth/callback. - Select + Create.
- Note the generated OAuth Client ID and secret, or download and save the JSON.
Enable Google Docs API
To enable Google Docs API access:
- Go to APIs & Services > Enabled APIs & services.
- Select + Enable APIs and services.
- Search for Google Docs API and enable it.
Step 2: Add an integration for Google Docs
After obtaining the credentials, add a Google Docs integration to your Conductor cluster.
To create an integration:
- Go to Integrations > Connected Apps from the left navigation menu on your Conductor cluster.
- Select + New integration.
- In the Productivity section, choose Google Docs.
- Select + Add and enter the following parameters:
| Parameter | Description | Required/Optional |
|---|---|---|
| Integration name | A name for the integration. | Required. |
| Scope | The OAuth2 scope for Google Docs API access. The scope you select determines the level of access Google grants to the integration. Supported values:
| Required. |
| OAuth Client ID | The OAuth client ID generated from Step 1. | Required. |
| OAuth Client Secret | The OAuth client secret generated from Step 1. | Required. |
| Default Document Id | The default document ID to use. To get the document ID, open the document. The ID is the string of characters at the end of the URL: https://docs.google.com/document/d/<YOUR-DOC-ID>/edit?tab=t.0. | Optional. |
| Description | A description of the integration. | Required. |

- (Optional) Toggle the Active button off if you don’t want to activate the integration instantly.
- Select Authorize.
This takes you to the Google sign-in page, where you can authorize the connection with your Google account. Once authorized, the integration is created successfully.
Step 3: Use Google Docs integration in workflows
Once the integration is ready, this can be used directly within the workflows.
To use Google Docs integration in a workflow:
- Go to Definitions > Workflow from the left navigation menu on your Conductor cluster.
- Select + Define workflow.
- In your workflow, select the (+) icon and select Connected Apps.

- In Add Task panel on the right, search for Google Docs, and select the integration created in Step 2.
The following operations are available for use with this integration.
| Operation | Description | Supported Integration Scopes |
|---|---|---|
| Create Document | Create a new Google Doc with a title and content. |
|
| Update Document | Replace all document content with new text. |
|
| Get Document | Fetch a Google Doc by ID, including structure and content metadata. |
|
| Replace Text | Find and replace all occurrences of target text in a Google Doc. |
|
| Append Text | Append text to the end of an existing Google Doc. |
|
- Select the required operation, configure the parameters, and select Save > Confirm.
- Select Execute to run the workflow.
For the complete operations parameters and output reference, see Google Docs Operations Reference.