In this ArticleView file name Use_Case_Process_Event.slp height 250
| Table of Contents | ||||
|---|---|---|---|---|
|
...
In any enterprise ecosystem, receiving notifications is critical to carry out your daily tasks. Emails are no longer the preferred method of receiving notifications, especially when the notifications involve time-critical issues. To fasten the decision-making process and deliver results, you can configure an Event Listener in the Slack workspace to cut through the clutter and get notified on items that need immediate attention. This use case demonstrates how you can use the Slack Snap Pack to route important events into a custom channel created for this purpose.
...
In a real business case scenario, going through all messages posted on the Slack is time-consuming. However, you cannot miss out on important updates that require attention.
...
Understanding the Slack Pipeline
Prerequisites:
- Create an app in your Slack Workspace that listens to the Slack instance.
- Set the required scopes for the app. In this Use Case we set the Bot and User Token scopes to perform the following actions:
- Add read channels, read messages, and read users.
- Add write messages and read channels.
...
| Info | ||||
|---|---|---|---|---|
| ||||
This expression includes three elements: Token, Challenge and Type.
|
...
If the input is a challenge, the Pipeline processes and sends the response. If the input is an event, the Router Snap routes the output to the Pipeline Execute Snap that runs the child Pipeline to process the event in the Process_Event Pipeline.
Next, we use the Join Snap to join both the output views of Pipeline Execute and Mapper Snaps using left outer join to get a unified output.
...