Enabling Integration via Webex Teams – All Now Together
Enabling Integration through Webex Cisco and Teams DNA, SD-Wan, Intersight, Thousand Eye through Cloud API Gateway
I actually was really excited to truly have a unique opportunity to come up with a group of my fellow engineers to focus on a Collaboration hacking contest within Cisco. For each day or two in San Jose this annual occasion is usually in-person, rendering it out of grab my nomadic desert comrades situated in Arizona. Year this, however, remote may be the new normal. This original situation made it easy for my ragtag band of misfits to take part in events irrespective of our geography. Therefore we embarked on a objective make it possible for webhook integration for Webex groups, so that our items can deliver notifications into Teams, because they can into email simply.
A cloud native however cloud agnostic solution
To carry out this we made a decision to make certain this wasn’t only in a position to support diverse items, but additionally, diverse clouds. A cloud indigenous, yet cloud agnostic solution based on serverless infrastructure supporting regular HTTPS and webhooks Write-up messages. We decided on Search engines Cloud Amazon and system Web Services for the multi cloud endeavor.
The original idea was for another use case – actually; I’ve esp8266 modules incorporated with Groups for the utilization case to be notified when my garage area door is opened/shut, my bearded dragon’s cage is hot, etc. As these level in number, easily were to improve my safety bot token or area ID ever, I would need to go re-flash most of my IoT Sensors to complement. So, it generates an operational issue for leveraging Groups as a IoT gadget receiver or alternative party integrator.
Enable cloud being an API gateway
The essential idea was make it possible for cloud being an API gateway to simply accept requests, do advanced security checks, and decouple the Webex Teams security and context information from what’s flashed onto the sensors to raised manage the lifecycle. But extending this to webbooks has been an all natural evolution that appeared to have the most instant impact to clients. When Demo’ing a few of our cloud technology (Intersight, Meraki), customers noticed that notifications can head to webhook or e-mail, and inquired about their Webex Groups integration naturally.
By enabling the webhook capacity, we immediately added assistance for several of our product models that assistance webhooks to integrate with Webex Groups. And achieve this without requiring any apparent change on either the merchandise, or Webex Groups. We did want native “handlers” in the program code to handle distinctions in webhook formatting between various products. For our task we created handlers for Cisco DNA Meraki and Center. We had started focus on Thousand Eye but didn’t possess the lab instance in a position to send webhooks at the proper period we finished the task. The quantity of effort to generate and change a handler is really as simple as 20 minutes worth of hard work making certain the JSON areas that you value, are included in what’s sent to Teams.
The code can be acquired on Github
Of note, as the code must have been very constant between solutions, there exists a difference inside how Search engines integrates their API making use of their cloud functions in comparison to AWS. The API gateway on GCP has already been out for some time, but at this time integration of the API gateway on Search engines for cloud functions is usually in Beta and will require a bit even more lift to create. I expect this can normalize since it is taken to market. I furthermore desire to caveat that by noting I had been seeking an operating product, nearer integration with GCP groups probably would have contributed to how I maintained some mistake handling in Cloud Features to create it integrate with API GW.
https://github.com/will0129/webexTeamsAWSLambda
https://github.com/will0129/webexTeamsGCPFunction