Repository navigation
Add Zoom support for Vexa transcription bots - #224
Merged
Merged
Conversation
Vexa can now be dispatched to Zoom meetings from the Transcription menu. Backend - Add ZOOM to the Platform enum and an optional meeting_url field to DispatchBotRequest, threaded through the provider interface. - Vexa provider builds the Zoom join link via _zoom_join_url(): - a link that already has ?pwd= is forwarded untouched - a link without pwd plus a typed passcode gets ?pwd=<passcode> - a bare meeting ID becomes https://zoom.us/j/<id>[?pwd=<passcode>] Vexa Cloud rejects Zoom without a meeting_url (422), and its web bot ignores the separate passcode field, stalling in "joining" unless the passcode is in the link. Zoom accepts the plain or encoded passcode as pwd. - Include Vexa's response body when it rejects a dispatch, instead of httpx's bodyless error message. Frontend - Add 'zoom' to the Platform type. - Move meeting URL parsing into a per-platform registry (transcription/meetingPlatforms.ts), keyed by Platform so a missing platform fails to compile. - Parse Zoom /j/, /wc/join/ and /wc/<id>/join links on any zoom.us or zoomgov.com host, plus bare 9-11 digit IDs. Pull the passcode from ?pwd= and send the pasted link as meeting_url. - Reject personal (/my/), host start (/s/) and Zoom Events links with specific messages. - Show the passcode field for Teams, and for Zoom when the link has no pwd. - Show the error when a meeting URL is invalid (previously the dispatch failed silently). Docs - Regenerate the OpenAPI spec (backend and dna-docs copies). - Document Zoom in the transcription pipeline doc and the user guide. - Correct ADR-005: sg_platform is a text field, not a list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Cameron Target <camerontarget@gmail.com>
Closed
6 tasks
jspada200
reviewed
Oct 12, 2026
jspada200
requested changes
Oct 12, 2026
- Move Zoom join-link details from the Platform data-model docs into the _zoom_join_url docstring; keep a short note under Layer 4 - Import parseMeetingUrl from meetingPlatforms directly and drop the re-exports from useTranscription and the hooks barrel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Cameron Target <camerontarget@gmail.com>
Collaborator
Author
|
@jspada200 just wondering if this guy is good to go? |
jspada200
approved these changes
Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Vexa can now be dispatched to Zoom meetings from the DNA Transcription panel.
Backend
Frontend
Docs
Testing
How I Tested
Ran DNA and added vexa to a Zoom call.