Chat Bots

Default Config:

'bots' => [
    'enabled' => env('MESSENGER_BOTS_ENABLED', false),
    'subscriber' => [
        'enabled' => true,
        'queued' => true,
        'channel' => 'messenger-bots',
    ],
],

Bots are disabled by default. When enabled, bots may be created within group threads that explicitly enable the bots feature. A bot may contain many actions, and each action may contain many triggers. Upon a trigger matching a message, the action's handler class will process and respond to the message.
The included event subscriber (BotSubscriber) will listen and react to events that may trigger a bot response. You may choose to enable it, whether it puts jobs on the queue or not, and which queue channel its jobs are dispatched on.
Ready-made bot handlers can be used with the optional Messenger Bots package.

Bots System

Automation

Based on the configs set above, you will want your queue worker listening on the messenger-bots queue to handle bot related jobs.

php artisan queue:work --queue=messenger-bots

To automate purging archived bots and their files from storage, you should schedule the bot purge command at a sensible interval within your applications App\Console\Kernel

<?php

namespace App\Console;

use Illuminate\Console\Scheduling\Schedule;
use Illuminate\Foundation\Console\Kernel as ConsoleKernel;

class Kernel extends ConsoleKernel
{
    /**
     * Define the application's command schedule.
     *
     * @param  \Illuminate\Console\Scheduling\Schedule  $schedule
     * @return void
     */
    protected function schedule(Schedule $schedule)
    {
        $schedule->command('messenger:purge:bots')->dailyAt('6:00');
    }
}

General Flow

Register your custom bot handlers (more on that below).
A bot can be created in a group thread with bots enabled.
The bot will have actions attached, where the actions have triggers and a handler that will be resolved when a match is found against message sent.
When a message is sent, we fire our NewMessageEvent.
The BotSubscriber will listen for the NewMessageEvent, and dispatch the BotActionMessageHandler job.
- This job will only be dispatched if the message sent is from a group thread, not a system message, not from a bot, is a text based message, and its thread has bots enabled.
BotActionMessageHandler will process each active bot on the messages thread, loading all attached actions on the bots, and looping through them to match any triggers against the message sent.
When a trigger is matched against the message, we will instantiate that actions BotActionHandler and execute its handle method.

Success and Failure Events

If a BotActionHandler throws an exception while being handled, it will be caught and dispatched in the BotActionFailedEvent.
Upon a BotActionHandler being handled successfully, the BotActionHandledEvent will be dispatched.
- You must attach your own event listeners to these events if you plan do utilize them.
- Please see the Events Documentation for more information.

Creating Bot Handlers

Create your handler class and extend the BotActionHandler abstract class.

You can use the included command to generate the bot handler class:

php artisan messenger:make:bot TestBot

At the very minimum, your bots class must define a public handle() method and a public static getSettings() method.
Should you need to inject dependencies, you may add your own constructor and type hint any dependencies. Your handler class will be instantiated using laravel's container.

Example

<?php

namespace App\Bots;

use RTippin\Messenger\Actions\Bots\BotActionHandler;
use RTippin\Messenger\MessengerBots;
use Throwable;

class TestBot extends BotActionHandler
{
    /**
     * The bots settings.
     *
     * @return array
     */
    public static function getSettings(): array
    {
        return [
            'alias' => 'testing',
            'description' => 'I am a test bot handler.',
            'name' => 'McTesting!',
            'unique' => true,
            'match' => MessengerBots::MATCH_EXACT,
            'triggers' => ['!test', '!trigger'],
        ];
    }

    /**
     * @throws Throwable
     */
    public function handle(): void
    {
        //Do some magic!
    }
}

`getSettings()`

Must return an array defining the handler's alias, description, and name.

unique, match, and triggers are optional overrides.

alias Used to locate and attach your handler to a bot.
description The description of your bot handler, typically what it does.
name The name of your bot handler.
unique (optional) When set and true, the handler may only be used once per bot.
triggers (optional) Overrides allowing the end user to set the triggers. Only the given trigger(s) will be used. Separate multiple via the pipe (|) or use an array.
match (optional) Overrides allowing end user to select matching method.

Available match methods

any - The action will be triggered for any message sent.
contains - The trigger can be anywhere within a message. Cannot be part of or inside another word.
contains:caseless - Same as "contains", but is case-insensitive.
contains:any - The trigger can be anywhere within a message, including inside another word.
contains:any:caseless - Same as "contains any", but is case-insensitive.
exact - The trigger must match the message exactly.
exact:caseless - Same as "exact", but is case-insensitive.
starts:with - The trigger must be the lead phrase within the message. Cannot be part of or inside another word.
starts:with:caseless - Same as "starts with", but is case-insensitive.

Match method constants

It is recommended to use the match method constants located on the MessengerBots core class.

use RTippin\Messenger\MessengerBots;

MessengerBots::MATCH_ANY;
MessengerBots::MATCH_CONTAINS;
MessengerBots::MATCH_CONTAINS_CASELESS;
MessengerBots::MATCH_CONTAINS_ANY;
MessengerBots::MATCH_CONTAINS_ANY_CASELESS;
MessengerBots::MATCH_EXACT;
MessengerBots::MATCH_EXACT_CASELESS;
MessengerBots::MATCH_STARTS_WITH;
MessengerBots::MATCH_STARTS_WITH_CASELESS;

`handle()`

The handle method will be executed when a matching actions trigger is associated with your bot handler.
When your handle method is called, you will have access to many properties already set by the messenger core.
- Your class will be instantiated using the container, so any dependencies you type-hint in your constructor will be made available when handle is called.
- $this->action provides the current BotAction model that was matched to your handler.
- $this->thread provides the group Thread model we are using.
- $this->message provides the Message model we are using. You can also access the message sender via the owner relation $this->message->owner.
- $this->matchingTrigger provides the trigger that was matched to the message.
- $this->isGroupAdmin boolean for if the message sender is a group admin or not.
- $this->senderIp provides the IP of the message sender.

`getPayload(?string $key = null)`

If your handler stores extra data as a payload, it will be stored as JSON.
getPayload will return the decoded array, with an optional $key to return a specific value.

`getParsedMessage(bool $toLower = false)`

Returns the message with the trigger removed.

`getParsedWords(bool $toLower = false)`

Returns an array of all words in the message with the trigger removed.

`releaseCooldown()`

Calling this will remove any cooldown set on the BotAction model after your handle method is executed.
Cooldowns are optional and are set by the end user, per action. A cooldown will be started right before your handle method is executed.
This is helpful when your handler did not perform an action (perhaps an API call that was denied), and you can ensure any cooldowns defined on that bot action are removed.

`composer()`

Returns a MessengerComposer instance with the TO preset with the Thread our triggering Message belongs to, and FROM preset as the Bot the BotAction triggered belongs to.
- Please note that each time you call $this->composer(), you will be given a new instance.
This has the most common use cases for what a bot may do (message, send an image/audio/document message, add message reaction, knock)
- silent() Silences any broadcast emitted.
- message() Sends a message. Optional reply to ID and extra payload.
- image() Uploads an image message. Optional reply to ID and extra payload.
- document() Uploads a document message. Optional reply to ID and extra payload.
- audio() Uploads an audio message. Optional reply to ID and extra payload.
- video() Uploads a video message. Optional reply to ID and extra payload.
- reaction() Adds a reaction to the message.
- knock() Sends a knock to the current thread.
- read() Marks the thread read for the FROM or set participant.
- emitTyping() Emits a typing presence client event. (Bot typing).
- emitStopTyping() Emits a stopped typing presence client event. (Bot stopped typing).
- emitRead Emits a read presence client event. (Bot read message).

Custom payloads

To allow your handler to store user generated data for later use, you must define the validation rules we will use when the end user is attaching your handler to a bot.
All fields you define in your rules will be serialized and stored as json on the BotAction model your handler gets attached to.
The rules and optional error message overrides use laravel's validator under the hood.

`rules()`

Return the validation rules used when adding the action to a bot. Any rules you define will have their keys/values stored in the action's payload. Return an empty array if you have no extra data to validate or store.

`errorMessages()`

If you define extra validation rules, you may also define the validator error messages here.

`serializePayload(?array $payload)`

This method will be called when the end user adds their custom payload while attaching the action to a bot.
We will store the validated data posted based on your rules defined. By default, this method will json_encode() your data.
You may overwrite this method if you plan to do further sanitization/manipulation of data before it is stored.

Example handler using preset triggers and match method, that sends a welcome message and adds a reaction when triggered.

<?php

namespace App\Bots;

use RTippin\Messenger\Actions\Bots\BotActionHandler;
use RTippin\Messenger\MessengerBots;
use Throwable;

class HelloBot extends BotActionHandler
{
    /**
     * The bots settings.
     *
     * @return array
     */
    public static function getSettings(): array
    {
        return [
            'alias' => 'hello',
            'description' => 'Say hello when someone says hi!',
            'name' => 'Hello Response',
            'triggers' => ['hello', 'hi', 'hey'],
            'match' => MessengerBots::MATCH_CONTAINS_CASELESS,
        ];
    }

    /**
     * @throws Throwable
     */
    public function handle(): void
    {
        $this->composer()->emitTyping()->message("Why hello there {$this->message->owner->getProviderName()}!");

        $this->composer()->reaction($this->message, '👋');
    }
}

Example reply bot, allowing end user to store up to 5 replies to the handler.

<?php

namespace App\Bots;

use RTippin\Messenger\Actions\Bots\BotActionHandler;
use Throwable;

class ReplyBot extends BotActionHandler
{
    /**
     * The bots settings.
     *
     * @return array
     */
    public static function getSettings(): array
    {
        return [
            'alias' => 'reply',
            'description' => 'Reply with the given response(s).',
            'name' => 'Reply',
        ];
    }

    /**
     * @return array
     */
    public function rules(): array
    {
        return [
            'replies' => ['required', 'array', 'min:1', 'max:5'],
            'replies.*' => ['required', 'string'],
        ];
    }

    /**
     * @return array
     */
    public function errorMessages(): array
    {
        return [
            'replies.*.required' => 'Reply is required.',
            'replies.*.string' => 'A reply must be a string.',
        ];
    }

    /**
     * @throws Throwable
     */
    public function handle(): void
    {
        $this->composer()->emitTyping();

        foreach ($this->getPayload('replies') as $reply) {
            $this->composer()->message($reply);
        }
    }
}

Authorization

To authorize the end user add your handler to a bot, you should define the authorize() method and return boolean.
This method will be called during the http request cycle, giving you access to the current auth/session/etc.
- If the end user is unauthorized, the handler will be hidden from appearing in the available handlers list while adding actions to a bot.
- This does NOT authorize being triggered once added to a bot action.

<?php

namespace App\Bots;

use RTippin\Messenger\Actions\Bots\BotActionHandler;
use RTippin\Messenger\MessengerBots;
use Throwable;

class TestBot extends BotActionHandler
{
    /**
     * The bots settings.
     *
     * @return array
     */
    public static function getSettings(): array
    {
        return [
            'alias' => 'testing',
            'description' => 'I am a test bot handler.',
            'name' => 'McTesting!',
            'unique' => true,
            'match' => MessengerBots::MATCH_EXACT,
            'triggers' => ['!test', '!trigger'],
        ];
    }
    
    /**
     * @return bool
     */
    public function authorize(): bool
    {
        return auth()->user()->admin === true;
    }

    /**
     * @throws Throwable
     */
    public function handle(): void
    {
        $this->composer()->emitTyping()->message('I need authorization to be added to a bot!');
    }
}

Register your Handlers

Once you are ready to make your handler available for use, head to your MessengerServiceProvider and add your handler classes using the facade MessengerBots::registerHandlers() method.

<?php

namespace App\Providers;

use App\Bots\HelloBot;
use App\Bots\ReplyBot;
use App\Bots\TestBot;
use Illuminate\Support\ServiceProvider;
use RTippin\Messenger\Facades\MessengerBots;

class MessengerServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        MessengerBots::registerHandlers([
            HelloBot::class,
            ReplyBot::class,
            TestBot::class,
        ]);
    }
}

API Flow

With bots now enabled, and your bot handler's registered, you may use the API to manage a group threads bots.
In order to create a new Bot in your group thread, the group settings must have chat_bots enabled, and the user creating the bot must be a group admin, or a participant with permissions to manage_bots.

Example storing a new bot

axios.post('/api/messenger/threads/{thread}/bots', {
  name: "Test Bot",
  enabled: true,
  hide_actions: false,
  cooldown: 0
});

Once a bot is created, you can view available handler's you may attach to the bot.
When attaching a handler, our base rules that are always required are:
- handler : [string, your handler alias]
- cooldown : [between:0,900]
- admin_only ; [bool]
- enabled : [bool]
If your handler defined the overrides triggers or match, then those parameters you defined can be omitted (backend also ignores) when posting to attach.
When not overridden, the rules are as follows:
- triggers : [array, min:1]
- match : [string, one of our match methods shown above]
Any additional fields required will be those you defined on your handler's rules(), if any.

Example adding our `HelloBot` we made above

The match and triggers are already overridden, and we defined no extra rules on the handler. Only the base rules are required.

axios.post('/api/messenger/threads/{thread}/bots/{bot}/actions', {
  "handler": "hello",
  "cooldown": 0,
  "admin_only": false,
  "enabled": true
});

Example adding our `ReplyBot` we made above

We have no overrides on our ReplyBot, but we did define the custom rule for replies. All rules are required, as well as the extra rules we defined on the handler.

axios.post('/api/messenger/threads/{thread}/bots/{bot}/actions', {
  "handler": "reply",
  "cooldown": 0,
  "admin_only": false,
  "enabled": true,
  "match": "contains:caseless",
  "triggers": [
    "help",
    "support"
  ],
  "replies": [
    "Why are you asking me?",
    "I say google it!"
  ]
});

Now that the bot has been created and is enabled, as well as having both the custom handler's attached, we can trigger them!
For HelloBot, sending a message that contains any of the triggers hello|hi|hey will cause the handler to send our message and reaction!
For ReplyBot, sending a message that contains our triggers help|support will cause the handler to reply with the two messages Why are you asking me? and I say google it!,

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ChatBots.md

ChatBots.md

Chat Bots

Bots System

Automation

General Flow

Success and Failure Events

Creating Bot Handlers

`getSettings()`

Available match methods

Match method constants

`handle()`

`getPayload(?string $key = null)`

`getParsedMessage(bool $toLower = false)`

`getParsedWords(bool $toLower = false)`

`releaseCooldown()`

`composer()`

Custom payloads

`rules()`

`errorMessages()`

`serializePayload(?array $payload)`

Authorization

Register your Handlers

API Flow

Example storing a new bot

Example adding our `HelloBot` we made above

Example adding our `ReplyBot` we made above

Files

ChatBots.md

Latest commit

History

ChatBots.md

File metadata and controls

Chat Bots

Bots System

Automation

General Flow

Success and Failure Events

Creating Bot Handlers

getSettings()

Available match methods

Match method constants

handle()

getPayload(?string $key = null)

getParsedMessage(bool $toLower = false)

getParsedWords(bool $toLower = false)

releaseCooldown()

composer()

Custom payloads

rules()

errorMessages()

serializePayload(?array $payload)

Authorization

Register your Handlers

API Flow

Example storing a new bot

Example adding our HelloBot we made above

Example adding our ReplyBot we made above

`getSettings()`

`handle()`

`getPayload(?string $key = null)`

`getParsedMessage(bool $toLower = false)`

`getParsedWords(bool $toLower = false)`

`releaseCooldown()`

`composer()`

`rules()`

`errorMessages()`

`serializePayload(?array $payload)`

Example adding our `HelloBot` we made above

Example adding our `ReplyBot` we made above