If you are implementing buttons & cards, you will need a public URL (e.If you don't need to serve buttons and cards images, you can set the environment variable WEBSOCKET_EVENTS=True and avoid the need for a public URL.

images associated with the cards and buttons feature or the health check URL. A public URL is also needed if your bot will be serving any web pages/files, e.g. Webex Teams also supports traditional HTTP webhooks for messages/events, which requires that your bot be accessible via a publically reachable URL. Most Botkit features can be implemented by using the Webex Teams JS SDK websockets functionality, which establishes a persistent connection to the Webex Teams cloud for outbound and inbound messages/events. Survey.js - Implements a basic survey, posting survey data into a cloud service (i.e. Query the device's 'PeopleCount' function, or execute an ad hoc 'xStatus' CLI command Roomkit.js - Interact with a Cisco room device via xAPI/jsxapi.

Roomid-phantom.js - Helpful utility bot when added to a room, it creates a separate space with the requestor and outputs the roomId of the original room This project implements a Botkit + Webex Teams adapter bot, based on the DevNet botkit-template project, providing some additional interesting samples and examples:Įmoji.js- Converts emoji tags into unicode characters and returns the 'emojified' phraseĮvents.js - Retrieve/display DevNet event details from an HTTP REST API providing JSON data

Webex teams bot