User guide

Documentation

Connect your own account, publish a meeting in a team chat and receive the processed result in the same place.

Documentation version: 25 August 2026

1. Overview

Zoombot connects one application user to one individual meeting-provider identity. It can show meetings owned by that identity, create a new meeting, and publish a meeting card in a selected Bitrix24 or Telegram conversation.

When recording or transcript processing finishes, Zoombot updates the originating card or conversation with a report link. Connections and archives are isolated per user.

2. Connect your account

  1. Open Zoombot from your supported chat or personal management link.
  2. Select Connect account.
  3. Sign in to the meeting provider in the new browser tab.
  4. Review the requested permissions and select Allow.
  5. Return to the original chat and reopen Zoombot.
During a limited beta, an external provider account must be included in the approved tester audience before authorization will succeed.

3. Use Zoombot in Bitrix24

  1. Open any Bitrix24 chat where you want to share the meeting.
  2. Open the applications menu and select Zoom meeting.
  3. Search your existing meetings, select one, or choose Create meeting.
  4. Review the title and publish the card.
  5. Use the private host link shown only to you to start the meeting.

The host link is never posted into the shared chat. Other participants receive only the public join link and later the report link.

4. Use Zoombot in Telegram

Open the Zoombot personal chat to manage your connection and default meeting title. In a target conversation, invoke Zoombot inline, search or name a meeting, and send the selected card. Inline cards contain no management token or private host link.

5. Meeting processing and reports

Depending on available provider features, Zoombot may process recording files, audio, captions, transcripts and meeting summaries. A report can contain:

  • a concise meeting overview;
  • topics and discussion context;
  • decisions and explicitly assigned action items;
  • links to available meeting assets.

AI-generated content can be incomplete or incorrect. Review important decisions against the original meeting materials.

6. Disconnect and delete data

Disconnect from the Zoombot management page or remove the app from the meeting provider's marketplace. A valid deauthorization event removes the exact provider connection and its local provider data. For an access or deletion request, follow the privacy request instructions.

7. Why permissions are requested

Zoombot requests user-level permissions only, without administrator scopes:

  • read the authenticated user's identity;
  • list and read that user's meetings;
  • create, update or delete meetings at the user's request;
  • read recording metadata, files, transcripts and summaries used for reports;
  • delete cloud recording files only after the configured archival checks succeed.

See the full endpoint-purpose mapping on the Data Usage page.

8. Frequently asked questions

Can my colleague see my meetings?

No. A colleague connects their own account and sees only meetings returned for their own provider identity.

Does Zoombot store my provider password?

No. Authorization uses OAuth. Zoombot receives revocable tokens, which are encrypted at rest.

Who can open a report?

Anyone who possesses its unguessable report link. Share the link only in an appropriately restricted conversation.

Where can I get help?

Visit Support or email info@conmant.com.