Issues trying to use existing MessageCard payload in Workflow

Question

Issues trying to use existing MessageCard payload in Workflow

Matherly, Toby 10

After following the steps provided here the workflow is failing when sending existing MessageCard payload. This payload is currently working using the old webhook in teams. Teddie-D suggested starting a new question with the details.

https://community.powerplatform.com/forums/thread/details/?threadid=915c0cfb-d5eb-f011-8544-000d3a554a74

Steps tried: Following instructions from above link

Generated workflow code: I attached the export of the flow. I had to change the ext from zip to txt for it to work.

Exact error message:

Action 'Post_card_in_a_chat_or_channel_1' failed: Microsoft.Azure.ProcessSimple.Data.Entities.Exceptions.ProcessSimpleDataException: The specified Teams flowbot adaptive card request is missing or invalid. The tracking Id is '{0}'. ---> AdaptiveCards.AdaptiveSerializationException: Property 'type' must be 'AdaptiveCard'

at AdaptiveCards.AdaptiveCardConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer)

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)

at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)

at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)

at Newtonsoft.Json.JsonConvert.DeserializeObjectT

at AdaptiveCards.AdaptiveCard.FromJson(String json)

at Microsoft.Azure.ProcessSimple.Data.Components.AdaptiveCards.AdaptiveCardBuilder.DeserializeAdaptiveCard(String serializedAdaptiveCard, RequestIdentity requestor, CultureInfo cultureInfo, BotAdaptiveCardAtMentions atMentions) in C:__w\1\s\src\processsimple\Roles\ProcessSimple.Data\Components\AdaptiveCards\AdaptiveCardBuilder.cs:line 930

--- End of inner exception stack trace ---

at Microsoft.Azure.ProcessSimple.Data.Components.AdaptiveCards.AdaptiveCardBuilder.DeserializeAdaptiveCard(String serializedAdaptiveCard, RequestIdentity requestor, CultureInfo cultureInfo, BotAdaptiveCardAtMentions atMentions) in C:__w\1\s\src\processsimple\Roles\ProcessSimple.Data\Components\AdaptiveCards\AdaptiveCardBuilder.cs:line 934

at Microsoft.Azure.ProcessSimple.Web.Common.Validation.BotAdaptiveCard(String card, RequestIdentity senderRequestIdentity) in C:__w\1\s\src\processsimple\Roles\ProcessSimple.Data\Common\Validation\BotValidation.cs:line 960

Matherly, Toby 10 Reputation points

2026-03-17T12:33:25.2733333+00:00
AI provided the following:
Convert the MessageCard payload to an Adaptive Card

Workflows do not support the older MessageCard format used by Office 365 Connectors.

Use the official conversion tool referenced in the documentation to transform the existing MessageCard JSON into Adaptive Card JSON: see the guidance in “how to convert connector message card format to Adaptive Card”.

Can you provide a link to the documentation referenced here? official conversion tool referenced in the documentation
Nivedipa-MSFT 4,071 Reputation points Microsoft External Staff Moderator

2026-03-18T06:07:18.79+00:00
Hello Matherly, Toby,
Power Automate’s “Post card in a chat or channel” action supports only Adaptive Cards, not the older MessageCard (Office 365 Connector) format. Since your current webhook payload uses MessageCard, you’re seeing this error:

Property 'type' must be 'AdaptiveCard'

Conversion and Documentation

Microsoft does not provide an official automated conversion tool. You will need to convert the card manually.

Helpful resources:

Adaptive Card Designer for building and testing: [https://adaptivecards.io/designer/]

Adaptive Card schema reference: [https://adaptivecards.io/explorer/]

Microsoft’s migration guidance: Create & Send Actionable Messages - Teams | Microsoft Learn

MessageCard format (legacy, unsupported):

{ "@type": "MessageCard", "@context": "http://schema.org/extensions", "themeColor": "0076D7", "summary": "Build Notification", "sections": [{ "activityTitle": "Build Succeeded", "facts": [ { "name": "Repository", "value": "main-app" }, { "name": "Branch", "value": "main" } ] }] }

Adaptive Card format (required):

{ "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4", "body": [ { "type": "TextBlock", "text": "Build Succeeded", "weight": "Bolder", "size": "Medium" }, { "type": "FactSet", "facts": [ { "title": "Repository", "value": "main-app" }, { "title": "Branch", "value": "main" } ] } ] }

Manual Conversion Steps

Copy your existing MessageCard JSON.

Open the Adaptive Card Designer: [https://adaptivecards.io/designer/]

Recreate your card using Adaptive Card elements (drag-and-drop or JSON editor).

Copy the new Adaptive Card JSON.

Paste it into the Power Automate “Post card in a chat or channel” action’s Adaptive Card field.

Test your workflow.

In Power Automate

The “Post card in a chat or channel” action requires the card in this format:

{ "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4", "body": [ ... ] }

Be sure the root type property is set to "AdaptiveCard", as the error specifically checks for this value.
Luis Torres 0 Reputation points Microsoft Employee

2026-03-18T06:40:32.3333333+00:00

Nivedipa-MSFT MessageCards are now supported, but the card needs to explicitly specify the card type by adding the following property to the JSON card object:

"@type": "MessageCard",
Nivedipa-MSFT 4,071 Reputation points Microsoft External Staff Moderator

2026-03-23T08:21:26.39+00:00

Hello Luis Torres,
This applies to the webhook/connector path. The Power Automate "Post card in a chat or channel" action still requires Adaptive Cards. The MessageCard support is specifically for the workflow webhook URL (the replacement for the deprecated O365 connectors).

3 answers

Your answer

Matherly, Toby 10 Reputation points

2026-03-17T12:33:25.2733333+00:00

AI provided the following:
Convert the MessageCard payload to an Adaptive Card

Workflows do not support the older MessageCard format used by Office 365 Connectors.

Use the official conversion tool referenced in the documentation to transform the existing MessageCard JSON into Adaptive Card JSON: see the guidance in “how to convert connector message card format to Adaptive Card”.

Can you provide a link to the documentation referenced here? official conversion tool referenced in the documentation
Luis Torres 0 Reputation points Microsoft Employee

2026-03-18T06:40:32.3333333+00:00

Nivedipa-MSFT MessageCards are now supported, but the card needs to explicitly specify the card type by adding the following property to the JSON card object:

"@type": "MessageCard",
Nivedipa-MSFT 4,071 Reputation points Microsoft External Staff Moderator

2026-03-23T08:21:26.39+00:00

Hello Luis Torres,
This applies to the webhook/connector path. The Power Automate "Post card in a chat or channel" action still requires Adaptive Cards. The MessageCard support is specifically for the workflow webhook URL (the replacement for the deprecated O365 connectors).

Answer 1

Matherly, Toby 10

JSON Payload: (I pulled this from the error in workflow editor. I assume this is the payload? If not, how do I get it?)
{

"host": {

    "connectionReferenceName": "shared_teams",

    "operationId": "PostCardToConversation"

},

"parameters": {

    "poster": "Flow bot",

    "location": "Channel",

    "body/recipient/groupId": "[Moderator note: personal info removed]",

    "body/recipient/channelId": "[Moderator note: personal info removed]",

    "body/messageBody": "{\"icon_url\":\"\",\"channel\":\"\",\"username\":\"\",\"text\":\"Notification Test 8 https://ansiblegateway.xxx.com\"}"

}
```}  
  
Are you using a built-in template like *"Send webhook alert to a channel"*? << Using the built-in template as instructed in the link I shared in the question.

Are you receiving the error *"Property 'type' must be 'AdaptiveCard'"* directly within the Ansible/AWX logs, or do you see it in the Teams Workflow run history?  <<< Shows successful on ansible side from the UI test.  I see the error on Workflow side in run history.  Pasted the error message from workflow run in original question.  
  
Can you confirm if you are using the built-in "Mattermost" notification type in Ansible Automation Platform, or if you are using a generic "Webhook" type?  <<< Using Mattermost.  Just change the webhook URL for testing.  Still working on the legacy webhook url as pasted above.

Luis Torres 0 Reputation points Microsoft Employee

2026-03-17T18:47:36.7833333+00:00

The body/messageBody property contains the actual card payload. For the action to work, you must specify the card type within the payload. In this case, the type should be a Message Card. For your scenario, it would look like this:

{

"@type": "MessageCard",

"icon_url":"",

"channel":"",

"username":"",

"text":"Notification Test 8 https://ansiblegateway.xxx.com"

}
Matherly, Toby 10 Reputation points

2026-03-17T19:28:51.0066667+00:00

Can I add that in as part of the workflow? It's a custom notification type in ansible so I can't change the json it creates at the front end. I did verify another use case worked without modification here so I'm making progress.
Luis Torres 0 Reputation points Microsoft Employee

2026-03-17T22:33:24.23+00:00

I think It should be technically feasible to modify the flow to include an operation that adds the missing property to the JSON payload when it is not present in the received payload. This would require parsing the payload to check for the '@type' property and, if not found, creating a new JSON object based on the original payload with the property added.

Answer 2

Kudos-Ng 15,050 Microsoft External Staff Moderator

Hi Matherly, Toby,

I have reviewed the link you attached and the suggested answer provided. Based on testing and verified technical behavior, here is a clarification on how Teams handles legacy MessageCard payloads:

1. Built-in Teams Workflow Templates

If you use the built-in Teams template "Send webhook alert to a channel", it does support legacy MessageCard JSON payloads. These specific templates include backward compatibility to help users migrate from old Office 365 Connectors without changing their code. However, even in these templates, button rendering is still not supported for legacy MessageCard. If your card has buttons, they will not render or may cause the card to fail.

2. Custom Power Automate Actions

If you are using a custom flow with the standard "Post card in a chat or channel" action, it will fail with your legacy payload. This action expects a modern Adaptive Card (type: AdaptiveCard). It does not recognize the legacy "@type": "MessageCard" format, which results in the error: Property 'type' must be 'AdaptiveCard'.

Since buttons and interactive elements are only supported in the Adaptive Card format, Microsoft provides tools to help you transform your payloads: Message Card to Adaptive Card Transformation

I hope this distinction helps you choose the right path for your workflow.

Reference: Retirement of Office 365 connectors within Microsoft Teams

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Matherly, Toby 10 Reputation points

2026-03-17T13:35:14.9866667+00:00

This is the output from Ansible Automation Platform mattermost notification that I'm testing with. There is no button. Does it still contain something that won't work with the suggested workflow?
Matherly, Toby 10 Reputation points

2026-03-17T13:37:15.88+00:00
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-17T14:34:53.6033333+00:00
Hi Matherly, Toby,

Thank you for confirming that you are testing with an Ansible Automation Platform notification and that there are no buttons in your card. This helps narrow down the cause.

To investigate this further and provide a precise solution, could you please provide the following information?

The exact JSON payload: Could you share the raw JSON content being sent by Ansible? (Please redact any sensitive information). This will allow us to see if there are any hidden fields or formatting that Teams is rejecting.

Reproduction Steps: Could you describe exactly how you have set up the workflow in Teams?

Are you using a built-in template like "Send webhook alert to a channel" or a custom flow in Power Automate?

Are you receiving the error "Property 'type' must be 'AdaptiveCard'" directly within the Ansible/AWX logs, or do you see it in the Teams Workflow run history?

Ansible Configuration: Can you confirm if you are using the built-in "Mattermost" notification type in Ansible Automation Platform, or if you are using a generic "Webhook" type?

Looking forward you update.
Matherly, Toby 10 Reputation points

2026-03-17T15:11:23.8833333+00:00

Please see my comment below.
Kudos-Ng 15,050 Reputation points Microsoft External Staff Moderator

2026-03-18T08:38:08.98+00:00

Hi Matherly, Toby,

Thank you for providing the payload. Have you had a chance to review Torres' latest response?

If you have any further concerns, please let us know.

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Best regards,

Answer 3

Luis Torres 0 Microsoft Employee

Hi Matherly, Toby

Would you be able to share the Message Card payload?

0 comments

Share via

Issues trying to use existing MessageCard payload in Workflow

3 answers

Your answer