node package manager


hermione the npm operations chat bot


Hermione the npm operations Slack chat battlestation is fully operational and is capable of demonstrating its power on a target, a military target. Name the system!

You'll want to create your own little node package for your installation. This package needs a package.json, a configuration file, and a shell script to run the bot.

Here's a nice minimal package.json, requiring opsbot & a third-party plugin:

  "name": "deathstar",
  "version": "0.0.0",
  "description": "a bot of destruction",
  "scripts": {
    "start": "bash",
    "dev": "NODE_ENV=dev bash"
  "dependencies": {
    "opsbot": "~1.0.0",
    "orlyowl": "^0.0.1"


opsbot --config ./configuration.js

To create your configuration file, start by copying config.example.js. Edit to your taste. You can have it log to console and/or log to a file depending on how you want to keep its logs. npm start runs the bot in prod mode. npm run dev will run it with pretty-printed console output.

Set up an outgoing webhook in Slack that points to /messages on your deployment URI. Set up a trigger word for the integration that is the botname you've configured. You can alternatively have the bot sent all traffic from a single channel.

Set up an incoming webhook in Slack. Add its full URI (with token) to the 'hook' field in your config.

List the plugins you want to load as fields in the plugins hash. The value should be an object with any required configuration for the plugin. Note that opsbot can load both built-in plugins and plugins installed via npm.

Example configuration:

module.exports =
    botname: 'hermione',
    token: 'slack-integration-token-here',
    hook: 'your-slack-incoming-webhook-uri-here',
    brain: { dbpath: '/path/to/leveldb' },
        console: false,
        path: '/var/log'
        pagerduty: { apikey: 'your-key-here', urlprefix: 'your-prefix' },
        npm: {},
        statuscats: {},

botname: help: return a help message

botname: status: gives bot uptime, loaded plugins, and location of the bot's brain.

Plugins must be objects with three required functions and a name field.

The constructor takes an options object. The required content of the options is up to the plugin itself. The options object will always be present and will always have a bole logger object in the log field. It will also have a leveldb instance in the brain field; see below.

A synchronous function that takes a string. Returns true if this plugin wants to handle the message, false otherwise. By convention and in order to be kind to fellow plugin authors, make this match on the prefix of incoming message. For instance npm koa might return information about the koa package on npm.

A function that takes a Message object. This function is expected to call message.send() with a string or with a fully-structured message with attachments as documented in the Slack API. The response handler will decorate the response with any missing required fields.

When you are finished sending replies to the incoming message, call message.done(). As a convenience, if the message requires only a single reply, you can call message.done(reply) to send & clean up.

Synchronously return a string with usage information.

Here's a simple plugin.

module.exports = function OwlPlugin() { }; = 'ORLYOWL';
OwlPlugin.prototype.matches = function matches(msg)
    return msg.match(/ORLY\?/);
OwlPlugin.prototype.respond = function respond(msg)
    msg.done('YA RLY');
}; = function help()
    return 'If you say ORLY?, you get the obvious response.';

bartly: Real-time BART departure information by station.
deployer: Invoke an ansible deployment playbook; requires customization for your environment. fastly: Fetches some current stats from the named Fastly service.
flipit: Table flip!
karma: Give points and take them away.
npm: Fetches package information from npm.
pagerduty: Show who's on call now & who's up in the next few days; list open incidents; ack & resolve incidents.
statuscats: Show an http status cat.
levenmorph: Morph one word into another using a nice short path.

Each plugin has more documentation at the top of its source file.

Opsbot uses levelup to provide a persistent key/value brain to plugins. Each plugin is, on construction, given an options object with a sublevel-namespaced db object in the brain field. This object might not be available if the opsbot configuration hasn't given it a path to store the db in, so your plugin should assert if it requires the brain but is not given one. See an example in the built-in karma plugin.

Write more plugins, add features to the existing plugins, it's all good.

Please follow the code style in existing files (4 spaces to indent, Allman bracing). If you write your own plugins, I don't much care what you do. Please try to be at least as responsible as I have been about writing tests.

If you want to use promises, go ahead! bluebird is already in the package deps.

If you write a plugin for opsbot & publish it on npm, please let me know so I can link it here! It might also help to give it the keyword opsbot so other people can find it when they search.

I'm running this against our Slack chat already. The existing plugins work perfectly well. I'm not calling it 1.0 yet because there is a small chance I might have to change the plugin API if I discover it isn't sufficient. The core features are in place, however.

Hermione the Opsbot is built on node-restify.

My colleagues bcoe and othiym23 have been invaluable.