Integration · Docs and data
AI agents for Google Docs
Create Google Docs documents, read their text, and add text to the end of them, signed in with the person's own Google account.
- Actions
- 3
- Read
- 1
- Write
- 2
Actions
What your agents can do in Google Docs
3 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 1
Look things up. Nothing changes.
Read a document
Reads a document's title and the text of its body (the first tab), as the Docs body JSON cut down to text.
Write 2
Create, change or send.
Create a document
Creates a blank Google Docs document with a title; any other content is ignored, so use Append text to fill it.
Append text
Adds text at the end of a document's body, generally in the style of the text before it.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Sign in with Google and approve access (OAuth).
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Google Docs data
Ask a question in plain words. The agent can read a document in Google Docs, then answers with what it found.
- 02
Let an agent update Google Docs
Have the agent create a document or append text in Google Docs as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Google Docs and Slack: it can read a document in Google Docs and post a summary to a Slack channel in the same run.
Works well with
More Docs and data tools
- Google Sheets3 actionsAdd rows to a Google Sheets spreadsheet, read a range of cells, and write over a range, signed in with the person's own Google account.
- Notion4 actionsAdd pages to Notion databases, append text to pages, query databases and search the pages shared with an internal integration.
- Confluence4 actionsCreate, read and search Confluence Cloud pages on your Atlassian site, signed in with an email address and an API token.
- Airtable4 actionsCreate, update, list and read records in Airtable bases that a personal access token can reach.
- Docusign3 actionsSend documents for signature from a Docusign template, check an envelope's status and list recent envelopes, as the person who connects.
- Adobe Acrobat Sign12 actionsSend agreements for e-signature from Acrobat Sign library templates, follow their status, signers and audit events, read form data, send reminders and cancel, as the Acrobat Sign user who connects.
FAQ
Google Docs and MyDeepAgents
Can MyDeepAgents connect to Google Docs?
Yes. The Google Docs connector has 3 actions: 1 reads and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Google Docs?
Sign in with Google and approve access (OAuth). Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Google Docs without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.
Can I use Google Docs in workflows as well as agents?
Yes. Every Google Docs action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Google Docs to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.