This is not a use case that makes sense on its own. But it belongs, in my view, to the portfolio of useful integrations that are quite generic and can be applied in many places. Slack is a widely used collaboration tool that is making email obsolete in many organizations.
Too unspecific? Okay, let me illustrate with an example. You already widely use Slack in your company and want to receive an active notification when a new user has registered to your service. That means you can create a new channel just for that purpose and all Slack users who are interested can join the channel.
If you already have an onboarding process running you can simply add a new service task with the Slack worker and that's it ;)
Since we want to integrate with Slack you need a Slack Workspace. Navigate to your Slack Apps and create a new Slack app or use an existing one.
Enable Incoming Webhooks and add a new webhook to a channel.
The next step is to have a worker that sends messages to this Slack channel via the webhook that has been set up.
The worker uses the official Slack Node Client which makes integration a breeze. The parameters set are the
webhookId and the message. This allows the worker to be used in different places with different webhooks. The message could alternatively come from the process context, but that depends on how you want to use the service task.
The process is pretty unspectacular. It gets exciting when you integrate this service task into a larger context.
Happy Slacking! ;)
I'm quite curious if and how you guys use Slack for active notifications from outside :)