![]() You also grant to Cisco a worldwide, perpetual, irrevocable, royalty-free and fully-paid, transferable (including rights to sublicense) right to exercise all copyright, publicity, and moral rights with respect to any original content you provide. By posting you agree to be solely responsible for the content of all information you contribute, link to, or otherwise upload to the Website and release Cisco from any liability related to your use of the Website. ![]() No information you consider confidential should be posted to this site. ![]() The content is provided for informational purposes only and is not meant to be an endorsement or representation by Cisco or any other party. Opinions expressed here and in any corresponding comments are the personal opinions of the original authors, not of Cisco. Some of the individuals posting to this site, including the moderators, work for Cisco Systems. You can follow a dedicated learning track to boost Webex API programming skills hereĬontacts | Feedback | Help | Site Map | Terms & Conditions | Privacy Statement | Cookie Policy | Tradmarks You can find more examples of Webex integrations here Maybe instead of retrieving a joke, you could retrieve network health stats and post them to Webex Teams instead? Or perhaps it could retrieve information about how busy the offices are by integrating with DNA Spaces (though by this point, you may need to leverage a more advanced programming tool)? The possibilities really are endless! Once you’re comfortable with how this flow works, there are many ways you can extend its capabilities. The concepts in this lab guide are kept super simple to break down the barriers to entry with automation and programmability. POST that joke to Webex Teams from the Bot account.Extract the most important information from the API response: the joke itself.Make an API call to get a joke from the icanhazdadjoke database ( ).When the bot receives a message and Webex Teams POSTs to the API, a flow is triggered.You create a webhook that makes Webex Teams POST to that API when the bot receives a message.You create an API on Node-RED for Webex Teams to POST to.Using other APIs to retrieve external information and push that info to Webex Teams.Using Webex Teams APIs to post messages.The lab guide briefly explains the following concepts: ![]() The bot created in the guide retrieves external information by getting a joke from an online joke database, but this can easily be substituted with any external source that exposes the appropriate APIs. There are explanations from the very beginning, such as how to set up an account on IBM Cloud and how to create a Node-RED instance once you’re signed in. Since this guide is designed for absolute beginners, the complexity is kept to a minimum. And believe it or not, you could run through the entire lab in about an hour or so. Here you can find a lab guide that walks you through step-by-step the process of creating a bot that retrieves information from an external source, extracts the information of interest and then posts it in Webex Teams. Through integrating with a flow-based tool such as Node-RED, you can do this with minimal programming, making it ideal for first timers aiming to gain more experience in leveraging Bots. Have you found yourself performing basic IT tasks, such as monitoring a dashboard, repeatedly? Are you one of the many engineers who want to automate these activities, but are slightly intimidated by the code you’ll need to learn in order to accomplish this?īots can help with alerting you when a certain event takes place, such as a high-priority incident on your network, by leveraging APIs, but many engineers feel they don’t yet have the programming skills needed to create a bot.Īt Cisco, there’s a simplified way of creating a bot that listens out for alerts and responds accordingly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |