Get Context

Documentation

How it works

1. You install Get Context from Zoom Marketplace and authorize it via OAuth.
2. When a Zoom meeting you host or attend starts, the Service is notified by Zoom.
3. A bot named "Meeting Notes" joins the call as a participant.
4. Audio is recorded for the duration of the meeting.
5. After the meeting ends, the recording is transcribed by Groq Whisper.
6. Anthropic Claude generates a summary, action items, and key decisions.
7. The result is committed to your private GitHub repository as a Markdown file.
8. You receive a Telegram notification (if you opted in) with a link to the file.

What gets installed

Installing Get Context grants the following Zoom OAuth scopes:

• meeting:read:meeting — fetch join URL and password when a meeting starts.
• user:read:user — read your name and email so we can identify your account.
• user:read:zak — fetch a short-lived Zoom Access Key per meeting so the bot can join meetings you are invited to.

Get Context also subscribes to two Zoom webhook events:

• meeting.started — to know when to spawn the bot.
• meeting.ended — to know when to start processing.

What participants see

When the bot joins, all participants see:

• A new participant named "Meeting Notes" in the participant list.
• Zoom's standard recording indicator (red REC dot in the top bar).
• An audible Zoom announcement that the meeting is being recorded.

This is by Zoom's design and cannot be disabled. Get Context does not attempt to hide its presence.

Topic blocklist

You can configure topics that should never trigger the bot — useful for personal or therapy meetings. Currently this is configured server-side; a UI is on the roadmap.

Disconnecting

1. Open Zoom Marketplace → Installed Apps.
2. Click "Uninstall" next to Get Context.

Within 24 hours, all OAuth tokens and webhook payloads are deleted from our infrastructure. Notes already in your GitHub repo are not affected — they remain yours.

Data flow

Zoom meeting.started
  → Cloudflare Worker (HMAC verify, fetch meeting URL)
  → Spawn bot via Attendee SDK on Hetzner VPS (Germany)
  → Bot joins meeting, records audio to Cloudflare R2 (EU)
  → meeting.ended
  → Sidecar pulls recording, transcodes to opus
  → Groq Whisper Large v3 → transcript with timestamps
  → Anthropic Claude Haiku → summary, action items, decisions
  → Commit Markdown to your GitHub repo
  → Audio deleted within 24 hours
  → 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.