I would love to see a new feature added that allows you to create an automation when a status changes that posts a customized update that can tag the person/people in the “people column” and a specific individual(s) that isn’t in the “people column.”
This would be super helpful! As far as I understood, the feature should allow us to use @mention when posting the update from automation recipe?
I see that there is no way to use @mention inside of automation recipe, but only to write someone’s name as the text.
So, instead of creating two automations:
- Notify someone &
- Post the update
It would be simpler and easier to create only one automation that is posting the update and in the update to mention someone. This way that someone will receive the notification about the update, and also can open a discussion about it with other people in the team. Another benefit of this is improved “track of record” for the particular item
I saw some cool recipe in automation center but is not the way to achieve the result described above:
I agree it would be very helpful to @mention someone in an automated update. The benefit of doing it this way vs just a notification, is it is transparent to anyone involved on that item what is going on, and the record stays attached to that item, vs a notification which is not attached to the item. My workaround was to add both a notification AND an update to the automation.
Hi Lita, for the notification in your workaround, it’s only sending a “bell” notification right?
we need this, it has been 4 years since the first request!
Because I wanted both to notify a teammate AND have something transparent posted about that communication, I had to build 2 steps into the automation:
When status is “Ready” [create an update with this text] and [notify Account Manager].
My update then reads like this:
The quote requests have been submitted via portals. Direct Quote Requests still need to be sent by the Account Manager. ~
(This is an automated update)
If the update would allow for @mentions, then I wouldn’t need to do this in two separate steps.