← Docs

Docs · Connector reference

Google Docs connector reference

Operations, inputs, troubleshooting, and questions for the Google Docs connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Google Docs connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

ResourceRecord identityStart withPage coverage
DocumentsidTop levelCursor
Record identity
Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with
Resolve the parent identifier first.
Cursor
Cursor pagination. Continue from the returned cursor; an initial page is not a complete inventory.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Read
Retrieves information; check the returned scope and identifiers before use.
Action
Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
OperationEffectApprovalProvider permissionsInputs
Google Docs Drive Activity QueryReadBy policyhttps://www.googleapis.com/auth/drive.activity.readonly3
Google Docs File GetReadBy policyhttps://www.googleapis.com/auth/drive.file1
Google Docs Comment GetReadBy policyhttps://www.googleapis.com/auth/drive.file2
Google Docs Reply CreateActionBy policyhttps://www.googleapis.com/auth/drive.file3
Docs Get DocumentReadBy policyhttps://www.googleapis.com/auth/documents.readonly1
Docs Create DocumentActionApproval requiredhttps://www.googleapis.com/auth/documents1
Docs Batch UpdateActionApproval requiredhttps://www.googleapis.com/auth/documents2

Inputs by operation

Google Docs Drive Activity Query Read
Inputs for Google Docs Drive Activity Query
InputRequirementAccepted value
file_idRequiredstringMinimum characters: 1Maximum characters: 1024
page_tokenOptionalstringMinimum characters: 1Maximum characters: 2048
start_timeRequiredstringMaximum characters: 64
Google Docs File Get Read
Inputs for Google Docs File Get
InputRequirementAccepted value
file_idRequiredstringMinimum characters: 1Maximum characters: 1024
Google Docs Comment Get Read
Inputs for Google Docs Comment Get
InputRequirementAccepted value
comment_idRequiredstringMinimum characters: 1Maximum characters: 1024
file_idRequiredstringMinimum characters: 1Maximum characters: 1024
Google Docs Reply Create Action
Inputs for Google Docs Reply Create
InputRequirementAccepted value
comment_idRequiredstringMinimum characters: 1Maximum characters: 1024
contentRequiredstringMinimum characters: 1Maximum characters: 32768
file_idRequiredstringMinimum characters: 1Maximum characters: 1024
Docs Get Document Read
Inputs for Docs Get Document
InputRequirementAccepted value
document_idRequiredstringMinimum characters: 1Maximum characters: 1024
Docs Create Document Action · approval required
Inputs for Docs Create Document
InputRequirementAccepted value
titleRequiredstringMinimum characters: 1Maximum characters: 512
Docs Batch Update Action · approval required
Inputs for Docs Batch Update
InputRequirementAccepted value
document_idRequiredstringMinimum characters: 1Maximum characters: 1024
requestsRequiredarrayMinimum items: 1Maximum items: 100

When the Google Docs task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the oauth connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Google Docs connector

Can I use my existing agent with Google Docs?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Google Docs?

This connector supports 1 action, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Google Docs?

Prepare Client ID, Client secret, Access token, Refresh token; the connection uses OAuth, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Google Docs keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.