Native Slack notification step in Journeys

Business problem

Currently, workflows that notify external teams via Slack are easily managed through Rules. However, replicating this in Journeys is difficult as it requires a custom HTTP step, creating a barrier for teams—like developers—who only log into Trengo when alerted via Slack.

Wished result

A native Slack notification step within Journeys, allowing users to easily trigger a notification to a specific Slack channel when a conversation enters a particular branch, similar to the existing "Forward to email" functionality.