On demand · Product video
Collect quality test values in Microsoft Teams with adaptive cards in Quality Inspector
For quality teams that want inspectors to enter test values from a Microsoft Teams channel and have the results go back to Business Central.

Summary
Quality Inspector provides adaptive card content that Power Automate can post to Microsoft Teams to collect test values. The video builds a flow that starts when a quality inspection test is created in Business Central, gets the adaptive card JSON for that test, posts it to a Teams channel as the Flow bot, and waits for a response. It then sends the submitted card back to Business Central with the process adaptive card JSON action. After a new test is created, the card appears in Teams, the saved values show on the test in Business Central, and a finished test displays as a read-only card with the resulting grade.
Key topics
- Start a flow when a quality inspection test is created
- Post the adaptive card for a test to a Microsoft Teams channel
- Send the submitted values back to Business Central
- Save or finish a test from Microsoft Teams
Read the transcript
We’re going to walk through a quick example of using Power Automate to take adaptive card information from Business Central, post it for collecting quality inspection test values, and send the result back to Business Central for processing. In our example, we’re going to use “when a quality inspection test is created” as our trigger. The first thing we’re going to do is get the adaptive card JSON. We use the Get record (V3) action, connect it to the IWX quality adaptive cards, and then use the ID from the Business Central event.
Once we have that adaptive card response, we post it into Teams. So the first step creates the JSON for the adaptive card, and this step puts it into Teams to collect the information. In our example, we post it as the Flow bot into a channel, and the message comes directly from the Get record response; we use this adaptive card JSON here. We post it into our Insight Works examples team and our quality inspectors channel, and that collects the information and waits for it to be submitted in Teams.
If you’re doing a demo or training, in the settings for this action, consider setting the action timeout to a small value, just to prevent flows from queuing up. The final step is to take that adaptive card response and send it back into Business Central. We use the Run action with the API category quality inspection, and then the process adaptive card JSON action, and we just use the system ID. You could use either system ID here; it doesn’t matter, they’ll be the same.
Then the input adaptive card JSON, which you’ll see if you click Show all, we set to the body, which is the result of the post adaptive card and wait for a response step. And that’s it. Okay, so we’re now going to save that and publish it.
Now we head into Business Central to test it out. We’re going to create a new quality inspection test. Let’s find a template here, create a new test with it, choose this example, and choose OK. So a test has been created, and behind the scenes this should have triggered the Power Automate flow to start, and we should now see a message in Teams. If we head into Power Automate and look at our flows, we can see that we’ve got one triggered.
If we navigate to our Business Central channel and look at our activity, we can see that we now have a new test waiting for us, asking for the values we want. We’ll say this is all good, we’ll choose green, and we’ll set this. When you’re doing this, you won’t have access to all of the actions. Save just saves the values, and Save and Finish actually finishes the test. We’re just going to save the values for now.
This takes the response and sends it back into Business Central, and if we look at the test in Business Central and refresh, we’ll see that the values have all been set. So that’s an example walkthrough of how you would create it. You can do the same with finish. Let’s say we finish this test. The only real difference is that a test in a finished state isn’t displayed with editable values; it’s non-editable instead.
If we look at what that did in Teams, we have another workflow for when a test has been finished, and you’ll see it looks very similar, except that you can’t change the values, and it’s just showing the resulting pass grade. So that is how you connect and use adaptive cards with Quality Inspector and Microsoft Teams.
Questions about this webcast?
Send your question and the Insight Works team will reply by email. Ready to plan a project? Contact your Microsoft Partner.
Ask a question
More recordings
Webinar recording · 38 minBusiness Central quality is a starting point: Here’s how partners take it furtherQuality InspectorRecorded May 2026
Webinar recording · 60 minTransform your quality assurance process with Dynamics 365 Business CentralQuality InspectorRecorded February 2026
Product video · 2 minRecord notes on quality test values in Quality InspectorQuality InspectorRecorded April 2025