Currently Slack nofications can only be sent to a static user or chanel that must be speicifed at the time of creating the automation workflow. It would be more useful if slack messages could be sent to users or channel based on ticket properties. For example, if a Hubspot ticket is closed and send a slack notification to the “creator” of that ticket.
1000% agree! This would be a huge lift for my use-cases as well. Since our sales team has transitioned to entirely remote, we are heavily dependent on notifying reps of new leads assigned via slack. As of now, we are reliant on convuluted processes that incoporate hubspot workflows, webhooks as well as zapier triggers to get this process to function and notify reps directly in slack.
If we were able to simply add a dynamic “company owner” or “contact owner” into the slack notification within hubspot workflows, we could eliminate 5-6 steps in our process and make life much easier!
We’re working on a more configurable slack integration at getharold.net. If this is still a feature you’d be interested in, I’d love to chat.
This is really important for us - being able to specify the required Slack channel for an automated message in a workflow, based on the value of a property of a core, or custom object would be incredibly useful.
This would be great. I want to send notifications to our internal customer slack channels when tickets are updated but it needs to be dynamic (pulling channel ID or name from Company) - no way we can create and maintain one per customer.
I would love this option, maybe we can just add a channel ID to specify which channels to send the notification to. This feature would greatly help in my use case as well.
It would be incredibly valuable if a Slack channel that’s already connected to a record could be notified automatically about any updates to the associated Deal, Ticket, or other object. Right now I have to do this manually for each update, which is time-consuming and easy to forget. Native support for posting to the linked channel would dramatically improve cross-team communication and keep everyone aligned in real time without extra effort.
We have many campaign related channels. A dynamic notification would let us notify the channel when there is campaign activity (assuming the channel would a property of the campaign record) without resorting to a 50+ branch statement in a workflow for each channel.