A while back Gainsight released a native Slack connector but only made it available for use in Advanced Programs.
This means that if I want to send a Slack message from Gainsight I either have to use AP (which is extreme overkill when the use case isn’t tied to an email or survey) or I have to create/maintain a custom Slack application, Custom Connector, and JSON coding in External Actions for this purpose, which requires a whole separate set of skills.
Why isn’t the native connector available to Rules Engine? There are innumerable use cases where this would be valuable.
New Idea
CS: Make the native Slack connector available to Rules Engine
+5
+7This would certainly be a benefit to Admin QoL. Please consider this.
+4At my last company, we had a nearly unmanageable amount of external actions & zaps in Zapier to trigger all sorts of Slack notifications. Troubleshooting had 3 points of failure, always. It would be a terrific time saver for at the very least the notifications to a single channel in a single format to be able to be sent directly from Rules, and to have some kind of log within rules to see if the action executed properly or what the point of failure was!
+15Agree. I just started exploring using the Slack connector, and didn’t realize I wouldn’t be able to use it in Rules Engine as well. Seems like a win to be able to use it everywhere
+5From Gainsight PM:
I want to be upfront here: making the native Slack connector available directly within Rules Engine (as a native action type) is not currently on the near-term roadmap.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.