# Walk into the call. With the full picture.

Source: https://corespeed.io/integrations/gmail-google-drive

Prepare for a customer call with Gmail and Google Drive in one request. Through CoreSpeed, your agent reads the latest email thread and the working Google Doc, then hands back one meeting brief with the request, the timeline constraints and the questions to settle first. It drafts in your agent and sends or edits nothing.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Gmail and Google Drive after setup. Each account needs its own authorization. Create an account: https://app.corespeed.io/sign-up

## Know what changed. Know what to ask

Bring the latest customer request and the working project context into one brief. Unresolved questions stay visible.

You ask your agent: "Read the latest Acme emails in Gmail and the rollout Google Doc in Drive. Prepare a meeting brief covering the request, timeline constraints, and open questions. Do not send or change anything."

It calls CoreSpeed:

- `gmail__search_emails`: ok, 412 ms
- `google-drive__list_files`: ok, 357 ms
- `google-drive__export_file_text`: ok, 1184 ms

It reads from: Gmail, Google Drive.

### Meeting brief: Acme, before the call.

Acme wants a rollout date. The Google Doc lists a customer data handoff as a prerequisite, and its date is still open.

**Bring into the call**

- Explain the data-handoff prerequisite.
- Review the proposed rollout sequence from the Google Doc.

**Resolve before committing**

- Who owns the data handoff?
- When can that handoff be confirmed?

_Illustrative result from fictional sources · Nothing sent or changed_

Gmail on its own: https://corespeed.io/integrations/gmail

## A useful brief starts with the right context

Requests you can make once Gmail and Google Drive are connected. The data is fictional.

### Latest customer request

Acme · rollout question · Gmail

- Request: Confirm the proposed rollout date
- Question: Is the revised plan ready?
- Illustrative source · Fictional data

### Working document

Acme · rollout Google Doc · Google Drive

- Prerequisite: Customer data handoff
- Constraint: Handoff date still unconfirmed
- Illustrative source · Fictional data

### One result to review

Meeting brief · Draft in your agent

- Bring into the call: Explain the data-handoff prerequisite.
- Resolve before committing: Who owns the data handoff?
- Nothing sent or changed

## Keep your agent. Bring the context

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Gmail and Google Drive**: Authorize each account and the content this task needs.
3. **Ask for a meeting brief**: Name the project or conversation, then review the result.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Does this record or transcribe meetings?

No. It prepares a brief before a meeting from connected work data. It is not a recorder, a transcription service, or a calendar bot.

### Do I need both connections?

Yes. This example combines Gmail and Google Drive. Connect both, or start from one app: an agent cannot use data it cannot access.

### Can this read every file format in Drive?

No. Text export covers Google Docs, Slides, Sheets, and text files. It does not extract text from every PDF or Office document.

### Does this send or change anything on its own?

No. These examples read context and draft a result. Sending or changing a record is a separate tool call, which approvals can hold for a person. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

## Related pages

- [Meeting prep with Gmail and Notion](https://corespeed.io/integrations/gmail-notion): Bring the latest Gmail conversation and your Notion project notes into one meeting brief, inside your agent.
- [Gmail for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gmail): Catch up on email threads and prepare thoughtful replies, right inside the agent you already use.
- [Google Drive for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/google-drive): Find the project document in Google Drive, read its context, and turn it into a brief inside your agent.

## Sources

- Connectors: https://corespeed.io/docs/connectors

Reviewed 2026-11-07.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)