This document provides an agenda and details for a Selangor, Malaysia Meetup discussing the integration of Google Hangouts with Mulesoft. It includes an introduction to the speakers, an overview of the community resources, and a presentation by Vishal Changlani on designing and implementing a Google Hangouts integration for platform and application alerts in Mulesoft. The presentation covers the webhook architecture, message formats, response structure, handling different types of alerts, and designing the Hangouts API to prevent error mail flooding and support operations. It concludes with a question and answer section and trivia quiz.

1. 26 June, 2021 1.30 PM
MYT
Selangor, Malaysia Meetup

2. Agenda
•Introduction Of Organizers and Speakers
•Community Details!
•Integration with Google hangout
•Q & A
•Trivia Quiz
2

3. Selangor, Malaysia Meetup Leader
3

4. Speaker for the day!
4

5. Community Details
•Register for Meetups : https://meetups.mulesoft.com
•Register for Official Training platform : https://training.mulesoft.com
•MuleSoft forum : https://help.mulesoft.com
•For all blogs : https://blogs.mulesoft.com/
•Anypoint platform : https://anypoint.mulesoft.com
5

6. Vishal Changlani
Sr.Integration Developer at Billennium, India
Design and Implementation of Google Hangouts
Integration With Mulesoft

7. 2
Agenda
• Google Hangouts Integration for :-
- Platform Alerts
- Application Alerts

8. 2
Why do we need this?
● Error Monitoring using Email Notifications is old way now
● It has its own drawbacks like -
- Dedicated person to monitor
- Chance of missing out mail
- Email flooding
- All notifications comes at single mailbox, difficult to segregate
priority errors

9. 9
Possible Solutions
● Need to embrace modern Instant Messaging tools for real-
time action :-
- Google Hangouts
- Microsoft Teams (connector available)
- Slack (connector available) and many more
● Today, we will cover Google Hangouts for discussion.
However, design of API will remain same for other tools as
well, msg format and target will change

10. 10
Google Hangouts (Google chat)
● Incoming webhooks let you send asynchronous messages
into Google Chat from applications that aren't bots
themselves
Features of Incoming Webhook API-
● Quick and easy to integrate with existing workflows, without
writing bot applications
● We can configure multiple incoming webhooks on any chat
room
Note : Google Chat API is only available to Google workspace
(Formerly G suite) customers only

11. 11
Webhook Architecture

12. 12
Webhook Config
https://chat.googleapis.com/v1/spaces/{ID}/messages?key={key}&token={token}

13. Message Formats
● Simple Text Message
Eg
13
{
"text": "Your pizza delivery is here!"
}
{
"text": "<https://example.com/foo|my link text>"
}
{
"text": "Hey <users/123456789012345678901>!
Thank you for using _Pizza bot!_"
}

14. Formatting in Text Messages
14

15. Message Formats
● Card Formatting Messages
15
{
"cards": [
{
"sections": [
{
"widgets": [
{
"image": { "imageUrl": "https://www.google.com/maps/d/thumbnail
l?mid=1HgTTJp9U9_MEzPUOcwFerFwKeiI&hl=en" }
},
{
"buttons": [
{
"textButton": {
"text": "OPEN IN GOOGLE MAPS",
"onClick": {
"openLink": {
"url": "https://goo.gl/maps/T5p2dPAACkGsATwX9"
}
}
}
}
]
}
]
}
]
}
]
}

16. Message Formats
16
{
"cards": [
{
"sections": [
{
"widgets": [
{
"image": {
"imageUrl": "https://picsum.photos/seed/picsum/200/300"
,
"onClick": {
"openLink": {
"url": "https://example.com/"
}
}
}
}
]
}
]
}
]
}

17. Message Formats
17
{
"cards": [
{
"header": {
"title": "The Bons Cafe",
"subtitle": "pizzabot@example.com",
"imageUrl": "https://goo.gl/aeDtrS"
},
"sections": [
{
"widgets": [
{
"keyValue": {
"topLabel": "Order No.",
"content": "12345"
}
},
{
"keyValue": {
"topLabel": "Status",
"content": "In Delivery"
}
}
]
},
{
"header": "Location",
"widgets": [
{
"image": {
"imageUrl": "https://www.google.com/maps/d/thumbnail?mid=1HgTTJp9U9_MEzPUOcwFerFwKeiI&hl=en"
}
}
]
},
{
"widgets": [
{
"buttons": [
{
"textButton": {
"text": "OPEN ORDER",
"onClick": {
"openLink": {
"url": "https://example.com/orders/12345"
}
}
}
}
]
}
]
}
]
}

18. Card Text Formatting
18

19. Response Structure
19
{
"name": "spaces/{spaceID}/messages/{messageID},
"sender": {
"name": "users/{userID}",
"displayName": "test",
"avatarUrl": "",
"email": "",
"domainId": "",
"type": "BOT",
"isAnonymous": false
},
"text": "Hi",
"cards": [],
"cardsV2": [],
"previewText": "",
"annotations": [],
"thread": {
"name": "spaces/{spaceID}/threads/{threadID}” },
"space": {
"name": "spaces/{spaceUD}",
"type": "ROOM",
"singleUserBotDm": false,
"threaded": false,
"displayName": "Mulesoft Application Alerts"
},
"fallbackText": "",
"argumentText": "Hi",
"attachment": [],
"createTime": "2021-06-25T15:49:51.108479Z"
}

20. 20
Types of Alerts
● Platform Alerts
- Alerts w.r.t MuleSoft platform like vcoreUsage, Anypoint MQ
messages, API status, Runtime Manager Notification etc can be
covered directly
- Alerts like CPU usage, Memory usage, or Worker unresponsive
or Policy violation can be covered by reading mailbox

21. 21
Types of Alerts
● Application Alerts
- To use hangouts-api, an application just need to make
HTTP call with error object
- The task of extracting important fields and notifying chat
rooms is taken care by our hangouts common api

22. 22
Hangouts API design

23. Error Mail Flooding Prevention
● Consider an API which is receiving 100 req/min and sue to some
glitch in target endpoint every request start failing and same alert
email start flowing to OPS mailbox
● This will result problem for OPS to identify unique error alerts due
to many duplication
● Using Object store in design, we tried to minimise this and support
the operations team
● We store APP_NAME:ErrorType as key in OS and if same
combination comes again within specified TTL it will be dropped
23

24. 24
Mule Flows

25. 25
Mule Flows

26. 26
Multi Chat Rooms
● Scenarios where Production API count is too large
● Managing alerts via single chat room can be annoying
● Notifications can be distributed across multiple chat rooms
based on -RoundRobin algorithm
- Defined Custom logic
- Chat room based on API type sapi,eapi,papi
- Chat room based on API priority etc

28. Questions ?

29. Trivia Quiz !

30. Enter Your Full Valid Name (no nick Names are allowed)
Only those who have registered and joined the session will be
allowed!
1. Go to Browser
Enter :
quizizz.com/join
2. Wait for code
3. Enter your name

31. Thank you