This is the maintenance branch for the legacy version of Botkit (< 0.7.4).
Only security and bug fix updates will be made to this branch!
If you are starting a new project, use the 4+ version found here.
You can also add Botkit into an existing Node application.
First, add it to your project:
npm install --save [email protected]
Then, add Botkit to your application code:
var Botkit = require('botkit');
var controller = Botkit.anywhere(configuration);
controller.hears('hello','direct_message', function(bot, message) {
bot.reply(message,'Hello yourself!');
});
Review the documentation to learn how to configure Botkit's controller to work with the messaging platform of your choice.
The goal of Botkit is to make it easier and more fun to build software that talks and works like a robot! Building a bot should feel cool, and not too technically complicated.
Botkit handles all the nitty gritty details like API calls, session management and authentication, allowing you to focus on building COOL FEATURES for your bot using middleware and event handlers.
The toolkit is designed to provide meaningful building blocks for creating conversational user interfaces - with functions like hears()
, ask()
, and reply()
that do what they say they do.
Most bots do their thing by listening for keywords, phrases or patterns in messages from users. Botkit has a special event handler called hears()
that makes it easy to configure your bot to listen for this type of trigger.
controller.hears(['string','pattern .*',new RegExp('.*','i')],'message_received,other_event',function(bot, message) {
// do something!
bot.reply(message, 'I heard a message.')
});
Read more about hearing things ›
Bots can respond to non-verbal events as well, like when a new user joins a channel, a file gets uploaded, or a button gets clicked. These events are handled using an event handling pattern that should look familiar. Most events in Botkit can be replied to like normal messages.
controller.on('channel_join', function(bot, message) {
bot.reply(message,'Welcome to the channel!');
});
See a full list of events and more information about handling them ›
In addition to taking direct action in response to a certain message or type of event, Botkit can also take passive action on messages as they move through the application using middlewares. Middleware functions work by changing messages, adding new fields, firing alternate events, and modifying or overriding the behavior of Botkit's core features.
Middleware can be used to adjust how Botkit receives, processes, and sends messages. Here is a list of available middleware endpoints.
// Log every message received
controller.middleware.receive.use(function(bot, message, next) {
// log it
console.log('RECEIVED: ', message);
// modify the message
message.logged = true;
// continue processing the message
next();
});
// Log every message sent
controller.middleware.send.use(function(bot, message, next) {
// log it
console.log('SENT: ', message);
// modify the message
message.logged = true;
// continue processing the message
next();
});
- Get Started
- Introduction
- Core Features
- Botkit Studio API
- Platforms
- Extending Botkit with Plugins and Middleware
- Storing Information
- Logging
- Contributing to Botkit
Join our thriving community of Botkit developers and bot enthusiasts at large. Over 6500 members strong, our open Slack group is the place for people interested in the art and science of making bots. Come to ask questions, share your progress, and commune with your peers!
You can also find help from members of the Botkit team in our dedicated Cisco Spark room!
We also host a regular meetup and annual conference called TALKABOT. Come meet and learn from other bot developers! Full video of our 2016 event is available on Youtube.
Botkit is a product of Howdy.ai.
Want to contribute? Read the contributor guide
Botkit is released under the MIT Open Source license