Forum Discussion
Solved
Error while running Teams workflow for sending message to a channel by triggering webhook
Hi,
I was using the incoming webhook connectors for sending messages to channels via webhooks. Recently heard that these connectors are no longer supported and need to use workflows. I had setup a workflow for the same and tried to trigger it from the UI itself. But every time it is returning an error as shown below. I tried to hit the workflow URL externally and it returned success (202) response, but no messages were delivered to my channel.
Error shown while running the workflow from UI.
Flow '3d8843ba-0636-0d1d-bb10-7234s4r4fea5' cannot be installed.
Please help me to find a solution to replace my old incoming webhook connectors.
Thanks.
@basharh190 , StoneE1085, sushantp1105 ,BrianA1775, MattJ1810, nidheeshbabu96, RCFTech
We tried to test this by creating a workflow and then by POSTing a payload to the webhook URL. The workflow sent the message successfully in desired team's channel.
Workflow:
Step:1Step:2
Step:3
Running cURL command:
Result:
This seems to still be a problem.
- We are also facing the same issue at our org, we cant use the old webhook because its deprecated and the new teams workflow webhooks are non functional.
Prasad_Das-MSFTMicrosoft
basharh190 , StoneE1085, sushantp1105 ,BrianA1775, MattJ1810, nidheeshbabu96, RCFTech
We got update from engineering team stating that, it should not be triggered via the UI.
The way to test is by POSTing a payload to the webhook URL. The error message is badly misleading.
Prasad_Das-MSFTI have been invoking workflows via HTTP requests, and while the requests return a success output (202 response), the message is not being delivered to the channel. Upon checking the run history of the workflow in Teams, I noticed that the runs are showing a failed status. Please find the screenshot attached for reference.
I would greatly appreciate your assistance in resolving this issue at the earliest, as it is having a significant impact on our operations. Your prompt attention to this matter would be highly valued.
- Just commenting here to track and to report that we're getting the same error. Also want to point out that it's insane that a working feature was moved and it isn't even working. Why move webhooks here in the first place!?
nidheeshbabu96 Prasad_Das-MSFT multiple people in my office getting the same errors and makes the feature useless. I lost days debugging it thinking I was doing something wrong to find this thread and see that it's a legit issue. Hopefully this is resolved soon. Thanks
- Prasad_Das-MSFT
nidheeshbabu96 - Thanks for raising your issue. We tried to repro this and are getting same error as you described above. We have reached out to engineering team internally and informed them about the issue. We will notify you in this thread once we get any update from them.
- Any update on this?
- Prasad_Das-MSFT
nidheeshbabu96 - Apologies. Currently there is no update from engineering team. We are actively following up with engineering team about this issue. We will update this thread once we hear from them. Thanks!
Prasad_Das-MSFT Thanks for the update.
