Bob with Google Drive: find the source, then finish the job

Matthew, founder of Bob · Published July 30, 2026

Short answer

Bob's Google Drive connection lets him search accessible files, read their contents, copy a file, and upload a UTF-8 text file. The connection follows the permissions of the Google account that connected it. It is useful because Drive often contains the missing source for work that begins somewhere else.

Google documents both file search and file creation and copying in the Drive API. Bob packages the useful subset into Slack-native work with approval gates on changes.

Five useful Bob and Google Drive workflows

1. Find the latest version

"Find the most recently modified launch brief in Drive and summarize the decisions that changed this week."

Giving Bob a title fragment, owner, folder, or date range makes the search more reliable.

2. Ground a customer reply

"Read the Acme implementation plan in Drive and their latest Gmail thread. Draft a reply that answers the open questions."

Bob uses Drive as the source, Gmail as the conversation, and keeps the send behind approval.

3. Prepare a meeting brief

"For tomorrow's roadmap review, read the strategy doc and summarize the unresolved decisions in the calendar thread."

This turns a file repository into context delivered at the moment it is needed.

4. Copy a working document

"Copy the approved kickoff template for the Northstar project. Do not change the original."

Copying is a Drive write, so Bob presents the action for approval by default.

5. Save a generated artifact

"Turn this incident timeline into a clean Markdown report and upload it to the incident folder."

The current upload path is intentionally specific: Bob can upload UTF-8 text content. It is not a promise of arbitrary binary conversion.

How the connection works

1. Ask Bob in Slack to connect Google Drive.
2. Open the hosted OAuth flow and sign in with Google.
3. Review the requested access and choose the right account.
4. Return to Slack and ask Bob to retry the file request.

Bob's purpose-built Drive connection is personal. Search results and reads are bounded by what that account can already access, including shared files visible to it.

Limits worth knowing

• No domain-wide visibility. Bob cannot bypass Drive sharing rules.
• No promise of arbitrary document editing. The current path supports search, read, copy, and UTF-8 upload.
• Duplicate names need disambiguation. Owner, folder, and modified date help Bob select the right source.
• Writes ask by default. Copying and uploading change Drive and remain reviewable.

FAQ

What can Bob do with Google Drive?

Bob can search and read accessible files, copy a file, and upload UTF-8 text through the purpose-built connection.

Can Bob see every file in our company?

No. Bob sees only the files available to the connected Google account.

Can Bob edit any Google Doc?

Do not assume that. The current Drive actions focus on search, reading, copying, and text upload.

Does Bob ask before creating a file?

Yes. A copy or upload asks by default unless a matching standing policy has been granted.

Start with a file your team keeps hunting for

Ask Bob to find and summarize it. Once the source is right, connect Gmail, Google Calendar, or Google Sheets to finish the surrounding job.