Bot Connector allows you to connect your bot to multiple messaging channels.
It provides a higher level API to manage several messaging platforms at once, and lets you focus on your bot by using a simple and unique format to talk to the entire world.
Generate the documentation with the following command:
docker-compose run mandrake-connector yarn doc
Bot Connector supports the following channels:
You can find more information on each channel in the wiki
Docker is required to build and start mandrake. Click here for setup instructions
Clone the repository and install the dependencies
git clone https://github.com/yantrashala/mandrake-connector.git
docker-compose build
docker-compose up
First of all, you need to create a connector with the Bot Connector's API.
curl -X POST 'http://localhost:8080/connectors' --data 'url=YOUR_CONNECTOR_ENDPOINT_URL'
Now that your bot (well, your code) and the Bot Connector are running, you have to create channels. Channel is the actual link between your connector and a specific service like Messenger, Slack or Kik. A connector can have multiple channels.
There are two distinct flows:
- your bot receive a message from a channel
- your bot send a message to a channel
This pipeline allows us to have an abstraction of messages independent of the platform and implement only a few functions for each messaging platform (input and output parsing).
The Bot Connector posts on your connector's endpoint each time a new message arrives from a channel.
- a new message is received by Bot Connector
- the message is parsed by the corresponding service
- the message is saved in MongoDB
- the message is post to the connector endpoint
To send a new message, you have to post it to Bot Connector's API
- the messages are saved in MongoDB
- the messages are formatted by the corresponding service to match the channel's format
- the messages are sent by Bot Connector to the corresponding channel
All messages coming from the bot are parsed and modified to match the destination channel specifications. Bot Connector supports several message formats:
- Text message:
[{
type: 'text',
content: 'My text message',
}]
- Quick Replies:
[{
type: 'quickReplies',
content: {
title: 'My title',
buttons: [
{
title: 'Button title',
value: 'Button value',
},
]
}
}]
- Cards:
[{
type: 'card',
content: {
title: 'My card title',
imageUrl: 'url_to_my_image',
subtitle: 'My card subtitle',
buttons: [
{
title: 'My button title',
type: 'My button type', // See Facebook Messenger button formats
value: 'My button value',
}
],
},
}]
- Pictures:
[{
type: 'picture',
content: 'url_to_my_image',
}]
- Videos:
[{
type: 'video',
content: 'url_to_my_video',
}]
If you encounter any issue, please follow this guide.
Want to contribute? Great! Please check this guide.
Copyright (c) [2016] Recast.AI
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.