If you're like me - you love HipChat (and boy, do I LOVE their Office Space Ads!)
HipChat is my go to tool to talk and sync up with my team.
My colleague Nitin Parashar , who has to kick start daily scrums on Hipchat at 8am sharp, came up with this cool idea to get a time-based schedule in CloudBees Flow to do it for him instead - since at CloudBees, we’re all about automation.
The way it works is an CloudBees Flow schedule kicks off at 8am every weekday, which interacts with Hipchat’s REST API to post a message on Nitin’s behalf. Setting it up is a snap!
Integrating HipChat and CloudBees Flow:
To post data to Hipchat, you need an auth token, which can be easily generated . In this example, we've hard-coded the token, but you can use CloudBees Flow Credentials to secure that information.
You can obtain the room ID by logging into the HipChat web app.
The green color simply serves to differentiate the message from the rest:
Go ahead- give it a try!
This is undoubtedly a simple example, but you can easily build on that to include HipChat as part of your automation flow. We have customers who use HipChat as their terminal to view/report/alert on certain events in their process. For example: a failed build or automatic notification of machines being ready, etc.
Hope you like incorporating HipChat to your processes with CloudBees Flow as much as we did. Got any questions? hit me up in the Comments.
And in conclusion, let me leave you with this important question to ponder on: how can we do better, as a team?