
Product
Introducing Tier 1 Reachability: Precision CVE Triage for Enterprise Teams
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
@zoom/rivet
Advanced tools
Zoom Rivet is a comprehensive toolkit built to help developers quickly integrate and manage server-side applications within the Zoom ecosystem. This tool currently supports Node.js, offering core functionalities like authentication, API wrappers, and even
Zoom Rivet is a comprehensive toolkit built to help developers quickly integrate and manage server-side applications within the Zoom ecosystem. This tool currently supports Node.js, offering core functionalities like authentication, API wrappers, and event subscriptions, enabling developers to focus on business logic instead of infrastructure.
In your Node.js application, install the Zoom Rivet package:
$ npm install @zoom/rivet
You can import and initialize the client from any supported module using the pattern for the Chatbot module in the code snippet below.
In a new entrypoint file called index.js
, add the following code, replacing CLIENT_ID
, CLIENT_SECRET
, and WEBHOOK_SECRET_TOKEN
with your Marketplace app credentials:
import { ChatbotClient } from "@zoom/rivet/chatbot";
(async () => {
const chatbotClient = new ChatbotClient({
clientId: "CLIENT_ID",
clientSecret: "CLIENT_SECRET",
webhooksSecretToken: "WEBHOOK_SECRET_TOKEN"
});
// Zoom Rivet code goes here!
const server = await chatbotClient.start();
console.log(`Zoom Rivet Events Server running on: ${JSON.stringify(server.address())}`);
})();
Save your index.js
file and run the following command to start your local development server:
$ node index.js
Now that your app runs on your local machine, let's use ngrok to allow Zoom to reach your server through webhook:
$ ngrok http 8080
To use Zoom Rivet effectively, you should understand three important concepts: authentication, listening to events, and using the Web API.
Zoom Rivet handles authentication for developers. All you have to do is provide your app's ClientId
and ClientSecret
. See the matrix in the table below to better how authentication works in each Rivet module:
Module | Auth Type |
---|---|
Chatbot | Client Credentials |
Video SDK | JWT |
Commerce | User OAuth |
Accounts, Marketplace, Meetings, Phone, Team Chat, Users | User OAuth, Server OAuth |
To listen to events sent to your app, you can use the event()
method in the webEventConsumer
property. This method can be used to listen to any supported Zoom webhook event, like a slash command shown below.
This method receives a required parameter of string
, which filters out webhook events that do not match.
chatbotClient.webEventConsumer.event("bot_notification", (response) => {
const payload = response.payload;
console.log(payload);
});
You can call any of the supported Zoom APIs using their respective methods in the endpoints
namespace of the module's client.
See the following example of the sendChatbotMessage()
API from the Chatbot module:
const reqBody = {
robot_jid: payload.robotJid,
account_id: payload.accountId,
to_jid: payload.toJid,
user_jid: payload.userJid,
content: {
head: {
text: "I am a header",
sub_head: {
text: "I am a sub header"
}
},
body: [
{
type: "message",
text: "I am a message with text"
}
]
}
};
chatbotClient.endpoints.messages.sendChatbotMessage({ body: reqBody }).then((response) => {
console.log("SENT MESSAGE", response.data);
});
Rivet provides built-in shortcuts that enable you to execute complex processes in just a few lines of code.
onSlashCommand()
Your app can use the onSlashCommand()
method to listen to incoming slash command requests.
Use the say()
method to respond to slash commands. It accepts a string or App Card JSON.
chatbotClient.webEventConsumer.onSlashCommand("SLASH_COMMAND", async ({ say, payload }) => {
console.log(payload);
await say("Hello World!");
});
onButtonClick()
Your app can listen to button clicks and respond using the onButtonClick()
method. This method takes in a string, which filters button action values.
You can respond with the say()
function, which accepts a string or App Card JSON.
chatbotClient.webEventConsumer.onButtonClick("BUTTON_VALUE", async ({ say, payload }) => {
console.log(payload);
await say("Hello World!");
});
onChannelMessagePosted()
You can use the onChannelMessagePosted()
method to listen to messages that your app can receive.
You can use the reply()
method to respond to slash commands. It accepts a string or App Card JSON.
teamchatClient.webEventConsumer.onChannelMessagePosted("KEYWORD", async ({ reply, payload }) => {
console.log(payload);
await reply("Hello World!");
});
For the full list of features and additional guides, see our Zoom Rivet docs.
If you're looking for help, try Developer Support or our Developer Forum. Priority support is also available with Premier Developer Support plans.
FAQs
Zoom Rivet is a comprehensive toolkit built to help developers quickly integrate and manage server-side applications within the Zoom ecosystem. This tool currently supports Node.js, offering core functionalities like authentication, API wrappers, and even
The npm package @zoom/rivet receives a total of 190 weekly downloads. As such, @zoom/rivet popularity was classified as not popular.
We found that @zoom/rivet demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.