- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎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.
It Seems, we have to build a custom Flow Action which supports Adaptive card format.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-17-2024 05:18 AM
I've had this same problem and raised a ticket with ServiceNow asking what the replacement was. There've responded with a KB article (KB1650148) saying that we should start using the MS Teams Graph Spoke. The set up for this is different but it provides the same (and more) functionality.
Now if someone can work out how we post messages as not the user that approves the connection, that would be great!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-17-2024 06:00 AM - edited ‎07-17-2024 01:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2024 06:33 AM
@spike did you figure out how to post messages as a different user using the graph spoke?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2024 06:42 AM
I did. The Graph Spoke is somehow connected to the original Spoke. So you need both. After configuring the graph spoke you'll verify your token is pulled successfully. Then you'll use the action from the new spoke to create the post. It is different in that it uses a direct connection to the Teams channel via Team and Channel IDs, and not the webhook. So whatever user you used to authenticate the token will need access to the Team in order to post to it. This has been our biggest issue, but we are making it work for now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2024 08:45 AM
but you are only able to make it post as yourself in the team? That is what I am trying to change. All the posts show as they are coming from me.
