Zoom Rivet SDK in Codex for a Test Integration
Design a minimal server-side Zoom integration with Rivet and isolate webhook handling from application logic.
中文Setup for Codex (Zoom plugin)
Use the complete Zoom plugin and the pinned Rivet getting-started reference. The dry run uses a local handler and an in-memory mock client. Live verification needs a Zoom developer app.
- In Codex, open /plugins and install Zoom. Use the full plugin package so its sibling skills and references are available.
- Invoke the bundled skill as $rivet-sdk in a scratch workspace. Keep the example on the local or demo inputs described below.
Example task
Use $rivet-sdk to design a route that sends a normalized meeting-ended event with meetingId='demo-44' to a fake summary queue. Pass the same event twice and test the business handler separately from the transport layer.Expected result
The handler enqueues one item for demo-44 and identifies the duplicate. The implementation plan separately tests the API client and webhook adapter using the documented Rivet interfaces.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Why keep the business handler separate from the webhook adapter?
The handler can be tested with local fixtures, while the adapter keeps HTTP parsing and the Zoom-specific validation in one place.