
Security News
The Next Open Source Security Race: Triage at Machine Speed
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.
@voiceflow/runtime-client-js
Advanced tools
The Voiceflow Runtime Client is an SDK for running Voiceflow apps in JavaScript.
First, you build a fully-functioning conversational app on Voiceflow. Then, you integrate that app into a JavaScript project using the SDK. This allows you to quickly add any kind of voice interface, such as a chatbot, to your project, without the hassle of implementing the conversational flow using code.
The Runtime Client can be used with jQuery, React, and any other JavaScript library or framework.
See the parent rcjs-examples repo for instructions on how to setup each Sample.
# with NPM
npm install --save @voiceflow/runtime-client-js
# with yarn
yarn add @voiceflow/runtime-client-js
The minimum code to start using the SDK is shown below:
const { RuntimeClientFactory } = require('@voiceflow/runtime-client-js');
// alternatively for ESM/ES6
// import RuntimeClientFactory from '@voiceflow/runtime-client-js'
// Construct an object
const factory = new RuntimeClientFactory({
versionID: 'your-version-id-here', // ADD YOUR VERSION ID HERE
endpoint: 'https://general-runtime.voiceflow.com',
});
const client = factory.createClient();
client.onSpeak((trace) => {
// whenever we come across a speak block, just say the message
console.log(trace);
});
// (optional) explicitly begin a conversation session
client.start();
// call this function from any input source
const interact = (input) => client.sendText(input);
// e.g. interact('can I have fries with that');
pass in user input with the client.sendText(input) function, and any of your client.on... functions will trigger during the response.
See here for instructions on how to quickly setup a Voiceflow app to try out your project.
See here for a step-by-step breakdown of the Minimal Working Integration. Make sure to read "Setting up a Voiceflow App" first.
See the documentation here for the available advanced features of the SDK.
yarn installRun yarn install to install any necessary dependencies to get started with working on the SDK.
yarn buildUse this to build the runtime-client-js locally. The build will be stored in the /build folder
yarn lintUse this command to find any issues that fails our linter. It is important to have proper linting, otherwise your PR will not pass our automation.
Use yarn lint:fix to check and automatically fix linting issues where possible.
yarn testUse this command to run all of the integration and unit tests. Make sure that your PR achieves 100% coverage and tests for potential edge-cases.
Use yarn test:single to execute a single unit or integration test.
Use yarn test:unit to run all of the unit tests
Use yarn test:integration to run all of the integration tests.
We're always open to improving our Runtime Client SDK. Consider opening a PR if there is some improvement that you think should be added. Make sure to achieve 100% coverage for unit tests and provide documentation if applicable.
FAQs
JavaScript runtime SDK for executing Voiceflow projects
The npm package @voiceflow/runtime-client-js receives a total of 49 weekly downloads. As such, @voiceflow/runtime-client-js popularity was classified as not popular.
We found that @voiceflow/runtime-client-js demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 27 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.

Security News
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.

Research
/Security News
Malicious dYdX client packages were published to npm and PyPI after a maintainer compromise, enabling wallet credential theft and remote code execution.

Security News
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.