Grok Bot Gmail connector can list attachments but cannot download their bytes

Ideas Feature Requests
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

I have a daily Grok Bot job, that downloads a daily csv attachment from my gmail.

The Gmail connector finds the message and returns attachment metadata (filename, MIME type, attachment id)but it never returns the file. There is no download-attachment tool. The only working path is opening Gmail in a browser and clicking Download.

Steps to Reproduce

Gmail connector authenticated and status ready.
search_threads for a recent message with a CSV attachment.
get_message with that messageId and messageFormat=FULL_CONTENT.
Response lists the attachment (filename, application/octet-stream or text/csv, plus a long attachment id). No content / bytes field.
Same call with messageFormat=RAW returns the MIME as base64, then the tool result is truncated (this run: full payload 163,005 bytes, inline limit 40,000, remainder discarded). Inline images in the email make RAW too big to use as a download path.
Tool catalog has no get_message_attachment / download_attachment. Attachment schema comments mention a GetMessageAttachment request, but that RPC is not exposed.
Workaround: open Gmail in the browser and click the attachment Download button. File landed at 9:09:56 AM MYT, 47,511 bytes.

Expected Behavior

Given a message id and attachment id, return or write the exact attachment bytes.

Screenshots / Screen Recordings

SCR-20260824-lgdc.png
SCR-20260824-lgdc.png1580×1406 225 KB

Operating System

Other

Version Information

Version: 0.24.0
Release Track: stable
OS: darwin

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @iSlyy0717, thanks for the detailed report!

Indeed, The Gmail connector currently only exposes attachment names and metadata, not the file contents; there’s no download tool in the connector’s catalog today. This is a known gap we’re tracking, and I’ve added your report.

In the meantime, the browser path you found is the most reliable workaround; alternatively, if you can get that CSV routed into Google Drive (e.g. a Gmail filter plus a small Apps Script that saves attachments to a Drive folder), the Drive connector can download file contents directly, which would keep your daily job fully automated.

8

Thank you for your quick response!

I humbly request the lovely people at the spacexai team to create a page where I can keep up with grok bot changelogs, so I can best monitor updates and reflect my workflows accordingly