Skip to main content

Thursday US Admin Office Hours (CS Platform): Dec 12, 2024 - 11am PT / 12pm MT / 1pm CT / 2pm ET - Pre-session Thread


sdrostgainsightcom
Forum|alt.badge.img+3

Hello everyone!  Apologies for the late post today!

This thread is for today’s Thursday Admin Office Hours session, Thursday, December 12, 2024 at 11am PT / 12pm MT / 1pm CT / 2pm ET.


Please submit your questions below as replies to this post in advance if you can, and we'll address them during the session (or if there’s a quick answer available, we’ll post as replies to the questions).

There is no need to register for these sessions - you can join at any time. Once the session is underway, I will go in order of questions posted below first, then field questions from anybody else who has joined as well. Look forward to talking with you!

Conference Details (Zoom):

Thursday, December 12, 2024 at  11am PT / 12pm MT / 1pm CT / 2pm ET

 

Join Zoom Meeting:

https://gainsight.zoom.us/j/95564886548?pwd=SGZyVmM2NGpYSW02RU5XY2x5TjJhUT09

 

Meeting ID: 955 6488 6548

Passcode: 296864

 

For dial-in info by your location, find your local number: 

https://gainsight.zoom.us/u/aeD4b4SdoB

Hi Scott,

 

I am using Event Framework as the source in several JO programs. While testing a criteria addition, I noticed that a different program than expected is triggering so I’m hoping to better understand if there is a priority sequence that occurs behind the scenes or for the criteria itself.


  • Contributor ⭐️⭐️⭐️
  • December 12, 2024

Hi Scott!

 

UPDATE: And I didn’t realize the session was at 12noon MT, and I missed it. Sorry about that!

 

It looks like using the new JO to send a slack notification will only work for public channels. Unfortunately, we use private channels mostly and have a private channel for NPS detractors. 

I started creating the Custom Connector for Slack and trying to follow the Slack api reference page. It seems that when I test on the slack api page, it works. However, when I test my External Action in GS, I get this error:

Status Code : 200

Response :

{  "ok": false,  "error": "not_authed",  "warning": "missing_charset",  "response_metadata": {    "warnings": [      "missing_charset"    ]  }}

From what I am reading that is due to the token? 

We were using Rattle which worked great, but we will be transitioning from Rattle to Slack Workflows. I have synced NPS data over to SF and built a workflow, but that is not working either, which I will need to troubleshoot with my team. But ultimately I feel I need to figure out the API as we will have other data from GS that we will need to send notifications for. 


sdrostgainsightcom
Forum|alt.badge.img+3

Hello ​@Heather C -- sorry for the delay in response -- if you are getting a similar error from a workflow you built in SFDC to push to Slack, you will probably need help from your slack admin.

In this case, I’m pretty sure it’s a permissions error (after you get a “not_authed” error, everything else errors out as well) -- you have to make sure the user that’s the OAuth user signing into Slack has permissions for using the API, accessing private channels, etc.

Just a guess at the moment but that’s where I’d start.

Best,

Scott


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings