Get Context

Documentation

Adding the App

Installing Get Context takes about a minute and a half.

1. Open the Zoom Marketplace and search for Get Context, or click the install link on the Marketplace listing.
2. Click Install. Zoom shows the OAuth consent screen with the scopes the app needs (see Permissions below).
3. Click Authorize. Zoom redirects you to https://get.context.select/ with a confirmation message.
4. That's it — you're installed. The app will now automatically capture any Zoom meeting you host over Zoom RTMS. There is nothing else to configure.

Prerequisites: a Zoom Pro account (or higher) and a GitHub repository where you would like your meeting notes to be committed.

Permissions requested

• user:read:user — to read your name and email so meetings you host are correctly attributed to your account.
• user:read:zak — to obtain a short-lived Zoom Access Key (ZAK) as a legacy fallback for the small number of meeting types not yet covered by RTMS. The ZAK is used immediately and not stored.
• meeting:read:meeting — to fetch meeting metadata when a meeting starts.
• meeting:read:meeting_audio — to receive the meeting's audio stream in real time over Zoom RTMS.
• rtms:read:rtms_started — to be notified by Zoom when an RTMS stream is available to consume.
• rtms:read:rtms_stopped — to be notified by Zoom when an RTMS stream ends.

Get Context subscribes to the following Zoom event notifications:

• meeting.rtms_started — primary trigger; the Service opens the RTMS audio stream.
• meeting.rtms_stopped — informational; the Service also detects stream end through the RTMS SDK callback.
• meeting.started / meeting.ended — legacy events, retained for the small number of meeting types not yet covered by RTMS.

Usage

Feature 1: Auto-capture via RTMS

Use case: you host a Zoom meeting and want a Markdown record of what was discussed without doing anything during the call.

Prerequisites: Get Context installed on your Zoom account; you are the host of the meeting.

1. Start any Zoom meeting (instant, scheduled, or from a calendar invite).
2. Zoom opens an RTMS stream to the Service automatically — no participant is added to the call.
3. Zoom displays its native Audio Assist Notification badge — "Brought by <your name>" — on your video tile so all participants can see the meeting is being captured by an app you authorized. This is by Zoom's design and cannot be disabled — Get Context never hides its presence.
4. Conduct your meeting normally. The Service only consumes audio over RTMS; it does not chat, mute participants, share screen, or take any in-meeting action.
5. End the meeting when you are done. The RTMS stream closes automatically and post-processing begins.

Feature 2: Transcript + AI summary in your GitHub repo

Use case: after the meeting, you want a searchable Markdown file with the full transcript, plus a TL;DR, action items, and decisions, in a private GitHub repository you control.

Prerequisites: Feature 1 above completed; a GitHub repository configured with Get Context (see Setup below).

1. Within ~2 minutes of the meeting ending, a new file appears at sources/YYYY-MM-DD-zoom-<meeting-uuid>.md in your repo, containing the speaker-aligned timestamped transcript.
2. ~1–3 minutes later, a follow-up commit appends a TL;DR, decisions, action items, and open questions section generated by Anthropic Claude.
3. The Markdown file is yours: it lives in your repository, is exportable, searchable in any tool (Obsidian, grep, GitHub search), and never locked into our service.

Feature 3: Telegram notification (optional)

Use case: you want a quick mobile notification with a link to the just-committed Markdown file.

Prerequisites: a Telegram bot configured for your account (contact hello@context.select for setup help).

When the AI summary commit lands, a Telegram message is sent to your configured chat with the meeting title, duration, and a direct link to the GitHub Markdown file.

Topic blocklist

You can configure topic substrings (for example "therapy", "personal") that, when present in a meeting's title, prevent the Service from opening the RTMS stream. This is useful for meetings you'd rather keep off the record. The blocklist is configured server-side at install time; a self-service UI is on the roadmap.

Removing the App

1. Open Zoom Marketplace → Installed Apps.
2. Find Get Context in the list and click Uninstall.
3. Confirm the uninstall in the dialog Zoom shows.

What happens to your data after de-authorization

When you uninstall the app, the following data implications apply:

• OAuth tokens (your refresh token and any cached access token) are deleted from our Cloudflare KV store within 24 hours of receiving Zoom's app_deauthorized event. After deletion, the Service can no longer make any Zoom API call attributed to your account.
• Webhook subscriptions are automatically removed by Zoom — we will stop receiving meeting.rtms_started, meeting.rtms_stopped, meeting.started, and meeting.ended events for your account.
• Meeting audio recorded during prior RTMS sessions exists only as an in-memory buffer on the sidecar during processing and is cleared immediately after transcription. No persistent audio storage is retained after a meeting ends.
• Transcripts and summaries already committed to your GitHub repository are not affected — they remain in your repo, which you own. If you wish to delete them, do so directly in GitHub (we have no further access).
• If you would like a written confirmation that data deletion has completed, write to privacy@context.select and we will provide one within 7 days.

Data flow

Zoom meeting.rtms_started webhook
  → Cloudflare Worker (HMAC verify, queue job)
  → Sidecar on Hetzner VPS (Germany) opens RTMS audio stream
  → Audio held in memory only — never written to disk longer than needed
  → meeting.rtms_stopped / SDK onLeave callback
  → Groq Whisper Large v3 → transcript with speaker-aligned timestamps
  → Anthropic Claude Haiku → summary, action items, decisions
  → Commit Markdown to your GitHub repo
  → All audio buffers cleared immediately after transcription
  → Telegram notification

Self-host

The full source code is open source and available on GitHub:

• meeting-bot — Cloudflare Worker (gateway and OAuth)
• meeting-bot-sidecar — Python processor (Hetzner)

If you'd rather run your own infrastructure rather than use the hosted Service, the repos contain Docker configurations and step-by-step deployment notes.