August 30, 20262 min read#design

Why every GoogMeetSlack meeting posts to your calendar, not a shared bot's

Meeting-bot accounts hide who scheduled what, split notifications from the humans who own the meeting, and route calendar conflicts through a fake user. Here's the alternative — and why it matters.

Will Steele

Most Slack meeting bots create meetings under a shared service account. You type /meet standup in Slack, the bot creates a Google Calendar event on meetings@yourdomain.com or on the bot's own Google account, and you go about your day.

This is fine right up until it isn't. When it isn't:

The wrong person gets the meeting reminder. Google Calendar sends the "starts in 10 min" push to whoever owns the event. That's the bot. Nobody is watching the bot's phone.
Conflicts are invisible. Calendar's "everyone's free at 3pm" check runs against the organizer's availability. The bot's calendar is always free. The humans in the meeting might not be.
The paper trail is wrong. Six months later somebody wants to know who scheduled the all-hands. Git blame for calendar is meetings@yourdomain.com. Cool.
Meet transcript delivery is scoped to the organizer's Workspace tier. If the bot lives on a cheap plan and the humans are on Enterprise, the transcript feature you're paying for is unavailable to your team.

We built GoogMeetSlack the other way. When you run /meet standup at 3pm in Slack, the meeting is created on your own Google Calendar, under your own account. You're the organizer. The invite comes from your address. Reminders hit your phone. The transcript uses your Workspace's transcription tier.

What this costs

The tradeoff: every teammate has to connect their own Google account once. Two clicks, standard Google OAuth. That's it — no admin has to provision a per-user setup, no Terraform, no service accounts. First time they run /meet they get a "Connect Google Calendar" button; they click it, they're done.

We think one 10-second setup step is a small price for meetings that behave like meetings you scheduled yourself. Because that's what they are.

What this enables

Real conflict detection. Google can now see your calendar when it schedules your meeting. So can everyone else's calendar when it decides whether to auto-decline.
Meeting cancellation from Slack cancels the calendar event. Because the bot has permission to edit your event, not a shared one.
Transcripts land in Slack, but they belong to your Workspace. If your compliance team runs a retention policy on Meet transcripts, our summaries respect it because we're reading through your tenant.
Off-boarding is one action. When a teammate leaves, revoking their Google OAuth revokes GoogMeetSlack's access to their calendar. No shared secret to rotate, no orphaned events to reassign.

If you're evaluating a Slack meeting scheduler, ask the vendor whose calendar the event lands on. It sounds like a small architectural detail; it turns out to be most of the product.

See all writing →

What this costs

We think one 10-second setup step is a small price for meetings that behave like meetings you scheduled yourself. Because that's what they are.

What this enables

Real conflict detection. Google can now see your calendar when it schedules your meeting. So can everyone else's calendar when it decides whether to auto-decline.

Meeting cancellation from Slack cancels the calendar event. Because the bot has permission to edit your event, not a shared one.

Transcripts land in Slack, but they belong to your Workspace. If your compliance team runs a retention policy on Meet transcripts, our summaries respect it because we're reading through your tenant.

Off-boarding is one action. When a teammate leaves, revoking their Google OAuth revokes GoogMeetSlack's access to their calendar. No shared secret to rotate, no orphaned events to reassign.

If you're evaluating a Slack meeting scheduler, ask the vendor whose calendar the event lands on. It sounds like a small architectural detail; it turns out to be most of the product.