PHP Classes
elePHPant
Icontem

PHP Slack Bot: Robot to automate interactions with Slack users

Recommend this page to a friend!
  Info   View files Documentation   View files View files (91)   DownloadInstall with Composer Download .zip   Reputation   Support forum   Blog    
Last Updated Ratings Unique User Downloads Download Rankings
2017-01-19 (Less than 1 hour ago) RSS 2.0 feedNot enough user ratingsTotal: 147 This week: 29All time: 8,254 This week: 33Up
Version License PHP version Categories
slackbot 1.0.23MIT/X Consortium ...5PHP 5, Web services, Chat, Social Net...
Description Author

This package can implement robots to automate interactions with Slack users.

It can listen to messages sent by users that match certain keywords and invokes a given callback function, so the bot can process and eventually reply to the messages.

The package can also extract certain patterns of the incoming messages and pass them to the callback function.

It can also create interactive conversations by sending messages to users and handling the responses with a callback function.

Innovation Award
PHP Programming Innovation award nominee
November 2016
Number 10
Slack is an application that has grown a lot in popularity as a communication application for teams that collaborate in the same project.

It provides an API that allows developers to create robot applications that can interact with Slack users.

This package can listen to messages sent by users and process them to generate useful replies.

It can also create interactive conversations by sending messages to users and handling the responses.

Manuel Lemos
Name: Marcel Pociot <contact>
Classes: 1 package by
Country: Germany Germany
Age: ???
All time rank: 3939219 in Germany Germany
Week rank: 38 Up2 in Germany Germany Up
Innovation award
Innovation award
Nominee: 1x

Details

PHP BotMan ? Create messaging bots in PHP with ease

Latest Version on Packagist Build Status codecov Scrutinizer Code Quality [Packagist]() StyleCI

BotMan is a framework agnostic PHP library that is designed to simplify the task of developing innovative bots for multiple messaging platforms, including Slack, Telegram, Microsoft Bot Framework, Nexmo, HipChat, Facebook Messenger and WeChat.

$botman->hears('I want cross-platform bots with PHP!', function (BotMan $bot) {
    $bot->reply('Look no further!');
});

Getting Started

> Want to get started even faster? Use the BotMan Laravel Starter Project!

  1. Open the Laravel/Symfony/PHP project your new Bot will live in
  2. Install BotMan with composer
  3. Configure your messaging platform
  4. Implement your bot logic

Installation using Composer

Require this package with composer using the following command:

$ composer require mpociot/botman

Basic Usage

This sample bot listens for the word "hello" - either in a direct message (a private message inside Slack between the user and the bot) or in a message the bot user is invited to.

use Mpociot\BotMan\BotManFactory;
use Mpociot\BotMan\BotMan;

$config = [
    'hipchat_urls' => [
        'YOUR-INTEGRATION-URL-1',
        'YOUR-INTEGRATION-URL-2',
    ],
    'nexmo_key' => 'YOUR-NEXMO-APP-KEY',
    'nexmo_secret' => 'YOUR-NEXMO-APP-SECRET',
    'microsoft_bot_handle' => 'YOUR-MICROSOFT-BOT-HANDLE',
    'microsoft_app_id' => 'YOUR-MICROSOFT-APP-ID',
    'microsoft_app_key' => 'YOUR-MICROSOFT-APP-KEY',
    'slack_token' => 'YOUR-SLACK-TOKEN-HERE',
    'telegram_token' => 'YOUR-TELEGRAM-TOKEN-HERE',
    'facebook_token' => 'YOUR-FACEBOOK-TOKEN-HERE',
    'facebook_app_secret' => 'YOUR-FACEBOOK-APP-SECRET-HERE', // Optional - this is used to verify incoming API calls,
    'wechat_app_id' => 'YOUR-WECHAT-APP-ID',
    'wechat_app_key' => 'YOUR-WECHAT-APP-KEY',
];

// create an instance
$botman = BotManFactory::create($config);

// give the bot something to listen for.
$botman->hears('hello', function (BotMan $bot) {
    $bot->reply('Hello yourself.');
});

// start listening
$botman->listen();

Using BotMan within a Laravel app

BotMan comes with a Service Provider to make using this library in your Laravel application as simple as possible.

Go to your config/app.php and add the service provider:

Mpociot\BotMan\BotManServiceProvider::class,

Also add the alias / facade:

'BotMan' => Mpociot\BotMan\Facades\BotMan::class

Add your Facebook access token / Slack token to your config/services.php:

'botman' => [
    'hipchat_urls' => [
        'YOUR-INTEGRATION-URL-1',
        'YOUR-INTEGRATION-URL-2',
    ],
    'nexmo_key' => 'YOUR-NEXMO-APP-KEY',
    'nexmo_secret' => 'YOUR-NEXMO-APP-SECRET',
    'microsoft_bot_handle' => 'YOUR-MICROSOFT-BOT-HANDLE',
    'microsoft_app_id' => 'YOUR-MICROSOFT-APP-ID',
    'microsoft_app_key' => 'YOUR-MICROSOFT-APP-KEY',
    'slack_token' => 'YOUR-SLACK-TOKEN-HERE',
    'telegram_token' => 'YOUR-TELEGRAM-TOKEN-HERE',
    'facebook_token' => 'YOUR-FACEBOOK-TOKEN-HERE',
    'facebook_app_secret' => 'YOUR-FACEBOOK-APP-SECRET-HERE' // Optional - this is used to verify incoming API calls,
    'wechat_app_id' => 'YOUR-WECHAT-APP-ID',
    'wechat_app_key' => 'YOUR-WECHAT-APP-KEY',
],

Using it:

use Mpociot\BotMan\BotMan;

$botman = app('botman');

$botman->hears('hello', function (BotMan $bot) {
    $bot->reply('Hello yourself.');
});

// start listening
$botman->listen();

Make sure that your controller method doesn't use the CSRF token middleware.

That's it.

Configuration

Cache

If not specified otherwise, BotMan will use `array` cache which is non-persistent. When using the Laravel facade it will automatically use the Laravel Cache component.

Doctrine Cache

Use any Doctrine Cache driver by passing it to the factory:

use Mpociot\BotMan\Cache\DoctrineCache;

$botman = BotManFactory::create($config, new DoctrineCache($doctrineCacheDriver));

Symfony Cache

Use any Symfony Cache adapter by passing it to the factory:

use Mpociot\BotMan\Cache\SymfonyCache;

$botman = BotManFactory::create($config, new SymfonyCache($symfonyCacheAdapter));

CodeIgniter Cache

Use any CodeIgniter Cache adapter by passing it to the factory:

use Mpociot\BotMan\Cache\CodeIgniterCache;

$this->load->driver('cache');
$botman = BotManFactory::create($config, new CodeIgniterCache($this->cache->file));

Connect with your messaging service

After you've installed BotMan, the first thing you'll need to do is register your bot with a messaging platform, and get a few configuration options set. This will allow your bot to connect, send and receive messages.

You can support all messaging platforms using the exact same Bot-API.

Core Concepts

Bots built with BotMan have a few key capabilities, which can be used to create clever, conversational applications. These capabilities map to the way real human people talk to each other.

Bots can hear things, say things and reply to what they hear.

With these two building blocks, almost any type of conversation can be created.

Developing with BotMan

Table of Contents

Receiving Messages

Driver specific information

BotMan can listen to many different messaging drivers and therefore it might be required for you, to respond differently depending on which driver was used to respond to your message.

Each messaging driver in BotMan has a getName() method, that returns a human readable name of the driver.

You can access the driver object using $botman->getDriver(). To match against the driver name, you can use each driver's NAME constant or use the table below.

The available driver names are:

| Driver | Name |--- |--- | BotFrameworkDriver | BotFramework | FacebookDriver | Facebook | HipChatDriver | HipChat | NexmoDriver | Nexmo | SlackDriver | Slack | TelegramDriver | Telegram

Matching Patterns and Keywords with hears()

BotMan provides a hears() function, which will listen to specific patterns in public and/or private channels.

| Argument | Description |--- |--- | pattern | A string with a regular expressions to match | callback | Callback function or Classname@method notation that receives a BotMan object, as well as additional matching regular expression parameters

$botman->hears('keyword', function(BotMan $bot) {
    // do something to respond to message
    $bot->reply('You used a keyword!');
});

$botman->hears('keyword', 'MyClass@heardKeyword');

You can restrict commands to specific messaging drivers, using the fluent API:

// Restrict to Slack driver
$botman->hears('keyword', function(BotMan $bot) {
    // do something to respond to message
    $bot->reply('You used a keyword!');
})->driver(SlackDriver::DRIVER_NAME);

// Restrict to Slack and Telegram driver
$botman->hears('keyword', function(BotMan $bot) {
    // do something to respond to message
    $bot->reply('You used a keyword!');
})->driver([SlackDriver::DRIVER_NAME, TelegramDriver::DRIVER_NAME]);

When using the built in regular expression matching, the results of the expression will be passed to the callback function. For example:

$botman->hears('open the {doorType} doors', function(BotMan $bot, $doorType) {
    if ($doorType === 'pod bay') {
        return $bot->reply('I\'m sorry, Dave. I\'m afraid I can\'t do that.');
    }

    return $bot->reply('Okay');
});

Fallback replies

If you want to provide your bot users with a fallback reply, if they enter a command that you don't understand, you can use the fallback method on the BotMan instance.

$botman->fallback(function(BotMan $bot) {
    return $bot->reply('Sorry I do not know this command');
});

Middleware

The usage of custom middleware allows you to enrich the messages your bot received with additional information from third party services such as wit.ai or api.ai.

To let your BotMan instance make use of a middleware, simply add it to the list of middlewares:

$botman->middleware(Wit::create('MY-WIT-ACCESS-TOKEN'));
$botman->hears('emotion', function($bot) {
    $extras = $bot->getMessage()->getExtras();
    // Access extra information
    $entities = $extras['entities'];
});

The current Wit.ai middleware will send all incoming text messages to wit.ai and adds the entities received from wit.ai back to the message. You can then access the information using $bot->getMessage()->getExtras(). This method returns an array containing all wit.ai entities.

If you only want to get a single element of the extras, you can optionally pass a key to the getExtras method. If no matching key was found, the method will return null.

In addition to that, it will check against a custom trait entity called intent instead of using the built-in matching pattern.

Sending Messages

Bots have to send messages to deliver information and present an interface for their functionality. BotMan bots can send messages in several different ways, depending on the type and number of messages that will be sent.

Single message replies to incoming commands can be sent using the $bot->reply() function.

Multi-message replies, particularly those that present questions for the end user to respond to, can be sent using the $bot->startConversation() function and the related conversation sub-functions.

Bots can originate messages - that is, send a message based on some internal logic or external stimulus - using $bot->say() method.

Single Message Replies to Incoming Messages

Once a bot has received a message using hears(), a response can be sent using $bot->reply().

Messages sent using $bot->reply() are sent immediately. If multiple messages are sent via $bot->reply() in a single event handler, they will arrive in the client very quickly and may be difficult for the user to process. We recommend using $bot->startConversation() if more than one message needs to be sent.

You may pass either a string, a Message object or a Question object to the function.

As a second parameter, you may also send any additional fields to pass along the configured driver.

$bot->reply()

| Argument | Description |--- |--- | reply | _String_ or _Message_ or _Question_ Outgoing response | additionalParameters | _Optional_ Array containing additional parameters

Simple reply example:

$botman->hears('keyword', function (BotMan $bot) {
    // do something to respond to message
    // ...

    $bot->reply("Tell me more!");
});

You can also compose your message using the Mpociot\BotMan\Messages\Message class to have a unified API to add images to your chat messages.

use Mpociot\BotMan\Messages\Message;

$botman->hears('keyword', function (BotMan $bot) {
    // Build message object
    $message = Message::create('This is my text')
                ->image('http://www.some-url.com/image.jpg');
    // Reply message object
    $bot->reply($message);
});

Slack-specific fields and attachments:

$botman->hears('keyword', function (BotMan $bot) {
    // do something...

    // then respond with a message object
    $bot->reply("A more complex response",[
        'username' => "ReplyBot",
        'icon_emoji' => ":dash:",
    ]);
})

Multi-message Replies to Incoming Messages

For more complex commands, multiple messages may be necessary to send a response, particularly if the bot needs to collect additional information from the user.

BotMan provides a Conversation object that is used to string together several messages, including questions for the user, into a cohesive unit. BotMan conversations provide useful methods that enable developers to craft complex conversational user interfaces that may span several minutes of dialog with a user, without having to manage the complexity of connecting multiple incoming and outgoing messages across multiple API calls into a single function.

Start a Conversation

$bot->startConversation()

| Argument | Description |--- |--- | conversation | A Conversation object

startConversation() is a function that creates conversation in response to an incoming message. You can control where the bot should start the conversation by calling startConversation in the hears() method of your bot.

Simple conversation example:

$botman->hears('start conversation', function (BotMan $bot) {
    $bot->startConversation(new PizzaConversation);
});

Creating Conversations

When starting a new conversation using the startConversation() method, you need to pass the method the conversation that you want to start gathering information with. Each conversation object needs to extend from the BotMan Conversation object and must implement a simple run() method.

This is the very first method that gets executed when the conversation starts.

Example conversation object:

class PizzaConversation extends Conversation
{
    protected $size;

    public function askSize()
    {
        $this->ask('What pizza size do you want?', function(Answer $answer) {
            // Save size for next question
            $this->size = $answer->getText();

            $this->say('Got it. Your pizza will be '.$answer->getText());
        });
    }

    public function run()
    {
        // This will be called immediately
        $this->askSize();
    }
}

Control Conversation Flow

$conversation->say()

| Argument | Description |--- |--- | message | String or Question object

Call $conversation->say() several times in a row to queue messages inside the conversation. Only one message will be sent at a time, in the order in which they are queued.

$conversation->ask()

| Argument | Description |--- |--- | message | String or Question object | callback _or_ array of callbacks | callback function in the form function($answer), or array of arrays in the form `[ 'pattern' => regular_expression, 'callback' => function($answer) { ... } ]`

When passed a callback function, $conversation->ask will execute the callback function for any response. This allows the bot to respond to open-ended questions, collect the responses, and handle them in whatever manner it needs to.

When passed an array, the bot will look first for a matching pattern, and execute only the callback whose pattern is matched. This allows the bot to present multiple choice options, or to proceed only when a valid response has been received. The patterns can have the same placeholders as the $bot->reply() method has. All matching parameters will be passed to the callback function.

Callback functions passed to ask() receive (at least) two parameters - the first is an Answer object containing the user's response to the question. If the conversation continues because of a matching pattern, all matching pattern parameters will be passed to the callback function too. The last parameter is always a reference to the conversation itself.

Using $conversation->ask with a callback:

// ...inside the conversation object...
public function askMood()
{
    $this->ask('How are you?', function (Answer $response) {
        $this->say('Cool - you said ' . $response->getText());
    });
}

Using $conversation->ask with an array of callbacks:

// ...inside the conversation object...
public function askNextStep()
{
    $this->ask('Shall we proceed? Say YES or NO', [
        [
            'pattern' => 'yes|yep',
            'callback' => function () {
                $this->say('Okay - we\'ll keep going');
            }
        ],
        [
            'pattern' => 'nah|no|nope',
            'callback' => function () {
                $this->say('PANIC!! Stop the engines NOW!');
            }
        ]
    ]);
}

Using $conversation->ask with a Question object

Instead of passing a string to the ask() method, it is also possible to create a Question object. The Question objects make use of the interactive messages from Facebook, Telegram and Slack to present the user buttons to interact with.

When passing question objects to the ask() method, the returned Answer object has a method called isInteractiveMessageReply to detect, if the user interacted with the message and clicked on a button.

Creating a simple Question object:

// ...inside the conversation object...
public function askForDatabase()
{
    $question = Question::create('Do you need a database?')
        ->fallback('Unable to create a new database')
        ->callbackId('create_database')
        ->addButtons([
            Button::create('Of course')->value('yes'),
            Button::create('Hell no!')->value('no'),
        ]);

    $this->ask($question, function (Answer $answer) {
        // Detect if button was clicked:
        if ($answer->isInteractiveMessageReply()) {
            $selectedValue = $answer->getValue(); // will be either 'yes' or 'no'
            $selectedText = $answer->getText(); // will be either 'Of course' or 'Hell no!'
        }
    });
}

Originating Messages

$bot->say()

| Argument | Description |--- |--- | message | _String_ or _Question_ The message you want to send | channel | _String_ A string containing the channel you want to send the message to. | driver | _Optional_ A DriverInterface class name to use when sending the message

Simple example:

$botman->say('Hello user', 'U123456789');

Specific driver example:

$botman->say('Hello user', 'U123456789', FacebookDriver::class);

Note: The channel argument depends on the driver(s) you plan to use for sending messages.

| Driver | Channel type |--- |--- | BotFrameworkDriver | Skype / Framework User ID | FacebookDriver | Facebook User ID | HipChatDriver | HipChat User ID | NexmoDriver | Phone number | SlackDriver | Slack User/Channel ID | TelegramDriver | Telegram User ID

Long running tasks

BotMan uses the Webhook APIs to get information from the messaging system. When the messaging system of your choice sends the information to your app, you have 3 seconds to return an HTTP 2xx status. Otherwise, the delivery attempt will be considered as a failure and the messaging system will attempt to deliver the message up to three more times.

This means that you should push long running tasks into an asynchronous queue.

Queue example using Laravel:

// ...inside the conversation object...
public function askDomainName()
{
    $this->ask('What should be the domain name?', function (Answer $answer) {
        // Push long running task onto the queue.
        $this->reply('Okay, creating subdomain ' . $answer->getText());
        dispatch(new CreateSubdomain($this, $answer->getText()));
    });
}

Storing Information

BotMan has a builtin storage system, which you can use to store user, team or driver specific information without having the need for conversations. By default, BotMan will use a simple JSON file storage to keep the data in the filesystem.

To access the different storage types, BotMan provides these functions:

userStorage() - Will give you a storage that automatically uses the current message user as the default key. channelStorage() - Will give you a storage that automatically uses the current message channel as the default key. driverStorage() - Will give you a storage that automatically uses the current driver name as the default key.

Example usage

$botman->hears("forget me", function (BotMan $bot) {
    // Delete all stored information. 
    $bot->userStorage()->delete();
});

$botman->hears("call me {name}", function (BotMan $bot, $name) {
    // Store information for the currently logged in user.
    // You can also pass a user-id / key as a second parameter.
    $bot->userStorage()->save([
        'name' => $name
    ]);

    $bot->reply('I will call you '.$name);
});

$botman->hears("who am I", function (BotMan $bot) {
    // Retrieve information for the currently logged in user.
    // You can also pass a user-id / key as a second parameter.
    $user = $bot->userStorage()->get();

    if ($user->has('name')) {
        $bot->reply('You are '.$user->get('name'));
    } else {
        $bot->reply('I do not know you yet.');
    }
});

License

BotMan is free software distributed under the terms of the MIT license.

  Files folder image Files  
File Role Description
Files folder imagesrc (1 directory)
Files folder imagetests (10 files, 6 directories)
Accessible without login Plain text file .php_cs Data Auxiliary data
Accessible without login Plain text file .styleci.yml Data Auxiliary data
Accessible without login Plain text file .travis.yml Data Auxiliary data
Accessible without login Plain text file CHANGELOG.md Data Auxiliary data
Accessible without login Plain text file composer.json Data Auxiliary data
Accessible without login Plain text file LICENSE Lic. License text
Accessible without login Plain text file phpunit.xml Data Auxiliary data
Accessible without login Plain text file readme-botframework.md Doc. Documentation
Accessible without login Plain text file readme-facebook.md Doc. Documentation
Accessible without login Plain text file readme-hipchat.md Doc. Documentation
Accessible without login Plain text file readme-nexmo.md Doc. Documentation
Accessible without login Plain text file readme-slack.md Doc. Documentation
Accessible without login Plain text file readme-telegram.md Doc. Documentation
Accessible without login Plain text file readme-wechat.md Doc. Documentation
Accessible without login Plain text file README.md Doc. Documentation

  Files folder image Files  /  src  
File Role Description
Files folder imageMpociot (1 directory)

  Files folder image Files  /  src  /  Mpociot  
File Role Description
Files folder imageBotMan (10 files, 9 directories)

  Files folder image Files  /  src  /  Mpociot  /  BotMan  
File Role Description
Files folder imageCache (5 files)
Files folder imageDrivers (11 files)
Files folder imageFacades (1 file)
Files folder imageHttp (1 file)
Files folder imageInterfaces (5 files)
Files folder imageMessages (1 file)
Files folder imageMiddleware (2 files)
Files folder imageStorages (1 file, 1 directory)
Files folder imageTraits (2 files)
  Plain text file Answer.php Class Class source
  Plain text file BotMan.php Class Class source
  Plain text file BotManFactory.php Class Class source
  Plain text file BotManServiceProvider.php Class Class source
  Plain text file Button.php Class Class source
  Plain text file Command.php Class Class source
  Plain text file Conversation.php Class Class source
  Plain text file DriverManager.php Class Class source
  Plain text file Message.php Class Class source
  Plain text file Question.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Cache  
File Role Description
  Plain text file ArrayCache.php Class Class source
  Plain text file CodeIgniterCache.php Class Class source
  Plain text file DoctrineCache.php Class Class source
  Plain text file LaravelCache.php Class Class source
  Plain text file SymfonyCache.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Drivers  
File Role Description
  Plain text file BotFrameworkDriver.php Class Class source
  Plain text file Driver.php Class Class source
  Plain text file FacebookDriver.php Class Class source
  Plain text file FacebookPostbackDriver.php Class Class source
  Plain text file HipChatDriver.php Class Class source
  Plain text file NexmoDriver.php Class Class source
  Plain text file NullDriver.php Class Class source
  Plain text file SlackDriver.php Class Class source
  Plain text file SlackRTMDriver.php Class Class source
  Plain text file TelegramDriver.php Class Class source
  Plain text file WeChatDriver.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Facades  
File Role Description
  Plain text file BotMan.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Http  
File Role Description
  Plain text file Curl.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Interfaces  
File Role Description
  Plain text file CacheInterface.php Class Class source
  Plain text file DriverInterface.php Class Class source
  Plain text file HttpInterface.php Class Class source
  Plain text file MiddlewareInterface.php Class Class source
  Plain text file StorageInterface.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Messages  
File Role Description
  Plain text file Message.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Middleware  
File Role Description
  Plain text file ApiAi.php Class Class source
  Plain text file Wit.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Storages  
File Role Description
Files folder imageDrivers (1 file)
  Plain text file Storage.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Storages  /  Drivers  
File Role Description
  Plain text file FileStorage.php Class Class source

  Files folder image Files  /  src  /  Mpociot  /  BotMan  /  Traits  
File Role Description
  Plain text file ProvidesStorage.php Class Class source
  Plain text file VerifiesServices.php Class Class source

  Files folder image Files  /  tests  
File Role Description
Files folder imageCache (4 files)
Files folder imageDrivers (9 files)
Files folder imageFixtures (7 files)
Files folder imageMessages (1 file)
Files folder imageMiddleware (2 files)
Files folder imageStorages (3 files)
  Plain text file AnswerTest.php Class Class source
  Plain text file BotManFactoryTest.php Class Class source
  Plain text file BotManTest.php Class Class source
  Plain text file ButtonTest.php Class Class source
  Plain text file ConversationTest.php Class Class source
  Plain text file DriverManagerTest.php Class Class source
  Plain text file LaravelTest.php Class Class source
  Plain text file MessageTest.php Class Class source
  Plain text file QuestionTest.php Class Class source
  Plain text file VerifiesServicesTest.php Class Class source

  Files folder image Files  /  tests  /  Cache  
File Role Description
  Plain text file ArrayCacheTest.php Class Class source
  Plain text file CodeIgniterCacheTest.php Class Class source
  Plain text file DoctrineCacheTest.php Class Class source
  Plain text file SymfonyCacheTest.php Class Class source

  Files folder image Files  /  tests  /  Drivers  
File Role Description
  Plain text file BotFrameworkDriverTest.php Class Class source
  Plain text file FacebookDriverTest.php Class Class source
  Plain text file FacebookPostbackDriverTest.php Class Class source
  Plain text file HipChatDriverTest.php Class Class source
  Plain text file NexmoDriverTest.php Class Class source
  Plain text file SlackDriverTest.php Class Class source
  Plain text file SlackRTMDriverTest.php Class Class source
  Plain text file TelegramDriverTest.php Class Class source
  Plain text file WeChatDriverTest.php Class Class source

  Files folder image Files  /  tests  /  Fixtures  
File Role Description
  Accessible without login Plain text file payload.json Data Auxiliary data
  Plain text file TestClass.php Class Class source
  Plain text file TestConversation.php Class Class source
  Plain text file TestDriver.php Class Class source
  Plain text file TestMatchMiddleware.php Class Class source
  Plain text file TestMiddleware.php Class Class source
  Plain text file TestNoMatchMiddleware.php Class Class source

  Files folder image Files  /  tests  /  Messages  
File Role Description
  Plain text file MessageTest.php Class Class source

  Files folder image Files  /  tests  /  Middleware  
File Role Description
  Plain text file ApiAiTest.php Class Class source
  Plain text file WitTest.php Class Class source

  Files folder image Files  /  tests  /  Storages  
File Role Description
  Plain text file BotManStorageTest.php Class Class source
  Plain text file FileStorageTest.php Class Class source
  Plain text file StorageTest.php Class Class source

 Version Control Unique User Downloads Download Rankings  
 100%
Total:147
This week:29
All time:8,254
This week:33Up