Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

On running the Pipeline, the relevant SWAT message is sent to #my_alerts channel as follows:
Image RemovedImage Added

If the event is a new member joining the channel we take this approach. We take a copy of the output from the Router Snap to extract user and channel information when a member joins a channel, and  configure the following Snaps:

...

On running the Pipeline, the relevant new user alert is sent to #my_alerts channel as follows:
Image RemovedImage Added

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.

...