Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Microsoft Teams Spoke will not work with Microsoft Teams Workflows - They will stop working in Oct

Go to solution
Community Alums
Not applicable

‎07-09-2024 01:25 PM

I ran across this yesterday and have tried to create a workflow in Microsoft Power Builder for Teams to create a new Webhook and it's not working.

The message I'm getting in Microsoft Teams:

Action Required: 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



Putting the new webhook in Microsoft Team Spoke I'm getting the following error:
Error: 400. Message: {"error":{"code":"InvalidRequestContent","message":"The input body for trigger 'manual' of type 'Request' must be of type JSON, but was of type 'application/octet-stream'."}}. (Process Automation.0e9862431324030039a039ed9344b05f; line 5)

Does anyone know how to deal with this.  We have a lot of flows that call into teams and this would suck to have it just stop working.

Any help would be appreciated.

  • 6,398 Views
1 ACCEPTED SOLUTION

Go to solution
Keminda
Tera Expert

‎07-10-2024 09:17 PM - edited ‎07-10-2024 10:53 PM

The reason for the above error is the webhook is expecting the request payload to be in JSON format.

Currently its sent in a  different format. to achieve this you have to edit the flow action step Post Message and add Content Type: "application/json"  in headers.

 

But the next issue you will face is MS Teams spoke is using connector cards (MessageCards) format for posting cards, which is in a different format from Adaptive cards in Teams workflows.

https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-referen...

 

It Seems, we have to build a custom Flow Action which supports Adaptive card format.

View solution in original post

0 Helpfuls
16 REPLIES 16

Go to solution
dan167
Tera Guru
In response to Rushali Pradip

‎03-27-2025 04:58 AM

I ended up using the graph spoke. That is what SN recommended in a KB article.

Go to solution
Rushali Pradip
Tera Contributor
In response to Spencer L

‎03-27-2025 08:02 PM

Thanks for posting this it worked!!

0 Helpfuls