Skip to main content
The Google Docs toolset lets an agent read a Google Doc, create a new one, add text, replace text, and make other edits, acting as the Google account that connected the toolset.

​
What agents can do

Tools that change a document (create_document, insert_text, replace_text, batch_update_document) act in the connected account. In a chat in the PipesHub app, each one asks the user to approve it before it runs, unless an admin has pre-approved it in the action’s Tool approvals. Where nobody can approve (the Slack bot, the API, the PipesHub MCP server, and service-account agents), these tools run only if they are pre-approved; the read tools run as usual. Tabs. get_document labels each tab’s text with its title and tab_id. Without a tab_id, insert_text writes into the first tab and replace_text changes every tab; give a tab_id to work in one tab. If create_document creates the document but can’t add its starting text, it says so and gives the new document’s id: the agent then adds the text with insert_text instead of creating a second document. A tool finds a document by its id: the part of the link after /document/d/. To work with a document you only know by name, also add the Drive toolset so the agent can search for it.

​
Permissions it asks for

Docs has its own sign-in, separate from Drive, Gmail and Calendar, so connecting it never asks those actions to sign in again.

​
Set up

An admin sets the action up once; then each person who wants agents to use it signs in with their own Google account.
1

Enable the Google Docs API

In Google Cloud Console, open your project, go to APIs & Services > Library, search for Google Docs API and click Enable.
2

Add the scope

Add https://www.googleapis.com/auth/documents to your OAuth app’s scopes. In the newer console layout that is Google Auth Platform > Data Access > Add or Remove Scopes; in the older one, APIs & Services > OAuth consent screen > Scopes.
3

Start the setup in PipesHub

Go to Workspace > Actions, find Docs and click Setup. The Action configuration panel shows the Redirect URI; copy it.
4

Create an OAuth client

In APIs & Services > Credentials (or Google Auth Platform > Clients), create an OAuth client of type Web application, paste the redirect URI under Authorized redirect URIs, and create it. Copy the Client ID and Client secret.
5

Finish the action configuration

Back in the Action configuration panel, enter an Instance name, an OAuth app name, the Client ID and the Client secret, then click Create.
6

Each person signs in

Each user opens Your actions, finds the Docs action and clicks Authenticate, signs in to Google and allows access. The action then shows Authenticated.
You can reuse the OAuth client of your other Google actions: add this action’s redirect URI to it and enable the Google Docs API in the same project.

​
Errors you may see

​
FAQ

The connector indexes documents so they appear in search and chat answers. The toolset lets an agent act on documents: create them and change them. Use both if agents should find documents and also edit them.
Yes. Search results link to the document, and get_document reads it by the id in that link, as long as the connected account can open it.