Extensible matrix bot written in Go
Go Shell
Latest commit d6d19a8 Jan 20, 2017 @Kegsay Kegsay Add GH Webhook test
Failed to load latest commit information.
hooks Move test util functions to dedicated file to clean up test files Oct 26, 2016
src/github.com/matrix-org/go-neb Add GH Webhook test Jan 20, 2017
vendor Implement slackapi Service (#116) Jan 13, 2017
.travis.yml Only emit travis results on success change Nov 18, 2016
LICENSE Create LICENSE Sep 30, 2016
README.md Update README.md Nov 18, 2016
config.sample.yaml Implement slackapi Service (#116) Jan 13, 2017



Build Status

Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python.

Table of Contents

Quick Start

Clone and run (Requires Go 1.5+ and GB):

gb build github.com/matrix-org/go-neb
BIND_ADDRESS=:4050 DATABASE_TYPE=sqlite3 DATABASE_URL=go-neb.db?_busy_timeout=5000 BASE_URL=http://localhost:4050 bin/go-neb

Get a Matrix user ID and access token and give it to Go-NEB:

curl -X POST localhost:4050/admin/configureClient --data-binary '{
    "UserID": "@goneb:localhost",
    "HomeserverURL": "http://localhost:8008",
    "AccessToken": "<access_token>",
    "Sync": true,
    "AutoJoinRooms": true,
    "DisplayName": "My Bot"

Tell it what service to run:

curl -X POST localhost:4050/admin/configureService --data-binary '{
    "Type": "echo",
    "Id": "myserviceid",
    "UserID": "@goneb:localhost",
    "Config": {}

Invite the bot user into a Matrix room and type !echo hello world. It will reply with hello world.



  • Login with OAuth2.
  • Ability to create Github issues on any project.
  • Ability to track updates (add webhooks) to projects. This includes new issues, pull requests as well as commits.
  • Ability to expand issues when mentioned as foo/bar#1234.
  • Ability to assign a "default repository" for a Matrix room to allow #1234 to automatically expand, as well as shorter issue creation command syntax.


  • Login with OAuth1.
  • Ability to create JIRA issues on a project.
  • Ability to expand JIRA issues when mentioned as FOO-1234.


  • Ability to query Giphy's "text-to-gif" engine.


  • Ability to query Guggy's gif engine.


  • Ability to read Atom/RSS feeds.

Travis CI

  • Ability to receive incoming build notifications.
  • Ability to adjust the message which is sent into the room.


Go-NEB is built using Go 1.5+ and GB. Once you have installed Go, run the following commands:

# Install gb
go get github.com/constabulary/gb/...

# Clone the go-neb repository
git clone https://github.com/matrix-org/go-neb
cd go-neb

# Build go-neb
gb build github.com/matrix-org/go-neb


Go-NEB uses environment variables to configure its SQLite database and bind address. To run Go-NEB, run the following command:

BIND_ADDRESS=:4050 DATABASE_TYPE=sqlite3 DATABASE_URL=go-neb.db?_busy_timeout=5000 BASE_URL=https://public.facing.endpoint bin/go-neb
  • BIND_ADDRESS is the port to listen on.
  • DATABASE_TYPE MUST be "sqlite3". No other type is supported.
  • DATABASE_URL is where to find the database file. One will be created if it does not exist. It is a URL so parameters can be passed to it. We recommend setting _busy_timeout=5000 to prevent sqlite3 "database is locked" errors.
  • BASE_URL should be the public-facing endpoint that sites like Github can send webhooks to.
  • CONFIG_FILE is the path to the configuration file to read from. This isn't included in the example above, so Go-NEB will operate in HTTP mode.

Go-NEB needs to be "configured" with clients and services before it will do anything useful. It can be configured via a configuration file OR by an HTTP API.

Configuration file

If you run Go-NEB with a CONFIG_FILE environment variable, it will load that file and use it for services, clients, etc. There is a sample configuration file which explains all the options. In most cases, these are direct mappings to the corresponding HTTP API.


The API is documented in sections using godoc. The sections consists of:

  • An HTTP API (the path and method to use)
  • A "JSON request body" (the JSON that is inside the HTTP request body)
  • "Configuration" information (any additional information that is specific to what you're creating)

To form the complete API, you need to combine the HTTP API with the JSON request body, and the "Configuration" information (which is always under a JSON key called Config). In addition, most APIs have a Type which determines which piece of code to load. To find out what the right type is for the thing you're creating, check the constants defined in godoc.

Configuring Clients

Go-NEB needs to connect as a matrix user to receive messages. Go-NEB can listen for messages as multiple matrix users. The users are configured using an HTTP API and the config is stored in the database.

Configuring Services

Services contain all the useful functionality in Go-NEB. They require a client to operate. Services are configured using an HTTP API and the config is stored in the database. Services use one of the matrix users configured on Go-NEB to send/receive matrix messages.

Every service has an "ID", "type" and "user ID". Services may specify additional "config" keys: see the specific service you're interested in for the additional keys, if any.

List of Services:

Configuring Realms

Realms are how Go-NEB authenticates users on third-party websites.

List of Realms:

Authentication via HTTP:

Authentication via the config file:


There's a bunch more tools this project uses when developing in order to do things like linting. Some of them are bundled with go (fmt and vet) but some are not. You should install the ones which are not:

go get github.com/golang/lint/golint
go get github.com/fzipp/gocyclo

You can then install the pre-commit hook:



|      |                 Go-NEB                               |
| +---------+                                                 |
| | Clients |                                                 |
| +---------+                                                 |
|      |                                                      |
| +---------+       +------------+      +--------------+      |
| | Service |-------| Auth Realm |------| Auth Session |-+    |
| +---------+       +------------+      +--------------+ |    |
|     ^                   ^              +---------------+    |
|     |                   |                                   |
      |                   |                   
    WEBHOOK            REDIRECT
    REQUEST            REQUEST

Clients      = A thing which can talk to homeservers and listen for events. /configureClient makes these.
Service      = An individual bot, configured by a user. /configureService makes these.
Auth Realm   = A place where a user can authenticate with. /configureAuthRealm makes these.
Auth Session = An individual authentication session /requestAuthSession makes these.

Viewing the API docs

The full docs can be found on Github Pages. Alternatively, you can locally host the API docs:

# Start a documentation server listening on :6060
GOPATH=$GOPATH:$(pwd) godoc -v -http=localhost:6060 &

# Open up the documentation for go-neb in a browser.
sensible-browser http://localhost:6060/pkg/github.com/matrix-org/go-neb