Connect Zoom

Connect your Zoom account inside qbash to use meeting details, participants, transcripts, saved chat, poll results, Q&A, and available AI Companion summaries in your tasks. The connector reads Zoom data; it does not create, change, or delete meetings.

After you connect Zoom, you can add its tools to a qbash MCP server for ChatGPT, Claude and other MCP clients, or call it from a Python task. The Zoom MCP server page lists what the connector can do.

Before you connect

You need a qbash account and a Zoom account. Your Zoom administrator may need to approve qbash before you can authorize it. This guide covers the User connection for the user-managed qbash app. It reads data available to the authorizing user, not every user's meetings across an account.

Availability depends on your Zoom plan, permissions, and meeting settings. A transcript requires a cloud recording with transcription enabled. Saved chat, polls, Q&A, and AI Companion summaries must exist for the meeting you select.

Add Zoom inside qbash

1. Sign in to qbash and select your organization.
2. Open Connectors, find Zoom, and select Connect (or Add another for an additional connection).
3. Give the connection a recognizable name. Under Connection Type, choose User - Access your own meetings.
4. Select Connect with Zoom. Sign in to the intended Zoom account, review the requested permissions, and authorize qbash.
5. Return to qbash. The saved connection is available for your tasks. If Zoom requires administrator approval, request it from your Zoom account administrator and then start the connection again.

Start this process inside qbash, rather than by opening a copied Zoom authorization URL. qbash creates a temporary authorization session to return the connection to the correct organization.

Use meeting data

In your task editor, open Resources → Integrations, add Zoom, and select the saved connection. See Connect resources for task setup.

Search meetings hosted by the connected Zoom user with a date range and, optionally, a topic keyword. Meetings you only attended do not appear in this search. Use a returned meeting ID or UUID with the meeting-detail, participant, transcript, chat, poll-result, Q&A, or AI-summary action. The SDK reference documents the available methods and parameters.

For example, create a task that searches last week's meetings, retrieves an available transcript, and produces a recap with decisions and follow-ups. Run it manually first, then add a schedule if you want recurring execution. When your task uses an AI model, the meeting content you pass to that model is shared with the selected provider.

Remove access

1. Sign in to the Zoom App Marketplace with the account that authorized qbash.
2. Open Manage → Added Apps, locate qbash, and choose Remove. Complete Zoom's removal confirmation. If your administrator controls removal, ask them to remove the app for you.
3. Disable or update any scheduled qbash tasks that use this connection. Zoom revokes the authorization. For connections saved with Zoom identity information, qbash processes the signed removal notification, clears matching access and refresh tokens, and marks the connection as requiring authorization again.
4. If you no longer need the saved connection, remove it from the Zoom connector's connection management controls in qbash.

Older saved connections created before Zoom identity tracking was introduced cannot be matched to removal notifications. Zoom still revokes their access, but qbash cannot automatically clear their stored tokens or mark them for reauthorization. Remove those saved connections in qbash, or reconnect them to record the identity needed for future removal handling.

Deleting a saved connection in qbash is not a substitute for revoking the app in Zoom. To reconnect, start Connect with Zoom inside qbash again and grant fresh authorization.

Zoom also documents adding and removing apps for personal use.

Retained content and privacy

Disconnecting Zoom stops future access through that authorization. It does not automatically delete previously saved conversations, task outputs, run logs, or copies sent to destinations you configured. qbash cannot reliably trace transformed content back to an individual Zoom API retrieval.

When Data Logging is enabled, run logs can retain full integration results, including transcripts, chat, polls, and participant data, even if the final output is only a summary. Settings → Details → Data logging controls retention of task run content. Turning it off prevents future task content logging; it does not erase existing records. Review Runs and logs and your organization’s retention settings. Model providers and configured destinations have their own retention policies.

Delete retained records using the relevant qbash controls, or ask your organization administrator for assistance with shared records. For privacy requests, contact legal@qbash.com. See the Privacy Policy for retention and deletion information, including account-deletion timing and backups.

Troubleshooting and support

• No meetings found: check the date range, topic filter, and which Zoom account you connected. User searches only return meetings hosted by the connected user, not meetings they merely attended.
• No transcript or other meeting content: confirm that Zoom has that data and that the connected user can access it. A meeting without a cloud transcript cannot return one.
• Authorization expired or removed: reconnect from qbash. Older connections may also need reconnection after a permission update.
• Authorization window does not return: allow the sign-in window, return to qbash, and start a fresh connection rather than reusing an old authorization link.
• Administrator approval required: ask your Zoom administrator to approve qbash.

For help, use qbash support or email alex@qbash.com. Include the action you tried, approximate time, and error message. Do not include passwords, access tokens, refresh tokens, or meeting content that is unnecessary for the support request.