-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Open
Labels
bugIndicates an unexpected problem or an unintended behavior.Indicates an unexpected problem or an unintended behavior.needs-triageThe issue has just been created and it has not been reviewed by the team.The issue has just been created and it has not been reviewed by the team.
Description
ABS when configured to "Add and configure interactive messages" as stated in the documentation Connect a bot to Slack doesn't forward interactive messages to the bot service.
Sample information
- Sample type: samples
- Sample language: all languages
- Sample name: n/a
Describe the bug
As per the documentation, Slack interactions initiate an HTTP POST request when users interact with interactive components. The request URL is pointed to https://slack.botframework.com/api/Actions which should forward those requests to the URL mentioned in 'Messaging Endpoint' for the bot. This request forwarding doesn't happen.
To Reproduce
Steps to reproduce the behavior:
- Create a new 'Azure Bot' in Bot Services in Azure portal
- Add 'Messenging Endpoint' bot configuration.
- Add 'Slack' as in the channels - a new Slack app need to be created and credentials properly filled in
- In the Slack app 'Interactivity & Shortcuts' menu, add 'https://slack.botframework.com/api/Actions' in the Request URL as mentioned in the documentation.
- Render a simple interactive Slack block card - see attached image for a sample card.
- Click on the interactive button.
Expected behavior
When a user clicks on the button in the interactive block card, Slack initiates a HTTP POST request which should route to the 'Messenting Endpoint' as setup bot configuration. Apparently, no such message is sent from the Bot Services.
Screenshots
Additional context
Metadata
Metadata
Assignees
Labels
bugIndicates an unexpected problem or an unintended behavior.Indicates an unexpected problem or an unintended behavior.needs-triageThe issue has just been created and it has not been reviewed by the team.The issue has just been created and it has not been reviewed by the team.