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.

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": n      "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. 

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