rivet-sdk
Reference skill for Zoom Rivet SDK. Use after routing to a Rivet-based server workflow when implementing auth handling, webhook consumers, API wrappers, multi-module composition, or Lambda receiver patterns.
Security Assessment
About rivet-sdk
This reference skill covers the Zoom Rivet SDK, a JavaScript/TypeScript server-side framework that bundles Zoom auth handling, webhook receivers, and typed REST API wrappers so developers can scaffold Zoom integrations with minimal glue code. It addresses the problem of assembling OAuth token handling, webhook signature verification, and API calls into one coherent Node.js server, and it helps decide when Rivet is worth adopting versus using direct OAuth plus REST.
The skill documents Rivet's lifecycle: choose modules and a per-module auth model (Client Credentials, User OAuth, Server-to-Server OAuth, Video SDK JWT), instantiate clients with credentials and a webhook secret, register event handlers, call APIs through `client.endpoints.*`, start receivers exposing webhook endpoints, persist tokens and enforce signature verification, and monitor per-module failures. It provides architecture and lifecycle notes, getting-started and multi-client patterns, a reference map, versioning/compatibility guidance, sample validation, and a detailed environment-variable reference covering client IDs/secrets, webhook secret tokens, S2S account IDs, redirect URIs, state-store secrets, and per-module ports. High-level scenarios include Team Chat bots, multi-module backends, Video SDK telemetry, ISV tenant-aware orchestration, and AWS Lambda webhook processing.
It targets backend developers building Zoom integrations who want faster server scaffolding, and its guidance is security-conscious — tokens are server-side, webhook signatures are verified, secrets are rotated. The content is documentation and pattern reference grounded in the official Rivet docs and Zoom sample repositories.
FAQ
What is Rivet SDK?
A Node.js (JavaScript/TypeScript) server framework that bundles Zoom auth handling, webhook receivers, and typed REST API wrappers to reduce glue code for Zoom integrations.
When should I use Rivet versus direct OAuth + REST?
Use Rivet when you want a Node.js server combining Zoom auth, webhooks, and API calls with minimal glue. If you only need direct API calls from an existing backend, the skill routes you to the rest-api skill instead. The skill recommends confirming this preference at planning start.
What environment variables are needed?
Core keys include a client ID and secret, a webhook secret token for receiver flows, an account ID for Server-to-Server OAuth, a redirect URI and state-store secret for User OAuth, plus optional per-module port keys.
What auth models does it support?
Client Credentials, User OAuth, Server-to-Server OAuth, and Video SDK JWT, chosen per module.
What are common deployment scenarios?
Team Chat slash-command bots, multi-module backends sharing one process, Video SDK telemetry backends, ISV orchestration with tenant-aware token storage, and AWS Lambda webhook processing via the Rivet AwsLambdaReceiver.
All Files
13 filesInstall rivet-sdk
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins