---
title: "Google Drive AI agent in Slack: find and read files in a channel | Chickpea"
description: "Give a Slack channel an AI teammate connected to Google Drive. Ask it to find a file, read it, and answer from it. Four capabilities, three of them reads."
canonical: https://chickpea.co/connectors/google-drive
keyword: "Google Drive AI agent in Slack"
verified: 2026-09-17
---

# A Google Drive teammate in Slack that finds files and answers from them.

> Chickpea gives a channel a named AI teammate that holds its own Google Drive connection. It searches My Drive and the shared drives the signed-in account belongs to, opens a file, reads it, and answers in the thread. It can write one thing back, a new text file, and that is the whole of what it changes in Drive.

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

**Google Drive** (Google LLC, https://drive.google.com): Find, read, create, and organize files. 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.

### Find a file by name or by what is in it
- @pm find the vendor agreement we signed with the Vancouver supplier
- @pm which doc has the Q3 headcount plan in it, and who owns it

Reads never need confirmation. The teammate runs a Drive search, reads the metadata for the files that look right, and opens the likely one to check. A search covers My Drive and every shared drive the account belongs to, and returns at most 100 files a page. Several candidates come back as a table with the owner, the last change, and a link.

### Answer a question out of a document
- @pm what does the renewal clause in the Northwind contract actually say
- @pm summarise the incident write-up from Tuesday and list the follow-ups

The teammate reads or exports the one file you meant and answers from it. A result is capped at 256 KB before it reaches the model, so a large file is refused rather than trimmed into a wrong answer. File content is untrusted input. A document cannot instruct the teammate, whoever wrote it.

### What changed in a folder this week
- @pm what was added to the Ops Handbook folder in the last seven days
- @pm list the files in the vendor folder nobody has touched since June

A folder search comes back with names, owners, and modified times, which is what a "what changed" answer is built from. There is no Drive webhook here, so the teammate hears nothing on its own. It looks when you ask, or on a schedule you set.

### Write the answer back into Drive
- @pm write this thread up as a file called Vendor decisions and put it in my Drive
- @pm save the checklist we just agreed as a text file

A new file is small and reversible, so it applies at once. The teammate creates one text-backed file, up to 100,000 characters, in the root of the connected account's Drive, and it starts private to that account. The reply names the file and links it. Moving it, renaming it, and sharing it are not in the capability list, so those stay yours to do in Drive.

### On a schedule
- @pm every Monday at 9am Pacific, list what was added to the Ops Handbook folder last week
- @pm every Friday at 4pm Eastern, post the files in the vendor folder that changed this week

A schedule saves on the spot. It needs an explicit time zone, and "every Monday at 9am" without one is refused rather than guessed. Each run uses the Google Drive connection of the person who asked. Before every run Chickpea re-reads the teammate, the channel grant, and that connection, and a missing one fails the run with a named reason.

### Example conversations

**Find the file**
> **Dana:** @pm where is the signed vendor agreement for the Vancouver supplier?
> **@pm:** Four files match. The signed one is Vendor agreement, Halvorsen Supply, 2026 in Ops / Contracts. The other three are drafts.
>
> | File | Folder | Owner | Last change |
> |---|---|---|---|
> | Vendor agreement, Halvorsen Supply, 2026 (signed) | Ops / Contracts | Priya | Aug 14 |
> | Vendor agreement, Halvorsen, draft 3 | Ops / Drafts | Marco | Aug 11 |
> | Halvorsen terms, redline | Ops / Drafts | Priya | Aug 8 |
> | Vancouver suppliers, shortlist | Ops | Dana | Jun 2 |
> **@pm:** I opened the signed one to check the counterparty name. Reads like this need no approval, and nothing in Drive moved.

**Write it back into Drive**
> **Priya:** @pm write this thread up as a file called Vendor decisions, September.
> **@pm:** Created Vendor decisions, September in the root of my Drive, 1,240 words. It holds the four decisions from this thread and who made each one.
> **@pm:** A new file is small and reversible, so it went straight through. It is private to my account until you move or share it, and I cannot do either of those.

**Twelve of them at once**
> **Marco:** @pm write up each of the twelve supplier threads from this month as its own file.
> **@pm:** Twelve files, one per supplier, in the root of my Drive. That is a bulk change, so read the list first.
> Buttons: Create the twelve files · Cancel
> **@pm:** Your message has to name the change for me to make one. Nothing in the thread above, and nothing I remember, can stand in for that.

**Every Monday**
> **Sofia:** @pm every Monday at 9am Pacific, list what was added to the Ops Handbook folder last week.
> **@pm:** Saved. Every Monday at 9:00 AM Pacific I’ll search the Ops Handbook folder for files added or changed in the previous seven days and post them here in #ops. First run is Mon Sep 21.
> **@pm:** It runs on your Drive connection. Disconnect that account and it stops with a reason rather than running on someone else’s.

## Connect Google Drive
1. In Chickpea Admin, open the teammate, then **Connections**, find **Google Drive**, and choose **Connect**. Or ask in Slack, `@pm connect Google Drive`, and follow the link it posts.
2. Choose who uses it. **Personal** means each member signs in as themselves, which fits a channel where people keep work in their own My Drive. **Team** is one shared Google account, which fits a team whose files live in a shared drive that account belongs to. A team account needs the Owner or Admin role.
3. Choose **Continue to sign in**. A hosted Google 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, never in Slack, and there is no token to paste anywhere in this connector.
4. Read the permissions on Google's screen before approving. The grant Google shows you can be wider than the four capabilities Chickpea hands the teammate, and approving it does not widen the teammate.
5. Ask something. Drive needs no selection step after sign-in, so it is ready immediately. `@pm find the vendor agreement we signed last quarter` is a good first question, because it only reads.

A connection belongs to one teammate. Giving a second teammate Google Drive means a second sign-in with its own consent, so the support teammate never inherits the files the ops teammate can reach. Each Google service is its own connection and its own consent screen, so Drive, Docs, and Sheets are connected one at a time.

## What the teammate is handed with Google Drive
A managed connector has no discovered tool list. The teammate is handed a fixed list of capabilities that Chickpea curates, not Google's whole Drive API. Four cover Google Drive: search files and folders, read one file's metadata, read or export one file, and create a text file. Three of the four read. Nothing in the list moves, renames, copies, shares, changes permissions on, trashes, or deletes a file, and there is no raw API passthrough to reach around it.

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

## Beside Google Drive
- **Google Docs:** Drive finds the document, Docs reads its structure and edits it
- **Google Sheets:** The file the teammate found, and the numbers inside the sheet beside it
- **Notion:** The archive lives in Drive, the page people actually read lives in Notion
- **Asana:** A file someone asked about becomes an owned task with a due date
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Is there an MCP for Google Drive?
Yes, and Google runs one. Google documents a remote Drive MCP server at drivemcp.googleapis.com/mcp/v1, which it describes as letting AI agents interact with Google Drive data. Its reference lists eight tools: copy_file, create_file, download_file_content, get_file_metadata, get_file_permissions, list_recent_files, read_file_content, and search_files. Setting it up takes a Google Cloud project, the Drive and Drive MCP APIs enabled, an OAuth consent screen, and a client configuration. Google names Antigravity and Claude as clients, and the server sits in its Workspace Developer Preview Program.

### Does it use Google's MCP server?
No. Google Drive is a managed connector here, and nothing in it speaks MCP. The teammate is handed four curated capabilities that reach Drive through the Google account you signed in with. There is no server address to configure, no Cloud project, and no client config file. Google's server puts Drive in one person's editor or chat client. This puts it in a channel, where the answer is visible to everyone who can read the thread.

### Is there an AI for Google Drive?
Google sells one. Gemini in Drive, by Google's own description, researches across several files, searches and retrieves files through AI Overviews, summarises files and folders, creates content, images and audio overviews, and organises files. Google says you need an eligible Google Workspace or Google AI plan to use it. It lives inside Drive. A Chickpea teammate lives in a Slack channel, holds other accounts beside Drive, and answers where the conversation already is.

### Can it delete a file?
No. The Drive capability list has four entries and none of them deletes, trashes, or empties anything. Under the 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 your current message names that action. A capability that does not exist cannot be named into existence.

### Can it move, rename, or share a file?
No, and that is the real limit of this connector. The four capabilities search, read metadata, read or export a file, and create a text file. Moving a file between folders, renaming one, copying one, changing who can see it, and starring one are all absent. Ask the teammate to find and read, and do the filing yourself. When the work is inside a document rather than around it, give the teammate Google Docs or Sheets as well.

### Which files can it see?
Whatever the connected Google account can see. A search covers My Drive and every shared drive that account belongs to, so a team account reaches the shared drives it was added to and nothing else. Chickpea never widens that. Choose a personal connection if you do not want everyone who can use the teammate reading through one shared account, and check Google's consent screen when you sign in, because the grant there can be wider than the four capabilities.

### How much of a file can it read?
A managed result is capped at 256 KB before it reaches the model, and a read above that is rejected rather than silently cut. A search returns at most 100 files a page, with a cursor for the next one. A file the teammate creates carries at most 100,000 characters of text. The limits live in the input schemas rather than in a prompt, so no amount of asking moves them.

### Do I still need the Google Drive app for Slack?
Most teams want both, because they run in opposite directions. Slack's Google Drive app pushes out: it shows a rich preview when someone posts a file, creates a new Doc, Slide or Sheet from Slack, brings an existing file into a channel, prompts you to fix permissions when members cannot open what you shared, notifies you when someone comments on your file, requests access, or shares one with you, and lets you reply to those comments from Slack. A Chickpea teammate posts nothing unprompted. It waits to be asked, searches across the Drive it is connected to rather than the files already pasted into Slack, and answers in the thread.

### How do I connect Google to Slack?
For Slack's own Drive app, one person installs it to the workspace and everyone else connects their account. For a Chickpea teammate, open the teammate in Admin, choose Google Drive, pick personal or team, and finish the Google sign-in in the tab that opens. Or ask in the channel, "@pm connect Google Drive", and follow the link it posts. Drive asks for no resource selection afterwards, so it works as soon as the sign-in finishes.

### Which Google plan does this need?
Google names no plan for this. What the teammate can read is what the Google account you signed in with can read, so seats and sharing inside your Workspace decide the rest. Google does name plans for two neighbouring things worth keeping straight: Gemini in Drive needs an eligible Google Workspace or Google AI plan, and Google's Drive MCP server is part of its Workspace Developer Preview Program. Neither is involved here.

## Sources
- [Chickpea docs: connector catalog, the managed lane and what Drive asks you to select](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: managed connectors, the sign-in flow and the read-and-write lanes](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 sign-in flow 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 four Google Drive capabilities and their input schemas](https://github.com/pejmanjohn/chickpea/blob/main/src/connections/catalog/google-workspace.ts)
- [Chickpea source: the Google Drive preset (managed toolkit, provider, category)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Google: configure the Drive MCP server, its address, tools and named clients](https://developers.google.com/workspace/drive/api/guides/configure-mcp-server)
- [Google: the MCP reference for drivemcp.googleapis.com](https://developers.google.com/workspace/drive/api/reference/mcp)
- [Google: get started with Gemini in Google Drive, and the plans it needs](https://support.google.com/drive/answer/16686008)
- [Slack help: Google Drive for Slack, its previews, notifications and comment replies](https://slack.com/help/articles/205875058-Google-Drive-for-Slack)
- [Slack Marketplace: the Google Drive app listing and its feature list](https://slack.com/marketplace/A6NL8MJ6Q-google-drive)
- [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 Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.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