Status: Available. Connect Gmail from Settings → Integrations and authorize the labels Corivo should use.
Most replies you send aren't to fresh people; they're to threads that already have history — a project context, a back-and-forth, a person whose preferences you know.
With Gmail connected, Corivo's agent draws on your recent threads as part of its context graph. You'll stop briefing your AI on the email; Corivo can already use the thread.
What Corivo's agent does with Gmail
"Reply to Marc's email." Corivo's agent uses the thread (subject + body + previous replies), who Marc is in the project, and what tone you usually use with him. It can draft a reply you can edit and send.
"Summarize this thread." Corivo can read the full thread from Gmail, including parts that are not currently visible on screen.
"What's outstanding in my inbox?" Corivo surfaces threads waiting on your reply, scoped to authorized labels.
"Draft a response to the customer issue." Corivo combines the email thread with the relevant project context from your connected tools.
What Corivo reads in Gmail
Scoped to what you authorize:
- Recent threads in labels you authorize.
- Subjects, bodies, and participants.
- Send / received metadata.
What Corivo does not do:
- Read your entire inbox if you authorize a narrow set of labels.
- Send mail on your behalf without explicit consent.
- Persist email content to a Corivo server. Your local context graph stays on your machine.
Authorization
You'll authorize Gmail with Google's OAuth flow. The intended pattern is to scope the integration narrowly — for example, only the Inbox and Sent labels, or labels you've curated for a specific project — so Corivo doesn't see more than it needs.