Bob with Google Calendar: schedule the work without the tab shuffle

Matthew, founder of Bob · Published July 30, 2026

Short answer

Connect Google Calendar and Bob can list events, find free slots, create an event, and respond to an invitation from Slack. Bob uses your own connected calendar and your Google permissions. He does not become a domain-wide scheduling administrator.

Google's Calendar API treats meetings as event resources and supports adding attendees when an event is created. Bob turns those primitives into a Slack conversation with a clear approval point before the calendar changes.

What Bob can actually do

Bob's purpose-built connection supports event listing, free-time search, event creation, and invitation responses. Google's event creation guide documents the underlying calendar model, including attendees and conference data.

Checking a calendar is a read. Creating a meeting, inviting someone, or accepting an invitation changes an external system. Those writes ask by default, and Bob's receipt records the action after it happens.

Five useful Bob and Google Calendar workflows

1. Find a time while the team is talking

"Find three 30-minute slots when I am free Thursday or Friday afternoon. Keep Friday after 3 open."

Bob returns workable options in the thread. No screenshot, copied calendar, or separate scheduling tab is required.

2. Turn an agreed time into the event

"Create the Friday 1:30 review with Priya and Owen. Use the launch brief from Drive in the description."

Bob can gather the document, prepare the event, and ask before sending invitations.

3. Prepare for the day

"Every weekday at 7:30, brief me on today's meetings. For external calls, add the latest Gmail thread and HubSpot deal stage."

Calendar supplies the schedule; other connections supply the context. Bob's own scheduler delivers the brief in Slack.

4. Find the commitments hidden in meetings

"Review my project meetings from last week and compare them with open Linear work. Tell me which promised follow-ups have no issue."

The calendar is not proof that work happened, but it is useful context for finding gaps.

5. Respond to an invitation

"Accept the customer review next Tuesday and tell the channel when it is done."

Because the response updates an external calendar, Bob asks first unless you have granted a matching policy.

How the connection works

1. Ask Bob in Slack to connect Google Calendar.
2. Open the secure connection button and sign in with Google.
3. Review the OAuth access and select the right account.
4. Return to Slack and ask Bob to finish the scheduling request.

The connection is per user. Availability only reflects calendars the connected user can access, and event changes happen as that user.

Limits worth knowing

• Availability is permission-bound. Bob cannot inspect a coworker's private calendar unless the connected account can.
• Time zones need clarity. Include the zone when attendees or travel cross regions.
• An event is an external commitment. Review guests, time, and description before approval.
• Recurring Bob work is separate. A daily brief can run on Bob's schedule even when it does not create a Google Calendar event.

FAQ

What can Bob do with Google Calendar?

Bob can list events, find free time, create events, and respond to invitations through the connected account.

Whose calendar does Bob use?

Google Calendar is personal in Bob. He acts with the calendar and permissions of the person who connected it.

Does Bob ask before creating a meeting?

Yes. Calendar changes ask by default unless the user deliberately granted that exact kind of work.

Can Bob schedule recurring work as well as meetings?

Yes. Bob has Slack-native schedules for recurring jobs and can use Google Calendar when the job needs an event or availability.

Start with the next meeting you need to arrange

Ask Bob to find the slots first. Once the times look right, let him prepare the event and review it before it lands. Add Gmail, Google Drive, or HubSpot when the meeting also needs context.