- Create two channels in Slack.
- Name the channel for your timeline something obvious like 'twitter_timeline'.
- Name the channel for posting to Twitter something obvious like 'twitter_post'.
- Get a Slack bot account. Visit https://my.slack.com/services/new and under "DIY Integrations & Customizations" click the "Add" button. Once you create this bot (name it something obvious like "twitter_bot") you will get an API token.
- Invite the bot to the channels you created in step #1. To do that, go to each channel and, in the top drop-down for the channel, click "Invite others to this channel..." and select your bot created in step #2.
- Associate a Twitter account with your Slack team. This is necessary so that Slack will unfurl the tweets, that is, it will show tweet text (and images that people tweet) from this account's timeline. Visit https://my.slack.com/services/twitter and then the "Authentications" tab to set this up.
- Login to the Twitter website Application Management website at https://apps.twitter.com/ with the Twitter account that you want to post tweets to from Slack. (It can be a different Twitter account than the one in step #3.) Click "Create New App". Make sure to give it read and write permissions.
- Set your environment variables. See the section below.
- Start the bot! Use PM2 or forever or something that will daemonize the bot.
Or you could deploy it to Heroku by clicking the button:
You still need to follow steps #1-6 in the above instructions before clicking the button.
Warning: All messages under 140 characters will get posted to Twitter. Only use a channel designated to post tweets from.
This bot uses environment variables to store Slack and Twitter tokens. If you want to run this software locally, use the following as a starting point.
export SLACK_POST_CHANNEL=yourSlackChannelforPostingtoTwitterHere export SLACK_TIMELINE_CHANNEL=yourSlackChannelforReadingtheTwitterTimeline export SLACK_TOKEN=yourSlackTokenHere export TWITTER_CONSUMER_KEY=yourTwitterConsumerKeyHere export TWITTER_CONSUMER_SECRET=yourTwitterConsumerSecretHere export TWITTER_ACCESS_TOKEN_KEY=yourTwitterAccessTokenKeyHere export TWITTER_ACCESS_TOKEN_SECRET=yourTwitterAccessTokenSecretHere
If you're deploying to Heroku, press the Deploy to Heroku button above and you can punch the tokens in the form. If you're deploying from the command line, use the following:
heroku config:set SLACK_POST_CHANNEL=yourSlackChannelforPostingtoTwitterHere heroku config:set SLACK_TIMELINE_CHANNEL=yourSlackChannelforReadingtheTwitterTimeline heroku config:set SLACK_TOKEN=yourSlackTokenHere heroku config:set TWITTER_CONSUMER_KEY=yourTwitterConsumerKeyHere heroku config:set TWITTER_CONSUMER_SECRET=yourTwitterConsumerSecretHere heroku config:set TWITTER_ACCESS_TOKEN_KEY=yourTwitterAccessTokenKeyHere heroku config:set TWITTER_ACCESS_TOKEN_SECRET=yourTwitterAccessTokenSecretHere
- Posting messages to the 'twitter_post' channel will evaluate whether the tweet meets Twitter's definition of 140 characters. That means that URLs are compressed down (and possibly up?) to be either 23 or 24 characters in length. You don't have to short URLs. (You don't have to in general either, not even for analytics, since http://analytics.twitter.com/ handles that now.)
- Faving and unfaving. Starring a tweet in Slack will fave that tweet on Twitter. Unstarring it will unfave it.
- Retweets in a timeline are handled by taking the URL of the retweeted tweet and saying who it was retweeted by.
- No replies or retweeting is currently possible in the 'twitter_post' channel. Use a client for that. In the Slack mobile app, you can specify which Twitter app to use. If you know what you're doing with Automator on Mac OS X, you can add a service to open a URL in Tweetbot
- A memory leak. You may have to manually restart the Node.js bot if tweets stop appearing or tweets no longer get sent from your Slack channel.
- Starring a retweet does not currently work.