Issues with migrating from O365 Connectors to Workflows for Teams webhook notifications

Hi all,

I've been trying to migrate our team's mechanism to notify to Teams to use the new Workflows, given that O365 Connectors will be removed in the coming months. So far, I've run into two significant issues that I'm hoping others have been able to resolve:

1. Any "post message or adaptive card" action in Workflows expects that the payload it has received from the previous webhook request step contains a field called "attachments". Our notification code that we have used so far with the Incoming Webhook app does not create that field, we use "text" instead. Is there any way to change the Workflow action to accept a different payload structure, so that we don't have to change our code at all?

2. Any successful invocations of the Workflow will be posted from the account of whomever set up the Workflow. Is it possible to have the notifications come from a bot (with no mention of the real user who set up the Workflow initially), or are we forced to create a service principal account from which to set up all of the needed Workflows?

Thank you all.

Quick Links

Leaderboard > Power Automate - General Discussion