2. Scenarios of Using MailTrigger

2.1. Receive Service Notifications on Various Messaging Platforms

Your company uses Jenkins to assist with deployments. When a deployment or build fails, Jenkins by default can only send emails. However, most developers do not frequently check emails, causing Jenkins build failure messages not to be promptly delivered to developers. The good news is that the MailTrigger system solves this problem. Although Jenkins can only send build result messages via email, if you have set up routes for LINE and WhatsApp in MailTrigger, you can receive build result messages on LINE and WhatsApp.

2.2. Expanding Existing Systems to Support Multiple Messaging Platforms

Jack is a software developer at Company A. The platform he is developing sends weekly emails to subscribed users, but currently, it only sends emails. His supervisor hopes to support sending messages to specific groups on Discord or WhatsApp in addition to email. To meet this requirement, Jack would need to separately implement message sending for Email, Discord, and WhatsApp, which is quite time-consuming. Jack decides to use the MailTrigger system to solve this need. He can directly add routes and rules for LINE and WhatsApp on the MailTrigger system for his domain, and then use the normal email sending function in his developed software to achieve simultaneous message sending to Discord and WhatsApp.

2.3. Forwarding Email Content Through Various Messaging Platforms

You can also use other mailbox tools (such as Gmail) to forward emails to the mailbox you set up in MailTrigger, and the email will automatically apply the routes you set for that mailbox to send messages. For example, Bob wants to forward emails about “CNN News” he receives in his Gmail to WhatsApp so that he can see these news articles more easily. He can set up a forwarding route in Gmail (emails about CNN News will be forwarded to bob@bobdomain.com), and Bob can receive these CNN News articles on his WhatsApp!