Coco + Google Calendar

Connect Google Calendar and Coco watches your meeting schedule. It prepares a pre-meeting brief for every external meeting, drafts the post-meeting follow-up email after the call, and proposes scheduling when you're trying to book new meetings. Calendar writes — creating events, modifying times, sending invites — gate on your approval at the start. Reads are free of approval, but Coco only reads the calendars you've granted scope to. About 8 credits per pre-meeting brief.

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

What Coco does with Google Calendar today

The integration is a read-heavy surface with approval-gated writes. Coco watches the calendar, generates the artifacts the calendar implies, and only writes when you've explicitly approved.

Watches your schedule for external meetings. Coco identifies which upcoming meetings are external (anyone outside your domain on the attendee list), which are recurring internal, and which are personal/blocked. The external set is what triggers the pre-meeting workflow.

Prepares a pre-meeting brief. The morning of the meeting — or 1 hour before, depending on what you configure — Coco assembles a brief from the connected attendees' CRM records, the related deal or opportunity, recent conversations on the thread, the company's recent public activity, and any associated notes in Notion or your playbook. The brief lands in your inbox. You read it in five minutes instead of pulling context for thirty. About 8 credits per brief. See prep sales meetings →.

Drafts the post-meeting follow-up. After the meeting (Coco watches for the end-time + buffer), it drafts the follow-up email pulled from the meeting context and any notes you took, queued in your Gmail Drafts folder for review. About 4-6 credits per draft. See automate follow-ups →.

Proposes scheduling for new meetings. When you ask Coco to set up a meeting — "find a time next week for the Mercury team and book a 30-minute call" — it reads availability across your granted calendars and proposes specific times. Coco doesn't create the event until you approve. The actual invite send is approval-gated.

Reads availability for outreach time suggestions. When Coco drafts outreach that proposes a specific time ("Tuesday 2pm PT works for me"), it pulls availability from your calendar to make sure the suggestion is real, not invented.

Excludes private and internal-only events. Coco respects calendar visibility. Events marked private aren't read into briefs. Internal-only standing meetings can be excluded from the briefing workflow entirely.

How to connect

OAuth flow, two minutes.

1. Go to /app/integrations.
2. Pick Google Calendar.
3. Run the Google OAuth flow. Grant scope to the specific calendars you want Coco to read (you can connect more than one — work calendar, shared team calendar, etc.).
4. Optional: grant write scope if you want Coco to create events and send invites on your behalf (still approval-gated per event).
5. Configure brief delivery — morning-of, 1-hour-before, or custom windows.

Coco confirms the connection and tests read access by listing upcoming external meetings. If the list looks right, you're set.

Approval gates by action type

Once a workflow is proven — say, "always generate pre-meeting briefs for external calls" — the trigger runs autonomously. The output still lands as a reviewable artifact, not a sent action. Calendar-side writes (creating events, sending invites) keep the approval gate by default because they're externally visible.

Workflows that use Google Calendar

Calendar is the trigger surface for nearly all of Coco's meeting-related work. The workflows that lean hardest:

• Prep sales meetings → — pre-meeting briefs assembled from CRM, thread, and public data.
• Automate follow-ups → — post-meeting follow-up drafts queued in Gmail.
• Cross-tool meeting orchestration — when paired with Gmail → and your CRM, Coco runs the full meeting workflow from prep through follow-up and CRM update (the meeting itself stays with you).

Each workflow uses the calendar as the trigger and pulls context from the rest of the connected stack.

How this pairs with Calendly

Some teams book meetings via Calendly; others rely on direct calendar coordination. Coco supports both.

When Calendly → is connected, Coco reads availability through Calendly's surface and can propose specific times in outreach drafts that match what's actually bookable on your Calendly link. When a Calendly booking happens, the resulting calendar event triggers Coco's pre-meeting brief workflow the same way a manually-created event would.

When only Google Calendar is connected, Coco reads availability directly and proposes times in outreach. The booking still happens through whichever channel you use (reply with a time, send a Calendly link, etc.) — Coco's calendar write to actually create the event is approval-gated.

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

Frequently asked questions

When does Coco generate the brief?

Configurable. The defaults are morning-of (delivered around 7am local time for the day's meetings) or 1 hour before each meeting. You can also configure custom windows — say, "always generate briefs for any external meeting added to the calendar within the next 48 hours, delivered immediately upon creation."

Does Coco see all my calendar events?

Only the calendars you grant scope to. If you connect one calendar, Coco only sees that one. If you grant scope to multiple, Coco sees all of them. Events marked private aren't read into briefs even when the calendar is connected. Internal-only standing meetings can be excluded from the briefing workflow via configuration.

Can Coco schedule meetings on its own?

For approved workflows, yes — but the calendar write is still approval-gated by default. The autonomous version looks like: Coco identifies available times, drafts the proposal, sends the proposal email through Gmail (gated), and creates the calendar event once the recipient confirms (gated). The autonomy lives in the orchestration, not the calendar-write itself.

Does this work with multiple calendars?

Yes. You can connect work calendar, shared team calendar, and personal calendar in the same Coco workspace. Coco respects the visibility settings on each — and you can configure which calendars trigger the briefing workflow vs. which are read for availability only.

Does Coco see private events?

Only if you grant scope to a calendar that includes them and the events aren't marked private. Events marked private are read as "busy" for availability purposes but their details are not included in briefs or outreach drafts. See why Coco's privacy posture matters for trust →.

Get started

If your calendar fills up faster than your prep can keep pace with, the integration takes a couple minutes to connect and starts surfacing pre-meeting briefs against the next external meeting on the calendar.

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

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