Skip to content

Create a service integration

This guide helps you to create a service integration such as twitch-chat or discord

Find a JavaScript library

Go to and look whether there's already a package that wraps around the API of your service. If there's no such package, you need to create one yourself. This is not described here. You may read the “Contributing packages to the registry” from the npm Docs.

Create the service files

To create the service you can either use a premade Python 3 script in .scripts/, or create the files manually.

What this script does:

  • It creates all required files for a new nodecg-io service
  • It copies version and dependency information (e.g., for typescript) from noodecg-io-template

It'll also create a sample and the files for the docs Requirements:

  • python3 in your $PATH (see install page)
  • executed from root of nodecg-io repo

The script waits for your input for each of those fields:

$ python3 .scripts/
Service name: <name here>
Short description: <description here>
Author name: <author here>
Author url: <url here>
Sample name: <name here>


Now the script will rebuild your environment.

Create the files manually


From here you will have to replace:

  • YourServiceName to your service's name in PascalCase.
  • yourServiceName to your service's name in carmelCase.
  • your-service-name to your service's name with only lowercase and hyphens (-) for example: ws-server.

Now you need to create a package. You should call it nodecg-io-your-service-name.

First create a directory with that name in /services/ and put file called package.json into it.

Put the following into it:

    "name": "nodecg-io-<your-service-name>",
    "version": "0.2.0",
    "description": "<Short description what is possible with your service.>",
    "homepage": "<your-service-name>",
    "author": {
        "name": "<Your name>",
        "url": "<Your github profile url>"
    "repository": {
        "type": "git",
        "url": "",
        "directory": "services/nodecg-io-<your-service-name>"
    "files": ["**/*.js", "**/*", "**/*.d.ts", "*.json"],
    "main": "extension",
    "scripts": {},
    "keywords": ["nodecg-io", "nodecg-bundle"],
    "nodecg": {
        "compatibleRange": "^1.1.1",
        "bundleDependencies": {
            "nodecg-io-core": "^0.2.0"
    "license": "MIT",
    "devDependencies": {
        "@types/node": "^15.0.2",
        "nodecg-types": "^1.8.2",
        "typescript": "^4.2.4"
    "dependencies": {
        "nodecg-io-core": "^0.2.0",
        "<the package you found in step 1>": "<the packages version you want to use>"

Next you need to put a file called tsconfig.json next to your package.json. The tsconfig.json should look like this:

    "extends": "../../tsconfig.common.json",
    "references": [
            "path": "../../nodecg-io-core"

Now run npm install in the repository root.

Create a configuration schema

Next create a file called your-service-name-schame.json. This is a JSON schema file that indicates how the configuration for your service should be structured. If you need help here take a look at this online resource and the schema-files of the other service implementations.

Create the service

Create a file called index.ts in a folder called extension inside your service's directory. You can then paste the following code and fill in your code instead of the comments.

// TODO: Rename all occurrences of "YourServiceName" in PascalCase
// TODO: Rename all occurrences of "yourServiceName" in carmelCase
// TODO: Rename all occurrences of "your-service-name" with only lowercase and hyphens ( - )

import { NodeCG } from "nodecg-types/types/server";
import { Result, emptySuccess, success, ServiceBundle } from "nodecg-io-core";
// TODO: Replace the "fake" service class with that found on npm etc.
import { ServiceClass } from "./";

interface YourServiceNameServiceConfig {
    // TODO Fill in the values from your json schema here. The json
    // schema will load into an instance of this.

// ServiceClient ensures that you will provide a `getNativeClient` function that should give
// access to the underlying client from the library that you are using.
// TODO: if you want to provide simplifications for the service then make this
// type-alias a separate class in a separate file and directly implement those simplifications
// there.
// TODO: Replace the `ServiceClass` with the class of the package from step 1
export type YourServiceNameServiceClient = ServiceClient<ServiceClass>;

module.exports = (nodecg: NodeCG) => {
    new YourServiceNameService(

class YourServiceNameService extends ServiceBundle<
> {
    async validateConfig(
        config: YourServiceNameServiceConfig
    ): Promise<Result<void>> {
        // TODO You can validate your config here. If this gets called, the schema is correct.
        // You should for example check whether oauth keys are valid and servers are online here
        // If everything is good return 'emptySuccess()'
        // If an error occurs return 'error(<The error message>)'

    async createClient(
        config: YourServiceNameServiceConfig
    ): Promise<Result<YourServiceNameServiceClient>> {
        // TODO Here you should return a <Your service name>ServiceClient that is exposed to bundles.
        // Or create a instance of your class if you have any simplifications and return that.
        // If everything is good return 'success(client)'
        // If an error occurs return 'error(<The error message>)'

    stopClient(client: YourServiceNameServiceClient): void {
        // Here you should make sure you disconnect everything here (if possible).


Now run npm run build in the repository root, start NodeCG and test your service out.

Next steps

You could create a sample bundle for your brand-new service.

If you don't do so, make sure you add a placeholder file called <the services name>.md in docs/samples in your fork of the documentation.

The file should look like this:

<!-- Marker for that there's no sample bundle. Remove this if you created one -->

## Using the <the services name> sample bundle

No sample bundle for service `<the services name>`.
[You can help us and create one!](


Do not remove the marker in the first line until there is a sample bundle, and it is documented there. Don't forget to add this file to mkdocs.yml.