Determine the type of event and route the flow appropriately.Įvent 2: When a user posts a SWAT message in the channel.We configure the child Pipeline to perform the following two operations:
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.Ĭreate a Child Pipeline to Process Events 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. We configure the Router Snap with expressions that evaluate whether the input view contains a challenge or an event and routes the outputs appropriately. Now we continue with the Parent Pipeline configuration to listen to the Slack events and process the events as per the requirement. The Redirect URL should correspond to the same URL used for event subscription for the Slack app to function with the Slack Snap Pack. To provide the Request URL in Slack app, you need to configure a Pipeline with a Mapper Snap and create a triggered task.įirst, we configure the Mapper Snap with an expression to determine if the object is a challenge or an event. Provide the URL of the triggered task of the Parent Pipeline in the Request URL field.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.Bot events: Whenever a bot performs the operation of adding a user to channel, we want to receive an alert.Subscribe to the events you want to listen.Click Event Subscriptions in the left navigation pane.Event 2: When a SWAT ticket is posted in the channel.Event 1: When a new member joins the Slack channel.We want to configure the following two events and receive alerts on the private channel when these events occur: Add read channels, read messages, and read users.īuilding this Pipeline involves the following key steps:Ĭreate a private (custom) channel named #my_alerts, and add the necessary stakeholders who should receive alerts for the given events.In this Use Case we set the Bot and User Token scopes to perform the following actions: Create an app in your Slack Workspace that listens to the Slack instance.We 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 demonstrates how we can automate the process of receiving alerts on the private channel when these events are triggered.ĭownload the Slack Listener and Process Events Pipelines.
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. However they cannot miss on important updates that require their attention. In a real business case scenario, checking for all messages 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. This use case demonstrates how we can use the Slack Snap Packto route events that are important to the manager into a custom channel created for this purpose.
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. In any enterprise ecosystem, receiving notifications is critical to carry out your daily tasks. Use Case: Using Slack Snap Pack To Design an Event Listener for Slack Workspace