In this Article

...

Design an Event Listener for Slack

...

Workspace Using Slack Snap Pack

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  To fasten the decision-making process and deliver results, they you can configure an Event Listener in their the Slack workspace to cut through the clutter and get notified on items that need their immediate attention. This use case demonstrates how we you can use the Slack Snap Pack to route important events that are important to the manager into a custom channel created for this purpose.

Problem

In a real business case scenario, checking for going through all messages posted on the Slack Channel is time-consuming and owing to the the hectic schedule of managers leaves them with little time to go through all the messages posted on Slack. However they you cannot miss out on important updates that require their attention. 

Solution

Using Slack integration for your organization allows you to set up notifications to send messages to a Slack private channel or a specific user on Slack. We You can efficiently automate the process of listening to Slack events, configuring the events, and receiving alerts on your Slack Channel upon the trigger of events. This Pipeline pipeline demonstrates how we you can automate the process of receiving alerts on the private channel when these events are triggeredsame.

Parent Pipeline - Slack Listener	Child Pipeline - Process Event

Download the Slack Listener and Process Events Pipelines. 

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.

Building this Pipeline involves the following key Key steps:

1. Create a Private Channel in Sack.
2. Subscribe to the Slack events.
   • Create a Parent Pipeline.
3. Create a Child Pipeline.

Create a Private Channel in Slack

Create a private (custom) channel named #my_alerts, and add the necessary stakeholders who should must receive alerts for the given events.

Subscribe to Slack Events

We want to configure the following Configure two events and to receive alerts on the private channel when these the following events occur:

• Event 1: When a new member joins the Slack channel.
• Event 2: When a SWAT ticket (customer-raised ticket) is posted in the channel.

To subscribe events in Slack:

1. Navigate to https://api.slack.com/apps—Slack Apps page.to the Slack Apps page.
   
   
2. Click Create New App.
   
   Image Added
   
   
3. Select From scratch.
   
   
4. Specify the App Name and choose a workspace in which to develop your app.
   Image Added
   
   
5. Click Event Subscriptions in the left navigation pane.
   Image Added
   
   
6. Enable the toggle for Enable Events.
   
   
7. Subscribe to the events you want to listen.
   • Bot events: Whenever a bot performs the operation of adding a user to channel, we want to receive an alert.
   • User events: Whenever a user posts a message to public channel, private channel, individual user or multiple users or group of users, we want to receive an alert.
     
     
8. Provide the URL of the triggered task of the Parent Pipeline in the Request URL field.
   To provide the Request URL in Slack app, you need to configure a Pipeline with a Mapper Snap and create a triggered task.
   
   

Create a Parent Pipeline 

First, we configure the Mapper Snap with an expression to determine if the object is a challenge or an event.

...

...

Triggered Task

Create a a triggered task for the Parent Pipelinepipeline. From the Triggered task dialog window, we copy the Cloud URL and HTTP Header (token) and paste it in Request URL field in the Slack app for verification.

...

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.

Create a Child Pipeline to Process Events

Image Modified

We configure the child Pipeline to perform the following two operations:

...

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

...