Bob with Zoom: make the meeting part of a finished workflow

Matthew, founder of Bob · Published July 30, 2026

Short answer

Bob connects to Zoom through the catalog and can use the authenticated meeting actions exposed by the live connection. Zoom documents REST APIs for meeting resources, users, recordings, and related account data. The exact subset Bob can invoke depends on the connection's available actions, the connected Zoom identity, OAuth scopes, account settings, and plan.

This page deliberately does not promise that Bob can fetch every transcript or control a live meeting. Ask Bob for the job; he can discover what the connected action set supports and report a missing action instead of pretending it succeeded.

Five useful Bob and Zoom workflows

1. Check the upcoming meeting setup

"Check tomorrow's customer Zoom meeting and tell me whether the host, time, and invite details match Google Calendar."

This is a useful read-oriented first test when the live connection exposes the required meeting lookup.

2. Create a meeting from an approved plan

"Prepare a Zoom meeting for the approved Thursday customer review. Show me the settings before creating it."

Bob checks the available actions and asks before the meeting is created.

3. Build a pre-meeting account brief

"Before each priority customer Zoom, brief me with the HubSpot deal, recent Gmail thread, and open Jira issues."

Zoom identifies the meeting while the other connections supply the substance.

4. Turn available meeting artifacts into work

"If the Zoom connection exposes the recording or transcript for yesterday's review, extract decisions and draft the Linear issues."

Recording and transcript availability varies by plan, retention, settings, permissions, and connection action set. Bob should say when the artifact is unavailable.

5. Audit recurring meeting hygiene

"List recurring Zoom meetings owned by the connected account that have no recent activity or clear owner. Do not delete anything."

A read-only inventory is safer than automatically cleaning up shared meetings.

Connection scope and setup

1. Ask Bob in Slack to connect Zoom.
2. Open the hosted OAuth flow and authenticate with the intended Zoom account.
3. Review the requested scopes and account permissions.
4. Return to Slack and retry the meeting request.

Zoom is a workspace-scoped catalog connection in Bob today. Use the least-privileged account appropriate for the team's workflows and make the acting identity clear.

Limits worth knowing

• Available actions vary. Bob discovers the Zoom catalog action set at run time.
• Recordings are conditional. Licensing, retention, consent, scopes, and account settings all affect access.
• No live-meeting control claim. A meeting API connection is not the same as joining or steering a live call.
• Writes ask by default. Creating, updating, or deleting a meeting remains reviewable.

FAQ

How does Bob connect to Zoom?

Through a hosted OAuth catalog connection that is workspace-scoped today.

What can Bob do with Zoom?

Bob uses the authenticated actions exposed by the live connection and allowed by the connected Zoom account.

Does Bob ask before creating or changing a meeting?

Yes. External meeting writes ask by default.

Can Bob access every Zoom recording or transcript?

No. Identity, scopes, licensing, settings, retention, and available actions all affect access.

Start with one meeting lookup

Ask Bob to find a known meeting and verify the details. Then connect Google Calendar, HubSpot, or Notion when the meeting needs preparation or follow-through.