This is a wrapper around the Slack RTM and Web APIs.
This library will provide the low level functionality you need to build reliable apps and projects on top of Slack's APIs. It:
- handles reconnection logic and request retries
- provides reasonable defaults for events and logging
- defines a basic model layer and data-store for caching Slack RTM API responses
This library does not attempt to provide application level support, e.g. regex matching and filtering of the conversation stream. If you're looking for those kinds of features, you should check out one of the great libraries built on top of this.
npm install @slack/client --save
IMPORTANT We're moving to NPM organizations, so going forwards the client will be published as a scoped module under the Slack organization.
We'll dual-publish both @slack/client and slack-client until at least 2.1.0 is released, and possibly past that, but please switch over before then.
The Real Time Messaging client connects to Slack's RTM API over a websocket.
It allows you to listen for activity in the Slack team you've connected to and push simple messages back to that team over the websocket.
var RtmClient = require('@slack/client').RtmClient;
var token = process.env.SLACK_API_TOKEN || '';
var rtm = new RtmClient(token, {logLevel: 'debug'});
rtm.start();The RTM client will emit a RTM.AUTHENTICATED event, with the rtm.start payload.
var CLIENT_EVENTS = require('@slack/client').CLIENT_EVENTS;
rtm.on(CLIENT_EVENTS.RTM.AUTHENTICATED, function (rtmStartData) {
});
var RTM_EVENTS = require('@slack/client').RTM_EVENTS;
rtm.on(RTM_EVENTS.MESSAGE, function (message) {
// Listens to all `message` events from the team
});
rtm.on(RTM_EVENTS.CHANNEL_CREATED, function (message) {
// Listens to all `channel_created` events from the team
});var RTM_CLIENT_EVENTS = require('@slack/client').CLIENT_EVENTS.RTM;
// you need to wait for the client to fully connect before you can send messages
rtm.on(RTM_CLIENT_EVENTS.RTM_CONNECTION_OPENED, function () {
// This will send the message 'this is a test message' to the channel identified by id 'C0CHZA86Q'
rtm.sendMessage('this is a test message', 'C0CHZA86Q', function messageSent() {
// optionally, you can supply a callback to execute once the message has been sent
});
});The RTM client has its own lifecycle events. These reflect the different states the RTM client can be in as it connects to Slack's RTM API.
The full details of the client lifecyle are in the RTM client events file
The most important events are:
RTM_CONNECTION_OPENED: the remote server has acked the socket and sent ahellomessage, the connection is now live and can be used to send messagesDISCONNECT: the RTM client has disconnected and will not try to reconnect again automatically
This is an incomplete list of items to consider when you migrate from earlier versions. As issues and PRs are raised for things that don't work as expected we'll fill this out.
The model objects no longer provide utility functions for working with the API. This is to decouple them from the client implementation. There should be functions on each of the clients that allow you to take the same actions you took from the model via the clients instead. The most common of these are below.
channel.sendMessage('test message');becomes
rtmClient.sendMessage('test message', channel.id);channel.postMessage({
attachments: [...]
});becomes
var data = {
attachments: [...]
};
webClient.chat.postMessage(channelId, 'test message', data, function() {});Copyright © Slack Technologies, Inc. MIT License; see LICENSE for further details.