Proposal: list zoom-chat-adapter as community adapter for Zoom Team Chat
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
This is a request to list an external community adapter, not a code change, so the first step is to find the repository's community adapter listing guidelines in its docs. Check whether the maintainers want a listing PR or a decision on inclusion first, since the issue asks for review before any PR. Done means either a maintainer decision on the proposal or a listing PR that follows the guidelines.
Written by the indexing model from the issue text.
Description
Proposal: Add zoom-chat-adapter to the Community Adapter Catalog
Hi maintainers!
I'd like to propose adding zoom-chat-adapter, an independently maintained adapter for Zoom Team Chat, to the Chat SDK community adapter catalog.
Package Details
- GitHub: https://github.com/aradhyacp/zoom-chat-adapter
- npm: https://www.npmjs.com/package/zoom-chat-adapter/v/1.0.1
- Package:
[email protected] - Factory:
createZoomAdapter()
Background
This adapter was inspired by PR #360 — kudos to the original contributor for exploring Zoom support.
Since Zoom support wasn't merged as an official adapter, I developed this as a standalone community package to bridge that gap and make Zoom Team Chat available to developers using Chat SDK.
Features and Implementation
The adapter currently supports:
- Webhook events:
endpoint.url_validation,bot_notification(including channel messages, DMs, and slash commands), andteam_chat.app_mention. - Webhook security: HMAC-SHA256 signature verification using
x-zm-signature, with a five-minute timestamp validation window. - Message operations: Send, edit, and delete messages, along with thread replies.
- Streaming: Buffered message streaming for incremental bot responses.
- Formatting: Markdown-to-Zoom and Zoom-to-Markdown conversion.
- Integration testing: End-to-end testing in a sample application using Chat SDK alongside
@chat-adapter/state-memory.
The goal is to provide a practical, maintainable integration that follows Chat SDK's adapter patterns while accommodating Zoom Team Chat's platform-specific behavior.
Testing and Verification
I've tested the adapter end-to-end in a sample application, including message handling and integration with the state-memory adapter.
I've also included screenshots demonstrating the integration in action:
- Bot interaction: A bot response in Zoom Team Chat.
- Webhook handling: Relevant webhook or terminal logs.
- Sample code: Sample application code showing how the adapter is initialized and used.
These examples should help reviewers verify the integration and understand how developers can use it.
Known Limitations and Maintenance
I'm an independent developer and am not affiliated with Zoom.
I intend to maintain the package, address issues, and track changes in Zoom's documentation and API behavior. I'm also documenting known platform limitations, including:
- Thread subscription flow limitations.
- DM thread-reply limitations.
- The Unicode-related HMAC verification issue tracked as
ZOOM-506645.
These are acknowledged compatibility considerations rather than claims of complete platform parity. I'll continue refining the implementation as the underlying behavior evolves.
Request for Inclusion
Could you take a look at the adapter and review it? I'd appreciate your feedback and would love to know if you'd be interested in including it in the Chat SDK community adapter catalog.
If so, I'm happy to open a PR following the repository's community adapter listing guidelines, including the relevant changes.
I'm happy to address review feedback, adjust the documentation or implementation to match the project's conventions, and make any necessary changes before the listing is merged.
Thanks for building and maintaining Chat SDK! I'd appreciate your feedback and the opportunity to contribute this integration to the community ecosystem.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 329
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 62
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/chat
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 45/100
vercel/chat#1058 · 1 reaction ·
Maintainers usually reply within 1 day
-
Slack adapter: dispatch `app_uninstalled` / `tokens_revoked` to `onUninstalled`Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
Similar issues
-
createAI: the ai peer range allows ai@6, which the provider cannot work withPossibly taken @akhil9tiet claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 83/100
cloudflare/agents#2690 · 3 comments ·
Maintainers usually reply within 1 day
-
[fullsend] E2E: theme — global-header ignores app.branding.fullLogo (RHDHBUGS-3670)Possibly taken @fullsend-ai-coder claimed this today. Opene2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 78/100
redhat-developer/rhdh-plugin-export-overlays#4503 · 1 comment ·
Maintainers usually reply within 1 day
-
needs triage 📥
Difficulty 1/5 Under an hour Newbie friendliness 86/100
ethereum/ethereum-org-website#19601 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cloudscape-design/components#5184 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agilepathway/label-checker#805 ·
Maintainers usually reply within 1 day