microsoft / microsoft/AdaptiveCards

[Authoring] Adaptive cards not taking any action on Action.Submit and no input is passed on to the Power Automate flow after clicking the button

Open
#8,918 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Schema Bug
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Target Application

Microsoft Teams

Application Operating System

Windows

Schema Version

1.4

Problem Description

Adaptive cards not taking any action on Action.Submit and no input is passed on to the Power Automate flow after clicking the button.
image
Upon clicking either of the buttons, the following message is posted and no action is taken on the clicked buttons.

image
The above image is where the flow is waiting for the input and no input is returned even after clicking the buttons.

Expected Outcome

The buttons should be actionable and should execute the intended action.

Actual Outcome

Clicking on the button has no action.

Card JSON
{
  "type": "AdaptiveCard",
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "version": "1.3",
  "body": [
    {
      "type": "Input.Text",
      "id": "name",
      "label": "Please enter your name:",
      "isRequired": true,
      "errorMessage": "Name is required"
    }
  ],
  "actions": [
    {
      "type": "Action.Submit",
      "title": "Cancel",
      "associatedInputs": "none"
    },
    {
      "type": "Action.Submit",
      "title": "Submit"
    }
  ]
}
Repro Steps

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in Microsoft Teams with the supplied Adaptive Card JSON and inspect how Action.Submit handles associatedInputs and the Power Automate flow. Done means both buttons are actionable and the expected input reaches the flow; the issue provides no repository file or test entry point to begin from.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.