rivet-sdk

anthropics/knowledge-work-plugins

Reference skill for Zoom Rivet SDK—a Node.js server framework for Zoom auth, webhooks, and typed API wrappers.

What is rivet-sdk?

Rivet SDK is a JavaScript/TypeScript server framework that bundles OAuth token handling, webhook event consumption, and typed REST API endpoint wrappers for Zoom integrations. Use it when building a Node.js backend that combines Zoom authentication, webhook receivers, and API calls with minimal boilerplate.

OAuth and token handling (Client Credentials, User OAuth, S2S OAuth, Video SDK JWT)
Webhook event consumption and signature verification
Typed REST API endpoint wrappers for Zoom modules
Multi-module server composition (Users, Meetings, Team Chat, Phone, Video SDK)
Lambda receiver pattern support for serverless webhook processing

How to install rivet-sdk

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill rivet-sdk

Prerequisites

Node.js runtime
Zoom app credentials (Client ID, Client Secret)
Webhook secret from Zoom app configuration
Environment variables configured per module

Claude Code

Cursor

Windsurf

Cline

How to use rivet-sdk

1.Choose modules and auth model per module (Client Credentials, User OAuth, S2S OAuth, or Video SDK JWT)
2.Instantiate client(s) with credentials, webhook secret, and per-module port
3.Register event handlers using webEventConsumer.event(...) or module shortcuts
4.Implement API calls through client.endpoints.*
5.Start receiver(s) and expose webhook endpoint (/zoom/events) to Zoom
6.Persist tokens/state for OAuth workloads and enforce signature verification
7.Monitor module-specific failures and rotate secrets per changelog cadence

Use cases

Good for

Team Chat slash-command bot with data API enrichment
Multi-module backend combining Users, Meetings, Team Chat, and Phone in one process
Video SDK telemetry backend consuming event streams and API surfaces
ISV orchestration layer with tenant-aware token storage and per-module webhooks
AWS Lambda webhook processor using Rivet AwsLambdaReceiver

Who it's for

Backend engineers building Node.js Zoom integrations
ISV developers needing multi-tenant Zoom server scaffolding
Developers implementing Zoom webhooks and OAuth flows
Teams combining multiple Zoom modules in a single service

rivet-sdk FAQ

When should I use Rivet SDK vs. direct OAuth + REST?

Use Rivet when you want a Node.js server that combines Zoom auth, webhooks, and API calls with minimal glue code. If you only need direct API calls from an existing backend, use the REST API skill instead.

Can I use Rivet with multiple Zoom modules?

Yes. Rivet supports multi-module composition—you can combine Users, Meetings, Team Chat, Phone, and Video SDK modules in a single process, each with its own auth model and webhook port.

Does Rivet support serverless (Lambda)?

Yes. Rivet provides an AwsLambdaReceiver pattern for AWS Lambda webhook processing.

What auth models does Rivet support?

Rivet supports Client Credentials, User OAuth, S2S OAuth, and Video SDK JWT authentication models, selectable per module.

Where do I find environment variable configuration?

See references/environment-variables.md in the skill for standardized .env keys and where to obtain each value from your Zoom app.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.

name: rivet-sdk description: "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." user-invocable: false triggers:

"rivet"
"zoom rivet"
"@zoom/rivet"
"rivet javascript"
"rivet sdk"
"rivet webhook"
"rivet oauth"
"rivet lambda"
"rivet team chat"
"rivet chatbot"

Zoom Rivet SDK

Background reference for Zoom Rivet as a JavaScript and TypeScript server framework for Zoom integrations.

Implementation guidance for Zoom Rivet (JavaScript/TypeScript) as a server-side framework for:

OAuth and token handling
Webhook event consumption
Typed REST API endpoint wrappers
Multi-module server composition

Official docs:

Reference samples:

Routing Guardrail

Rivet SDK is a Node.js framework that bundles Zoom auth handling, webhook receivers, and typed API wrappers.
Rivet is recommended for faster server-side scaffolding, but it is not mandatory.
At planning start, confirm preference:
Do you want Rivet SDK, or direct OAuth + REST without Rivet?
Use Rivet when the user wants a Node.js server that combines Zoom auth + webhooks + API calls with minimal glue code.
If the user only needs direct API calls from an existing backend, chain with ../rest-api/SKILL.md.
If the user is focused on Zoom Team Chat app cards/commands behavior, chain with ../team-chat/SKILL.md.
If the user needs SDK embed (Meeting SDK/Video SDK client runtime), route to ../meeting-sdk/SKILL.md or ../video-sdk/SKILL.md.

Quick Links

Start here:

Common Lifecycle Pattern

Choose modules and auth model per module (Client Credentials, User OAuth, S2S OAuth, Video SDK JWT).
Instantiate client(s) with credentials, webhook secret, and per-module port.
Register event handlers (webEventConsumer.event(...) or shortcuts).
Implement API calls through client.endpoints.*.
Start receiver(s) and expose webhook endpoint(s) (/zoom/events) to Zoom.
Persist tokens/state for OAuth workloads and enforce signature verification.
Monitor module-specific failures and rotate secrets/version with changelog cadence.

High-Level Scenarios

Team Chat slash-command bot + Team Chat data API enrichment.
Multi-module backend (Users + Meetings + Team Chat + Phone) sharing one process.
Video SDK telemetry backend using videosdk module event stream + API surfaces.
ISV orchestration layer with tenant-aware token storage and per-module webhooks.
AWS Lambda webhook processor with Rivet AwsLambdaReceiver.

See scenarios/high-level-scenarios.md for details.