Slack Spoke Inbound Configuration Debugging

[DorianK]

Hi,

How does one debug the slack spoke inbound configurations? I followed https://docs.servicenow.com/bundle/tokyo-application-development/page/administer/integrationhub-stor... and I am able to successfully get actionable message to be sent to the slack server, but when the user clicks it - it throws a "This app has responded with a 400". I have tried it for slack commands, slack shortcuts, and actionable messages. I've configured a simple decision response and also tried using the OOTB. I can't seem to figure out what is wrong and it doesn't look like SN is producing any logs.

I see in the documentation that the "slack app name" needs to be put in the signing secret configuration (which I have done and made sure its using the alias that has the connection credentials). I've tried both the app id and the slack app name (changed the url on the slack app interactivepayload, re-deployed, changed the url to be the app id in the interativepayload, re-deployed - all while changing it on the signing secret configuration)

First question: Is the slack app name the app id or just the display name that can be changed? Is there some secret magic that I am missing to get my actionable message response to work?

[Meenakshi]

Hi @DorianK 

Has the issue been resolved? If so, could you please provide the steps you took to address the issue you have mentioned, as we are currently experiencing a similar issue.

[DorianK]

So debugging isn't straightforward BUT there is a flow that runs when you hit the endpoint. It is the "Slack Interactive Commands Service" (or something along those lines - not in front of the instance with it on atm). My guess is there is a hidden endpoint API that has a script include that calls that flow.

The second piece of the "app id / display name" - that just needs to be the same as the url you have in the interactivity url. So whatever you put in that name should equal whatever you put in that signing secret configuration. 

[Meenakshi]

Hello @DorianK,

Thank you for your response!

We've already verified the signing secret, request URL in the interactive page of Slack, and the OOB Scripted REST Resource named (Slack Interactive Payloads) for the resource path in ServiceNow. The Scripted REST Resource successfully triggered when testing with POSTMAN. However, even after these checks, the Slack button continues to throw the same error message, "This app responded with error 400."

Is there any other additional configurations that need to be addressed to resolve this issue?

Thanks in advance.

[DorianK]

Hi @Meenakshi  ,

Did you setup the inbound configuration policy to accept the shortcut or param correctly in the filter that then triggers the subflow you care about? A good way to test that part is just have a simple subflow that posts a response back to SN (or utilize the ones that already exist). Once that is setup, it just becomes configuring the subflow properly (like making sure the correct response action is used for approvals vs posting a message, etc).