IntegrationsMeeting prep · Gmail + Google Drive
Walk into the call.With the full picture.
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.
A useful brief startswith the right context.
Requests you can make once Gmail and Google Drive are connected. The data is fictional.
- GmailInbox
- DDiane8:15Can you confirm the proposed rollout date? Is the revised plan ready?
- DDianeOct 14Thanks for the plan. We’ll review it this week.
Latest customer request
Illustrative source · Fictional data
- Google DriveGoogle Doc
Acme · rollout plan
- Prerequisite: customer data handoff.
- Handoff date: not confirmed.
- Rollout: three phases after the handoff.
Working document
Illustrative source · Fictional data
- CodexAnswer
Meeting brief
Acme, before the call.
- Explain the data-handoff prerequisite.
- Who owns the data handoff?
One result to review
Nothing sent or changed
Know what changed.Know what to ask.
Bring the latest customer request and the working project context into one brief. Unresolved questions stay visible.
Reads fromGmailGoogle Drive
Gmail on its own →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.
gmail__search_emailsok
1 thread: Acme asks for a rollout date
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 guidesClaude CodeCodexCursor