Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actions fails to publish cards in new MS Teams Workflows #70

Open
carriquiry-g opened this issue Oct 29, 2024 · 3 comments
Open

Actions fails to publish cards in new MS Teams Workflows #70

carriquiry-g opened this issue Oct 29, 2024 · 3 comments

Comments

@carriquiry-g
Copy link

carriquiry-g commented Oct 29, 2024

Since July 3rd 2024, Microsoft has retired Office 365 connectors within Microsoft Teams.
I have tried changing it to the new way that Microsoft has provided and this action is failing to adapt.
image

The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array.

I believe changing the way the card is structured following the adaptive card schema should fix this issue.

@jdcargile please take a look. This should be a simple fix and right now this action cant be used.

@LennardSchwarz
Copy link

Can confirm. I failed to setup Teams Notifications using the new recommended way, which is using Power Automate Flows.

This is my flow:
Screenshot 2024-10-30 at 08 05 45

@jdcargile , you can use this tool to build a new template:
https://adaptivecards.io/designer/

@carriquiry-g
Copy link
Author

https://adaptivecards.io/designer/

Nice tool! I'll wait a few days for @jdcargile to answer. If not I'm making a fork of this action to (at least) comply with the new mechanics.

@carriquiry-g
Copy link
Author

Hey everyone that comes here looking for a solution. I have worked on an action that takes in the changes made by Microsoft Teams.
You can find it in this repo and here is the published action.

Note

You may need to make some adjustments to the workflow to make it work and understand the JSON received. Here is my working workflow:
image
In the future I will add this to the action documentation or even generate a workflow template that works from the get-go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants