In this Article
...
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. Managers usually run on a time crunch; to fasten the decision-making process and deliver results, they can configure an Event Listener in their Slack workspace to cut through the clutter and get notified on items that need their immediate attention. This use case demonstrates how we can use the Slack Snap Pack to route events that are important to the manager into a custom channel created for this purpose.
...
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.
...
| Note |
|---|
You must append the bearer token to the URL. |
Once the Slack app receives the challenge from the Parent Pipeline, the URL is verified. After the URL is verified which usually takes three seconds, the request triggers the Parent Pipeline and it receives the challenge as response.
| Note |
|---|
The Request Redirect URL should correspond to the same URL used for event subscription for the Slack app to function with the Slack Snap Pack. |
Now we continue with the Parent Pipeline configuration to listen to the Slack events and process the events as per the requirement.
We configure the Router Snap with expressions that evaluate whether the input view contains a challenge or an event and routes the outputs appropriately.
...
Finally, we configure the Join Snap to get a single output from the two output views. This output is the output of the Pipeline Execute Snap in the Parent Pipeline.
Downloads
| Attachments | ||
|---|---|---|
|
...