Coco + Gmail

Connect Gmail and Coco drafts your sales emails — cold outreach, replies to active threads, follow-ups after meetings, re-engagement on stale conversations. Every draft pulls context from the thread, the contact's CRM record, and any connected enrichment data. Drafts queue in your Gmail Drafts folder; nothing sends without your approval at the start. Once an approved sequence is proven, you can let Coco queue drafts autonomously — still approval-gated for send by default, or auto-send for narrowly-defined low-risk patterns you've authorized. About 4-6 credits per drafted outreach; about 32 credits for a 5-email send batch.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

What Coco does in Gmail

Coco operates against Gmail through the standard Gmail API surface. Reads context. Writes drafts to your Drafts folder. Sends only with approval.

Drafts cold outreach in your voice. When you ask Coco for first-touch email to a target contact, it pulls from the contact's CRM record, their public activity, and any enrichment data you have on them, then drafts a message grounded in real context. Not "Hope you're doing well" boilerplate. The kind of opening line a human SDR would write after 20 minutes of research. About 4-6 credits per drafted outreach. See draft cold outreach →.

Drafts replies to active threads. When a prospect replies to an outbound thread, Coco reads the full thread context, the deal stage, and any new information surfaced in the reply, then drafts your response. Sits in Drafts for review. Edit inline before send.

Drafts post-meeting follow-ups. After a meeting (read from your connected calendar), Coco drafts the follow-up email grounded in the meeting notes, the deal context, and whatever next-steps the call generated. About 4-6 credits per draft. See prep sales meetings →.

Drafts re-engagement for stalled conversations. When a thread has gone silent past your threshold, Coco surfaces it and drafts a re-engagement message — value-first, not "just following up on this." See reactivate stale deals →.

Runs full sequences. For approved outreach patterns, Coco can queue a multi-touch sequence in your Drafts folder — the first touch, a follow-up at day 3, a second follow-up at day 7, a breakup email at day 14. Each draft is reviewable. About 32 credits for a 5-email send batch (drafting + queuing + the credit tax on cross-tool coordination).

Reads only what's needed. Coco pulls thread context for the specific task. It doesn't index your inbox or train on your private email. Every read is audit-logged.

How to connect

OAuth flow, two minutes.

1. Go to /app/integrations.
2. Pick Gmail.
3. Run the Google OAuth flow. Grant the scopes you want enabled — typically read for thread context plus compose/draft for writing to Drafts.
4. Send scope is optional and per-workflow. If you'd rather Coco never send and only ever draft, leave send scope off.
5. Coco confirms the connection and tests draft creation against a test message.

Works for both personal Gmail and Google Workspace. For shared inboxes, Workspace delegation works as expected — Coco operates within the permissions your account has on the shared inbox.

Approval gates by action type

The default posture is: Coco drafts freely (drafts in your Drafts folder are reversible and reviewable). Send is the line where approval matters. Once you've approved a narrow pattern enough times — say, "auto-send the day-3 follow-up if no reply, only for the design-partner sequence, only between 9am and 5pm PT" — you can graduate that pattern to autonomous send inside those rules.

Workflows that use Gmail

Gmail is downstream of nearly every Coco workflow that touches a human. The ones that lean hardest:

• Draft cold outreach → — first-touch emails grounded in real context, in your voice.
• Automate follow-ups → — drafts queued after reply, silence, or stage change.
• Reactivate stale deals → — value-first re-engagement on silent conversations.
• Prep sales meetings → — pre-meeting context and post-meeting follow-up.

Each workflow uses Gmail as the destination for drafted output and the source of conversation context.

Voice match — how Coco writes like you

Generic AI email is the fast tell that breaks deliverability and reply rate. Coco fights this at two levels.

Sent-history inference (default). Coco reads a sample of your recent sent messages (with your permission, in a one-time setup pass) and infers your default tone, sign-off, paragraph length, and the kinds of openings you actually write. The drafts that follow match the cadence.

Explicit voice training (Founder tier). On the Founder tier, you can run an explicit voice-training pass — Coco analyzes a larger sample, you label which drafts are on-voice vs. off, and Coco tunes for that specific signal. The output is noticeably sharper.

The voice match isn't a marketing claim. It's the difference between drafts you edit and drafts you send. See why Coco isn't a spray-and-pray tool → for the design rationale.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Frequently asked questions

Will Coco send without me approving?

No. By default, drafts queue in your Gmail Drafts folder and gate on your approval at send. Auto-send is only available on workflows you've explicitly authorized, inside guardrails you've defined (time windows, audience scope, content rules). The default posture is draft-then-approve. See the security model → for the full audit trail.

Does Coco read all my email?

No. Coco reads what's needed for the workflow you've asked for — typically the thread or threads relevant to the task. It doesn't index your full inbox, doesn't train on your private email, doesn't read messages outside the assigned scope. Every read is audit-logged and you can revoke at any time.

Can I use this for Google Workspace?

Yes. The Gmail integration covers both personal Gmail and Google Workspace. The OAuth flow is the same; Workspace admins can apply org-level controls if needed.

Does it work for shared inboxes?

Yes, with proper Workspace delegation. Coco operates within the permissions your connected account has on the shared inbox. If your account has send-as permission, Coco can draft from that address (subject to the same approval gate).

What about deliverability?

Coco drafts; your account sends. Deliverability follows your normal sending reputation — Coco doesn't route around your domain or use third-party infrastructure. For high-volume sends, the same hygiene rules apply that govern your normal cold-email motion. Coco is built for quality and approval, not for high-volume spray that would burn deliverability.

Get started

Connect Gmail, hand Coco one concrete email task — a cold outreach for a new target list, a follow-up sweep for stale threads, a post-meeting note for last week's calls. Watch how the draft lands.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Or book a walkthrough → if you'd rather see the Gmail workflow in action first.