The CloudRadial AutomationAI Microsoft Teams extension lets a workflow or agent post messages, Adaptive Cards, and severity-tagged alerts into Microsoft Teams. It posts through a Power Automate cloud flow that you build in your own Microsoft 365 tenant. This article covers how the extension reaches Teams, how to build the flow, the one secret it needs, and the skills that ship with it. It is for workspace users who build automations (Admin or Owner Role).
- How the Extension Posts to Teams
- What the Extension Covers
- Building the Power Automate Flow
- Providing the Flow URL to Your Runner
- Posts and Approval
- Skills
- Tips and Troubleshooting
How the Extension Posts to Teams
The extension does not use a Teams incoming webhook. Instead, you build a small Power Automate cloud flow that starts with the When an HTTP request is received trigger and ends with a Post message in a chat or channel action. The extension sends a JSON message to the flow's HTTP POST URL, and the flow posts it into Teams.
The flow URL is both the address and the credential. It carries its own signature in its sig= query parameter, so there is no separate token or key.
What the Extension Covers
The extension provides five tools. Each sends the flow a fixed messageType along with the fields that message type uses:
| Tool | messageType |
Fields sent |
| Post a message | message |
text |
| Post a titled message | messageWithTitle |
title and text |
| Post an Adaptive Card | adaptiveCard |
card, a complete Adaptive Card JSON object |
| Post to a specific channel | channel |
text, channelId, and teamId |
| Post an alert | alert |
title, text, and severity (info, warning, or critical) |
What each message looks like in Teams, and where it lands, is decided by your flow. The extension only delivers the payload.
Install it from Extensions like any other catalog extension. See Browsing and installing extensions for the general install flow.
Building the Power Automate Flow
- Go to make.powerautomate.com and create a new Instant cloud flow (or an automated one). For the trigger, choose When an HTTP request is received.
- On the trigger card, set Who can trigger the flow? to Anyone, then paste a Request Body JSON Schema that accepts the fields above. A minimal schema:
{"type":"object","properties":{"messageType":{"type":"string"},"title":{"type":"string"},"text":{"type":"string"},"card":{"type":"object"},"channelId":{"type":"string"},"teamId":{"type":"string"},"severity":{"type":"string"}}} - We recommend adding a Switch on
triggerBody()?['messageType']so the flow can format plain messages, titled messages, Adaptive Cards, and alerts differently - Add the Teams Post message in a chat or channel action, posting as the Flow bot or as the user. Set the Team and Channel, either as fixed values or, for the channel branch, from the incoming
teamIdandchannelId. Set the Message to the incomingtitleandtext, or build an Adaptive Card fromcardfor the Adaptive Card branch. - Save the flow. Power Automate then fills in the HTTP POST URL on the trigger card. Copy the full URL; it ends with
&sig=….
Providing the Flow URL to Your Runner
Store one secret in your runner's Key Vault with this exact name:
| Secret | Value |
Teams-FlowUrl |
The full HTTP POST URL from your flow's When an HTTP request is received trigger, including its sig= parameter |
Treat the flow URL like a password: anyone who has it can post through your flow. If it leaks, regenerate the SAS key on the trigger to invalidate the old URL, then update the secret. For how to add or update secrets, see Accessing and updating your runner's Key Vault. The agent reads the URL from the runner and never asks you for it.
Posts and Approval
None of the five tools is approval-gated. Posting a notification is treated as a low-risk outbound action, so a post goes out as soon as the workflow or agent sends it, without creating an Action Required item in the Inbox. The extension does not read anything from Teams.
Skills
The extension ships three skills that guide an agent through posting to Teams:
| Skill | Use it to |
| Send a Teams Notification | Deliver a notification or status update from a workflow as plain text, a titled message, or a post to a specific channel |
| Post an Adaptive Card | Post a rich Adaptive Card, with formatted blocks, facts, or actions, instead of a plain text line |
| Send a Teams Alert | Raise an info, warning, or critical alert, such as a monitoring or incident notification, that your flow can color or route by severity |
To give an agent these skills, see Creating custom agents and using them in workflows.
Tips and Troubleshooting
- A successful step means the flow accepted the message. The post into Teams happens inside the flow, so if the step succeeds but no message appears, check the flow in Power Automate.
- If every post fails with an authorization error (HTTP 401 or 403), the flow URL in
Teams-FlowUrlis wrong or its SAS key was regenerated. Copy the current URL from the trigger card and update the secret. - To post to a specific channel, the agent needs the channel and team ids, and your flow must route the channel branch with them
If you are still having trouble, we’re here to help! Submit a ticket here for assistance, and don’t forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Please sign in to leave a comment.