Google Suite Bridge

Calendar, Drive and Meet — surfaced in the channels that need them. No more tab-switching to figure out who has access to what.

google-slack-integrations · primary screen

Overview

Features

Pricing

Permissions

Changelog

What's in the box

Four bridges between Google Workspace and the channel you're already in.

— 01

Subscribe channels to calendars

Point a channel at any shared Google Calendar. Events post in-line, RSVP from the message, link straight to the Meet.

— 02

/meet from any thread

Typing /meet inside a thread spins up a Meet, pins the link, and notifies threadwatchers. Two seconds, zero context loss.

— 03

Drive permission requests as approvals

When a teammate hits a "Request access" wall, you get a single DM with Approve / Deny buttons. No more email purgatory.

— 04

Per-user scopes, per-workspace OAuth

Admins install once. Teammates grant only the scopes they need. Revoke any of it without breaking the others.

How it runs in your workspace

Install and approve at the workspace level

A Slack admin and a Google admin both click yes once. We never store passwords or full-drive scopes.

Point a channel at a calendar

/google connect #design-team google-design-cal. That's the whole setup for most teams.

Layer per-user scopes when you need them

Anyone can opt in to /meet, Drive approvals, or both. They control their own permissions from a slash command.

"We deleted three separate 'calendar-bot' integrations the week we installed this. One bridge, predictable behaviour."

Devon T. · Engineering Manager · 140-person scaleup