Cheat sheet

Adaptive Card Payload Cheat Sheet

Reusable Adaptive Card payload ideas for Teams approvals, request summaries, task cards, and action buttons.

Adaptive Cards TeamsPower Automate adaptive cardTeams approval card

Who this helps

Flow builders sending actionable Teams messages from Power Automate.

What to standardize

Keep cards short and action-oriented.
Show the business identifier near the top.
Use facts for scannable metadata.
Make button actions match the flow branch names.

Examples

Request review card skeleton

Send a clear Teams card for a request approval.

Formula / code

{
  "type": "AdaptiveCard",
  "version": "1.4",
  "body": [
    { "type": "TextBlock", "text": "Request review needed", "weight": "Bolder" },
    { "type": "FactSet", "facts": [
      { "title": "Request", "value": "@{triggerBody()?['Title']}" },
      { "title": "Priority", "value": "@{triggerBody()?['Priority']?['Value']}" }
    ] }
  ]
}

Expected result: Reviewers receive a structured Teams message with the key request facts.

Common mistakes

Overloading the card with every field
Not testing mobile Teams
Using action labels that do not match flow logic