I cannot add an incoming webhook to ms teams channel

Question

Hello,

yesterday when I tried to add an incoming webhook I got the generic error message that "something went wrong".

Now when I hit "add" on the incoming webhook, I just get a blank page.

Following the network traffic, I found out that the request on

/connectors/IncomingWebhook/Manage/New?MailboxAddress=e880cc50-6518-49f2-9abd-549668ec3b86%401b94b413-6d28-42b0-bf1a-7bb10aa22440&client=SkypeSpaces&SSThread=19%3ApJFBJXqrH3tfd-wLD5uuJOE6xrwauZN_0znaj0OeEAg1%40thread.tacv2&HostName=teams.microsoft.com&culture=de-de&ssApiHost=de.ng.msg.teams.microsoft.com&iframe=true&SSTheme=default&isDesktopClient=false&enableConnectorApps=true&providerId=203a1e2c-26cc-47ca-83ae-be98f960b6b2

returns a server error 500.

We need this desperately. Thankful for any help!

Answer 1

We checked this from our side by creating a new incoming webhook and are able to create successfully.

Tested in Microsoft Teams version 24187.501.2981.3768. The client version is 49/24053101421.

FYI, O365 connectors within Teams will be deprecated and notifications from this service will stop. Learn more about the timing and how the Workflows app provides a more flexible and secure experience. If you want to continue receiving these types of messages, you can use a workflow to post messages from a webhook request. Set up workflow

Answer 2

I dont see how this is not covered. I am paying for thr service and I cannot use it. I am running into a server error. Its not related to my connection, its fine. I have tried multiple times, my colleague has tried multiple times. I cannot add an incoming webhook. There is no url, no debugging. I cannot even add it. I need help, urgently.

Answer 3

getting the same error while adding incoming webhook

Answer 4

Same problem. I cannot create new incoming webhooks or display existing ones. When using the filter ‘Configured’ only the wait-indicator appears endlessly. An error message is not displayed

Answer 5

We have the same problem in our company. This is a problem since not every application supports workflows already. Some still depend on incoming webhooks...