This method offers a few advantages over webhooks. Through this persistent connection, we can send & receive messages very quickly and easily. With a websocket, we're instead opening a direct, persistent TCP connection to the Webex APIs. On the other hand, we could use websockets to accomplish the same function. ![]() We could also use a tunneling method (like ngrok) to avoid having to directly open ports to our webserver. For example, we could use something like FastAPI to quickly build our web listener & handle incoming POST requests. Both of these could be overcome with easy workarounds, if needed. Now, the potential downside of using webhooks is that we need to 1) manage a web server and 2) expose the bot publicly to the internet. This way, every time Webex receives a message from a user that wants to interact with our bot, the Webex cloud knows where to send that chat message. When we run our bot, one of our first actions will be sending a request to the Webex APIs with our bot URL. Using this method, we need to run out bot code on a publicly reachable URL. Likely webhooks are the method most people are familiar with. Next, I wanted to cover the two primary methods of sending & receiving messages from the Webex APIs: Webhooks and websockets. If you're looking to do this, make sure you give a good description of your bot!Īfter we finish all that, we'll finally get our API key! Once the bot is completed, we have the ability to publish it via the Webex App Hub where anyone could interact with it. This includes a display name, username, image, and some details. Next we'll need to provide some details about our bot. Then we'll be asked what type of app we're creating. Once logged in, we'll go to the upper-right corner of the screen and click on our user icon - and select "My Webex Apps" from the drop down: So head on over to the Webex Developer site & log in (or sign up for a new account). So the first thing we'll worry about is getting signed up for a Webex developer account & generating API keys. Repo here for all the sample code used below Contents With all that being said - I wanted to throw together a quick guide on how to get started building a basic chatbot, in case anyone else is interested but worried that it may be too complicated. Building out some of the more interactive parts of the bot hasn't been quite as difficult as I originally imagined, and some of the newer modules & SDKs have made the process much simpler. Mostly what I've done before is just using Webex or Discord APIs to send alerts or messages to a room.Īs with anything new - I've stumbled my way through a couple of things, but have been enjoying the challenge of trying something different. I didn't previously have a ton of experience building something like this. If Eurl is set to have its list enabled in a Webex group space, then it will appear here on for users to search for and join! Whether the internal setting is used will determine which users will be able to see the space as joinable.I've been spending some of my time lately working on a new project that involves an interactive chatbot - where you can send commands to the bot & ask for it to take certain actions or return information.send the word 'test' and Eurl will return a list of all spaces with the word 'test' in the space title. You can also send a direct message to in Webex to search public and internal spaces, e.g. ![]() Support - Join the support space for this bot Source - Get the link to the source code for this bot Url new - Create a new url to join the space Logo - See or set custom logo (transparent png, 50px width recommended)ĭescription - See or set description ![]() Internal - Only users from specific domains can join the space List off - Remove the space from public listing at List - Anyone can see the space listed at Url - Get details on how someone can join the space Then, the bot in the group space in Webex with one of the following commands: Eurl is used to create spaces that users can search for and join.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |