Important
This repository is only sporadically maintained. Breaking API changes will be maintained on a best efforts basis.
Collaborators are welcome, as are PRs for enhancements.
Bug reports unrelated to API changes may not get the attention you want.
By using this module, you can create a Webex Teams messaging bot quickly in just a couple of lines of code.
This module does not require you to set up an ngrok tunnel to receive incoming messages when behind a firewall or inside a LAN. This package instead uses a websocket to receive messages from the Webex cloud.
- Uses the websockets module to receive incoming messages, thus avoiding the need to have a public IP or use incoming webhooks.
- Simply add 'commands' which are just strings which instruct the bot to perform some action and reply with some result.
- Allows for single or multi-post responses. This is useful if you want to reply with a lot of data, but it won't all fit in a single response.
- Restrict bot to certain users or domains.
- Uses the webexteamssdk package to send back replies from the bot.
You can find a sample project, using OpenAI/ChatGPT with this library here: https://github.com/fbradyirl/openai_bot
Only Python 3.9 is tested at this time.
- Install this module from pypi:
pip install webex_bot
If you need optional proxy support, use this command instead:
pip install webex_bot[proxy]
- On the Webex Developer portal, create a new bot token and expose it as an environment variable.
export WEBEX_TEAMS_ACCESS_TOKEN=<your bots token>
- Run your script:
python example.py
See example.py for details:
import os
from webex_bot.commands.echo import EchoCommand
from webex_bot.webex_bot import WebexBot
# (Optional) Proxy configuration
# Supports https or wss proxy, wss prioritized.
proxies = {
'https': 'http://proxy.esl.example.com:80',
'wss': 'socks5://proxy.esl.example.com:1080'
}
# Create a Bot Object
bot = WebexBot(teams_bot_token=os.getenv("WEBEX_TEAMS_ACCESS_TOKEN"),
approved_rooms=['06586d8d-6aad-4201-9a69-0bf9eeb5766e'],
bot_name="My Teams Ops Bot",
include_demo_commands=True,
proxies=proxies)
# Add new commands for the bot to listen out for.
bot.add_command(EchoCommand())
# Call `run` for the bot to wait for incoming messages.
bot.run()
where EchoCommand is defined as:
import logging
from webexteamssdk.models.cards import Colors, TextBlock, FontWeight, FontSize, Column, AdaptiveCard, ColumnSet, \
Text, Image, HorizontalAlignment
from webexteamssdk.models.cards.actions import Submit
from webex_bot.formatting import quote_info
from webex_bot.models.command import Command
from webex_bot.models.response import response_from_adaptive_card
log = logging.getLogger(__name__)
class EchoCommand(Command):
def __init__(self):
super().__init__(
command_keyword="echo",
help_message="Echo Words Back to You!",
chained_commands=[EchoCallback()])
def pre_execute(self, message, attachment_actions, activity):
"""
(optional function).
Reply before running the execute function.
Useful to indicate the bot is handling it if it is a long running task.
:return: a string or Response object (or a list of either). Use Response if you want to return another card.
"""
image = Image(url="https://i.postimg.cc/2jMv5kqt/AS89975.jpg")
text1 = TextBlock("Working on it....", weight=FontWeight.BOLDER, wrap=True, size=FontSize.DEFAULT,
horizontalAlignment=HorizontalAlignment.CENTER, color=Colors.DARK)
text2 = TextBlock("I am busy working on your request. Please continue to look busy while I do your work.",
wrap=True, color=Colors.DARK)
card = AdaptiveCard(
body=[ColumnSet(columns=[Column(items=[image], width=2)]),
ColumnSet(columns=[Column(items=[text1, text2])]),
])
return response_from_adaptive_card(card)
def execute(self, message, attachment_actions, activity):
"""
If you want to respond to a submit operation on the card, you
would write code here!
You can return text string here or even another card (Response).
This sample command function simply echos back the sent message.
:param message: message with command already stripped
:param attachment_actions: attachment_actions object
:param activity: activity object
:return: a string or Response object (or a list of either). Use Response if you want to return another card.
"""
text1 = TextBlock("Echo", weight=FontWeight.BOLDER, size=FontSize.MEDIUM)
text2 = TextBlock("Type in something here and it will be echo'd back to you. How useful is that!",
wrap=True, isSubtle=True)
input_text = Text(id="message_typed", placeholder="Type something here", maxLength=30)
input_column = Column(items=[input_text], width=2)
submit = Submit(title="Submit",
data={
"callback_keyword": "echo_callback"})
card = AdaptiveCard(
body=[ColumnSet(columns=[Column(items=[text1, text2], width=2)]),
ColumnSet(columns=[input_column]),
], actions=[submit])
return response_from_adaptive_card(card)
class EchoCallback(Command):
def __init__(self):
super().__init__(
card_callback_keyword="echo_callback",
delete_previous_message=True)
def execute(self, message, attachment_actions, activity):
return quote_info(attachment_actions.inputs.get("message_typed"))
- Now, just interact 1-1 with the bot. Send it a message with the text:
echo
and off you go!
- If you are a Cisco employee, and find this useful, consider sending me a Connected Recognition (cec:
fibrady
) 🙂 - Also, join the discussion space here.
- Alternatively, open an issue or PR with a question on usage.
- First release on PyPI.
- Better retry on websocket connection failure
- Added support for approved domains
- Other cleanup
- Retry websocket connection on socket.gaierror. (#1)
- Send ack on websocket message received. (#2)
- Minor cleanup.
- Log bot email on startup.
- Fetch incoming message ID as base64.
- Switch format entirely to use cards.
- Import fix
- Typo fix
- Fix no module found error
- Pin websockets version
- Couple of bug fixes and support python 3.8 fully
- Fix for #11 server rejected WebSocket connection: HTTP 404
- Pass activity down to execute function so attibutes such as email can be fetched from card actions.
- Update your existing
execute
functions to include the extraactivity
parameter.
def execute(self, message, attachment_actions, activity):
log.info(
f"activity={activity} ")
email = activity["actor"]['emailAddress']
return quote_info(f"person email is '{email}'")
- Fixes for #14 & #16
- Add new workflow for Github releases.
- Add
pre_execute
function to Command. (optional function to overide). Reply before running the execute function. Useful to indicate the bot is handling it if it is a long running task. - See echo.py for example usage.
- Check for duplicate card callback keywords and raise exception if one exists.
- add support for
pre_card_load_reply
overide. Reply before sending the initial card. Useful if it takes a long time for the card to load.
- add support for deleting previous card in a chain.
- Support for chained cards
- Add support for approved rooms.
- Add support for using pyadaptivecards
- Remove pyadaptivecards as it is actually built into webexteamssdk
- Add options for bot name, help message etc.
- Bug fix Thanks @muhammad-rafi
- Fix for #13 - Update websockets lib to latest.
- Allow for commands to only respond if you are in the approved space.
- Add
chained_commands
as a parameter of Command. This allows multiple related cards to be added at once. - Updated Echo to use Adaptive Card objects (instead of JSON/Dict blob)
- Added docs for some function params.
- Fix old school dict cards
- Update webexteamssdk to latest release.
- Auto re-connect on websockets.exceptions.ConnectionClosedOK
- Bot will reply in response to the original message via the thread ID. This is not always possible in the case of a card action response due to some server side issue.
- Always ensure there is a thread ID in the Activity before accessing it
- ❌ Bad release. Please do not use this one as there is a startup issue with it.
- Add max backoff time (#55)
- Attached files. Help, threading and log level overrides. (#54)
- add stop() call to gracefully exit the bot (#42)
- feat(20231212): add help image size parameter (#46)
- update websockets to 11.0.3 (#43)
- Fix for help_command syntax issue
- Add Proxy Support. (#56)
- Introduce exact_command_keyword_match feature (#59)