OK….after a bunch of troubleshooting and support telling me it’s a limitation from Microsoft, I figured this out on my own. ;(

In Microsoft Teams, in your connector, you must first use the Parse JSON object. Parse the “body” of your message and set this as your schema:

{
    "type": "array",
    "items": {
        "type": "object",
        "properties": {
            "type": {
                "type": "string"
            },
            "text": {
                "type": "string"
            }
        },
        "required": u
            "type",
            "text"
        ]
    }
}

Once you have the intermediary step, you can set the following step to post to a channel:

I used the “Post message in a chat or channel”. Using this method instead of Post with a card allowed me to have a message that wouldn’t be truncated. In looking at this method, there is no current plan to decommission it that is noted from Microsoft in the help file.

Here’s the result of my final workflow with simple lorem ipsum text:

We just started playing with this so following to learn more but we took a different path in setting up an email address for power automate, we just use FS to send an email with a subject and details then parse and act on it through a power automate script. Less integration within FS and allows us to just do everything in power automate directly.

Hi, by default, messages sent via Power Automate use Adaptive Cards, and unless you explicitly enable wrapping ("wrap": true) in the card’s schema, text will truncate after a certain width/line count. That’s why your old Office 365 connector messages looked fine, but the new ones are clipped. In your power automate you can replace the card JSON with your updated schema from the adaptive card designer with (“wrap”: true). Freshwork’s own example on their page is truncated because they might’ve not set wrap: true.

Hi ​@mbutler 

You can simply use 

"msteams": {  
        "width": "Full"  
    }

in your schema to make the card full width. 

I have been looking at setting up some new communciations between Freshservice and Teams, and also came accross the same documentation with regards to the updated method using Power Automate.

MS Teams Connector Deprecation : Freshservice

I’m experiencing the same issue and this needs resolving from Freshworks as the informational update is unable to be read in full.

Change Teams card with Microsoft Power Automate | Freshworks Community

I have used the above as a workaround solution.

Use this in the schema to get a full width adaptive card in Teams:

"msteams": {  
        "width": "Full"  
    }

Thanks - I had posted a solution the other day, but it appears it hasn’t been approved by the moderators quite yet. As noticed in the other one though, the solution is exactly the same. You must modify the schema for the card to include the wrap property and set it to true since it is false by default.

I also updated the support personnel because I had called it in

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "text": "@{triggerOutputs()?['body/attachments'][0]['content']['body'][0]['text']}",
            "wrap": true,
            "maxLines": 0
        }
    ],
    "version": "1.2"
}

Thanks for posting

Heyy ​@mbutler 

I had approved both your posts. But, is there any other post to be approved for this thread? Can you confirm? I do not see anything in the pending bucket.