n-trello-slack

Based heavily off of node-trello-slack, with 3 extra features added including:

• tracking member adding to cards
• tracking cards created by email
• board ids, channel names, trello key+token and slack webhook in environment variables*

*when using n-trello-slack in conjunction with my fork of node-trello-slack on GitHub

The built-in integration for Trello provided by Slack/SlackHQ isn't enough. It's limited to one board!

This tool will check the Trello api once a minute for updates and push them into your desired channels. You can configure any number of boards.

Install (if using Method 1)

npm install --save n-trello-slack

Usage

Method 1 (based on node-trello-slack)

Create an executable script with the following code:

#!/usr/bin/env node
 
var Bot = require('n-trello-slack')
    ,bot = new Bot({
        pollFrequency: 1000*60 //every 1 minute
        ,start: true
        ,trello: {
            boards: ['Nz5nyqZg','...']
            ,key: 'trello-key-here'
            ,token: 'trello-token-here'
            ,events: ['createCard','commentCard','emailCard','addMemberToCard','addAttachmentToCard','updateCard','updateCheckItemStateOnCard']
        }
        ,slack: {
            webhook: 'slack-webhook-url'
        }
    });

You may completely omit trello.events, which indicates that you want all (recognized) events announced. All recognized events are listed in the example above. Alternately, include some subset of the list shown above. (Case sensitive)

Trello-board-specific channels

If you want to send alerts from each board to a different Slack channel, pass object hashes instead of string board id's in the trello.boards array, as you see here:

,trello: {
    boards: [
        {
            id: 'Nz5nyqZg'
            ,channel: '#general'
        }
        ,{
            id: '...'
            ,channel: '#devops'
        }
    ]
    ,key: 'trello-key-here'
    ,token: 'trello-token-here'
}

Method 2 (recommended, especially for Heroku deployment)

Do not npm install --save n-trello-slack

Instead, use it as a dependency in my fork of node-trello-slack on GitHub:

• git clone https://github.com/Wraithers/node-trello-slack.git
• The index.js file present is preconfigured for up to 20 boards, add more as needed following the naming conventions
• Do npm install -g config-heroku to store ids, channels, trello key+token and slack webhook in Heroku environment variables
• Add all your secure info to the heroku.json file in config/
• Once all secure info is added, do config-heroku save which will show you all the info being saved in the environment variable HEROKU_CONFIG before interactively saving
• For more info on config-heroku check out the npm package

Getting your Trello and Slack credentials

You'll need a Trello key and token. Get your key here. It's the one in the box near the top labeled "key." Once you have that key, substitute it into the following url for <KEY-HERE> and open it up in a browser tab:

https://trello.com/1/connect?name=node-trello-slack&response_type=token&expiration=never&key=<KEY-HERE>

You'll also need your webhook url for Slack. The domain is just the part of the url before .slack.com. To get your webhook url, go to the following url (substituting your domain for <YOUR-DOMAIN>) and add the webhook integration (if it's not already enabled). The url will appear after the integration is added.

https://<YOUR-DOMAIN>.slack.com/services/new/incoming-webhook

For Method 1, fill all three of these values into the index.js file, and tweak the other options For Method 2, fill all of them in the config/heroku.json file along with the board ids & slack channels

Running...

Once you've configured access to your Trello and Slack accounts, the last thing to know is how this tool knows what events it's already seen. There are two options: File system, and Redis.

...locally (or where the file system is writeable)

The simplest is using the file system. Just create a file named last.id in the root folder of the project and put the number 0 into it. As long as the filesystem is writeable the file will be updated when new board actions have been seen.

...on Heroku (or where the file system is not writeable)

I run this tool on Heroku (a single free dyno works great!) but they dont allow you to write to the filesystem. Instead, I use Redis. Add the free Redis To Go addon and everything should just work out of the box.

heroku create
heroku addons:add redistogo
git push heroku master
heroku ps:scale worker=1 && heroku logs -t

This will push whatever you've got committed in your local git repo up to a new heroku app connected to a free RedisToGo instance, running on a free Heroku worker dyno, and tail the Heroku log file -- just in case there are errors. If no errors appear after a minute or two, just hit ctrl+c to exit the log tail and go about your business.

Enjoy!

The MIT License (MIT)

Copyright (c) 2015 Aaron Khare

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.