---
title: "Google Docs AI agent in Slack: read, summarize, and write documents | Chickpea"
description: "Give a Slack channel an AI teammate connected to Google Docs. Ask it to summarize a document, find what the docs say, or draft the next one. Open source."
canonical: https://chickpea.co/connectors/google-docs
keyword: "Google Docs AI agent in Slack"
verified: 2026-09-17
---

# A Google Docs teammate in Slack that reads your documents and drafts the next one.

> Chickpea gives a Slack channel a named AI teammate that holds its own Google Docs connection. It finds the documents the connected Google account can open, reads them, and answers in the thread. It also writes: a new document from a Slack thread, or a section replaced in one you named. Sharing a document, changing who can see it, and deleting one are absent from the list it is handed.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/google-docs; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Google Docs** (Google LLC, https://docs.google.com): Find, read, export, create, and update documents. Category: Docs and files. Lane: Hosted sign-in. Sign in: OAuth, managed.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @pm, published to #ops.

### Summarize a document
- @pm summarize the Q4 ops plan doc and list what is still open
- @pm what does the onboarding guide say about the trial, in three lines

Reads never need confirmation. The teammate finds the document, then reads it as bounded plain text, with tables, headers, footers, and footnotes kept in or left out. A result over 256 KB is refused rather than quietly trimmed, so a very long document comes back as a narrower question instead of half an answer.

### Find what the documents say about something
- @pm which onboarding docs mention the 30-day trial, and what do they say
- @pm find where we wrote down the vendor escalation path

Search takes a phrase and returns up to a hundred documents a page, and the teammate reads the ones that matter. A long answer comes back as a table in the thread. Document text is untrusted content, so an instruction written inside a document cannot tell the teammate to do anything.

### Turn a thread into a document
- @pm turn this thread into a doc called Vendor review notes, decisions first
- @pm write up the incident as a doc with a timeline and the follow-ups

A new document is a small write, so it applies at once and the reply names what it made. The teammate can create a plain-text document or build one from Markdown, up to 100,000 characters. It lands in the Drive of the connected account, and sending the link is your job, because sharing is not a capability here.

### Append or replace a section
- @pm add a Status section to the four launch docs saying the date moved to Nov 3
- @pm replace the Timeline section in the launch plan with the new dates

Three capabilities edit a document that already exists: insert text at the end or at an explicit position, replace one section between two positions, and replace a whole tab. Replacing overwrites what was there, and several documents at once is a broad change, so it comes back as a list of what would change and waits for a yes. Google Docs version history is the way back.

### On a schedule
- @pm every Monday at 9am Pacific, post a summary of the Ops weekly doc here
- @pm every Friday at 4pm Eastern, list the open questions in the launch plan

A schedule saves on the spot. It needs an explicit time zone and runs under the Google connection of the person who asked. Before each run Chickpea re-reads the teammate, the channel grant, and that connection, and a missing one fails the run with a named reason. A digest of everything that changed in a folder wants the Google Drive connector beside this one, because the Docs search takes a phrase rather than a folder.

### Example conversations

**Summarize a document**
> **Dana:** @pm summarize the Q4 ops plan doc. What did we decide and what is still open?
> **@pm:** Q4 ops plan, 11 pages, last edited Monday. Decided: the Vancouver move goes ahead in November, headcount stays flat, and the vendor review runs before renewals.
> **@pm:** That is the document text, headings, tables, and footnotes. Reading changed nothing in the doc.

**What do the docs say**
> **Priya:** @pm which of our onboarding docs mention the 30-day trial, and what do they say about it?
> **@pm:** Four documents name it, and two of them disagree with each other.
>
> | Document | Section | What it says |
> |---|---|---|
> | Northwind onboarding guide | Getting started | 30 days, starts on the first sign-in |
> | Sales handover notes | Trials | 30 days from the contract date |
> | Support macros | Trial expiry | Extendable once, by 14 days |
> | Pricing one-pager | Footnote 2 | No card required during the trial |
> **@pm:** The handover notes are the odd one out. Document text is treated as content, not as instructions to me, so anything written in there asking me to act is ignored.

**Turn a thread into a doc**
> **Marco:** @pm turn this thread into a doc called Vendor review notes, with the decisions at the top.
> **@pm:** Created Vendor review notes. Decisions first, then the open questions, then the thread in order with who said what. It sits in the Drive of the account I am connected to.
> **@pm:** A new document is a small write, so it applied on the spot. Sharing is not something I can do, so send the link yourself or add people in Docs.

**Edit four docs at once**
> **Sofia:** @pm the launch moved to Nov 3. Update the date section in the four launch docs.
> **@pm:** Four documents, one section each. Here is what I would replace, and what the section says today.
>
> | Document | Section | Now | After |
> |---|---|---|---|
> | Launch plan | Dates | Oct 20 | Nov 3 |
> | Support readiness | Timeline | Week of Oct 20 | Week of Nov 3 |
> | Comms brief | Key dates | Oct 20, embargo Oct 17 | Nov 3, embargo Oct 31 |
> | Field FAQ | When does it ship | late October | Nov 3 |
> Buttons: Apply the four edits · Cancel
> **@pm:** Replacing a section overwrites what is in it, and four documents is a broad change, so this waits for you. There is no undo inside Docs from here; version history in Google Docs is the way back.

**Every Monday**
> **Dana:** @pm every Monday at 9am Pacific, post a summary of the Ops weekly doc here.
> **@pm:** Saved. Every Monday at 9:00 AM Pacific I’ll read Ops weekly and post its decisions and open items, here in #ops. First run is Mon Sep 22.
> **@pm:** It runs on your Google connection and reads only. Disconnect that account and it stops with a named reason rather than running on someone else’s.

## Connect Google Docs
1. In Chickpea Admin, open the teammate, then **Connections**, find **Google Docs**, and choose **Connect**. Or ask in Slack, `@pm connect Google Docs`, and follow the link it posts.
2. Choose who uses it. **Team** is one shared Google account that everyone who can use the teammate works through, and it needs the Owner or Admin role. **Personal** means each member signs in as themselves and reaches only the documents their own account can open.
3. Choose **Continue to sign in**. A hosted sign-in opens in a second tab while Chickpea waits in the first, and the attempt lasts 30 minutes. You sign in to Google there. There is no token to paste anywhere in this connector, and nothing goes into Slack.
4. Read the permissions on Google's screen before approving, because that grant can be wider than the capabilities Chickpea hands the teammate. There is nothing further to pick afterwards. Google Docs asks for no resource selection, so the connection is usable as soon as sign-in finishes.
5. Ask something. `@pm summarize the Q4 ops plan doc` is a good first question, because it only reads and nothing in the document changes.

A connection belongs to one teammate. Giving a second teammate Google Docs means a second sign-in with its own consent, so the support teammate never inherits what the ops teammate can open. Each Google service is its own connection and its own consent screen, so Docs, Drive, and Sheets are three of them.

## What the teammate is handed with Google Docs
A managed connector has no discovered tool list. The teammate is handed a fixed list of capabilities that Chickpea curates, not the whole Google Docs API. Nine cover Google Docs. Four read: search the documents the account can open, read one document's structure, read it as bounded plain text, and export it as a PDF. Five write: create a document, create one from Markdown, insert text at the end or at an explicit position, replace a section, and replace one tab's content. Sharing, permission changes, deletion, and arbitrary batch requests are absent from the list.

The capability list is in the product source: https://github.com/pejmanjohn/chickpea/blob/main/src/connections/catalog/google-productivity.ts

## Beside Google Docs
- **Google Drive:** Drive finds the file in a folder, Docs reads and edits what is inside it
- **Google Sheets:** The write-up in a document, the numbers it quotes in a sheet
- **Notion:** Half the team writes in Docs and half in Notion, one teammate reads both
- **Granola:** The meeting notes on one side, the document they turn into on the other
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Do I still need the Google Drive app for Slack?
Most teams want both, and there is no separate Google Docs app for Slack; documents ride on the Drive one. Slack says its Google Drive app lets you create, share, and access Google Drive files from your workspace, covering documents, presentations, and spreadsheets. It notifies you when someone comments on your files, requests access, or shares one with you, it lets you reply to comments, and it shows a rich preview when a file link is pasted. One member installs it and each person connects their own Google account. Keep it for links, previews, and notifications. A Chickpea teammate hears nothing from Google and posts nothing unprompted. It sits in the channel, reads the documents when asked, and writes the next one.

### Is this Gemini in Google Docs?
No, and they sit in different places. Google describes Gemini in Docs as a side panel you open with Ask Gemini, where it writes and edits, summarizes, refines and rewrites, adjusts tone, generates images, and references your other files. Google says that feature requires an eligible Google Workspace or Google AI plan. It lives inside the document, with one person in front of it. A Chickpea teammate lives in a Slack channel, holds other accounts beside Docs, and answers where the conversation already is. Gemini keeps working exactly as it does now.

### Does it use Google's Docs MCP server?
No. Google Docs is a managed connector here, and nothing in it speaks MCP. Google does run one: its developer docs describe a remote Docs MCP server at docsmcp.googleapis.com with two tools, read_doc and update_doc, which you set up by enabling APIs in a Google Cloud project, configuring an OAuth consent screen, creating client credentials, and pasting a server block into a client such as Antigravity or Claude. That puts Docs in one person's client. This puts it in a channel, with no project to create and no config file to edit.

### Can it change anything in Google Docs?
Yes, within the five write capabilities: create a document, create one from Markdown, insert text, replace a section, and replace a tab. Minor reversible writes may proceed; broad ones wait for a yes. Under that judgment sits a gate that does not consult the model. During a Slack turn Chickpea refuses any managed capability whose effect is not read unless the message you just sent names that action, so thread history, a pasted document, and memory cannot authorize a write on their own.

### Can it delete a document?
No. Deletion is not in the capability list, and neither is sharing a document, changing who can see one, nor an arbitrary batch request against the Docs API. What it can overwrite is text inside a document you named, when you replace a section or a tab, and that comes back for confirmation when it is broad. Google Docs keeps version history, which is the way back from an edit you did not want.

### Which documents can it see?
The ones the connected Google account can open. There is no resource selection on this connector, unlike Search Console, Analytics, and Gong, which stay pending until an Admin picks sites, properties, or workspaces. So the account is the boundary. A team account is one shared sign-in that everyone who can use the teammate works through, so choose personal if you want each member to reach only their own documents.

### What does bounded mean on this connector?
Limits written into the input schema rather than left to the model. A search returns at most 100 documents a page. The text of a created or replacing document is capped at 100,000 characters. Inserting text needs either the end of the document or an explicit position, and replacing a section needs an end position after its start. Every result is capped at 256 KB, and a bigger one is refused rather than trimmed, so nothing comes back silently shortened.

### Can it export a document as a PDF?
Yes. Exporting one document as a PDF is one of the four read capabilities, beside search, reading the structure, and reading the plain text. Posting the file back into Slack is itself one of the actions behind the gate, so it happens because you asked for it in the message you sent, not on the teammate's own initiative.

### How do I sync Google with Slack?
Nothing is synced or copied here, which is the point. The teammate holds a Google Docs connection and opens a document at the moment you ask about it. Each Google service is its own connector and its own sign-in, so Docs, Drive, Sheets, Slides, Gmail, and Calendar are six separate connections, and one teammate can hold several of them at once. If what you want instead is file links, previews, and comment notifications flowing into a channel, that is Slack's Google Drive app, and the two sit happily side by side.

## Sources
- [Chickpea docs: connector catalog, the Google Docs row and the managed lane](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: managed connectors, the sign-in flow and what each connector selects](https://docs.chickpea.co/agents/managed-connectors/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the managed-capability effect gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, the hosted sign-in and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the nine Google Docs capabilities and their input schemas](https://github.com/pejmanjohn/chickpea/blob/main/src/connections/catalog/google-productivity.ts)
- [Chickpea source: the Google Docs preset (managed toolkit, provider, category)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Google: configure the Docs MCP server, its two tools and its prerequisites](https://developers.google.com/workspace/docs/api/guides/configure-mcp-server)
- [Google: write and edit with Gemini in Docs, and the plan it requires](https://support.google.com/docs/answer/14206696)
- [Slack: the Google Drive app for Slack, its previews, notifications and file creation](https://slack.com/help/articles/205875058-Google-Drive-for-Slack)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co