Microsoft Teams
- Trigger
- Message
Teams · at most every 4 h
Message to a Teams channel. Sends the alert as a card to a Microsoft Teams channel. Create a workflow in the channel: “…” next to the channel, “Workflows”, template “Send webhook alerts to a channel”, then copy the URL it shows. You need a Microsoft 365 work or school account for this. Teams comes with the Community plan. Example: the alert appears as a card with name, message and values in the channel.
What it looks like
Section titled “What it looks like”- signal true
- alert goes out
- held back
- cooldown running
Settings
Section titled “Settings”The settings appear on the right under “Properties” once you click the node on the board. Below each field you find the same explanation as here.
Workflow URL
Section titled “Workflow URL”The workflow URL from Teams; it ends with a long signature (sig=…). Anyone who knows it can post to the channel. That is why it stays empty when you export the chain.
At most every … hours
Section titled “At most every … hours”Cooldown: after an alert the action waits at least this long before the next one. 4 hours suit most chains. 0 means an alert every time the condition turns true.
Message
Section titled “Message”The alert text. {{chain}} inserts the chain’s name, {{values}} the values of the nodes, {{price}} the price; there are also {{pair}}, {{coin}} and {{time}}. Use **bold**, _italic_ and `code` to highlight text. If a message template is connected to the Message input, its text is used instead.
Example
Section titled “Example”Sends the alert as a card through a workflow to a Teams channel (Community plan).
How to connect the nodes:
- Candle (Price) → RSI (Value)
- RSI (RSI) → Compare (Value)
- Compare (true/false) → Microsoft Teams (Trigger)
On the board it reads: Teams · at most every 4 h
Chain as JSON
To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.
{ "name": "Example: Microsoft Teams", "version": 1, "nodes": [ { "id": "c1", "type": "core.candle", "position": { "x": 40, "y": 40 }, "settings": { "pair": "BTC/USDT", "timeframe": "1h" } }, { "id": "r1", "type": "core.rsi", "position": { "x": 260, "y": 40 }, "settings": { "length": 14 } }, { "id": "k1", "type": "core.compare", "position": { "x": 480, "y": 40 }, "settings": { "operator": "below", "value": 30 } }, { "id": "m1", "type": "core.teams", "position": { "x": 700, "y": 40 }, "settings": { "url": "https://default0123456789abcdef.12.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/0123456789abcdef0123456789abcdef/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=example-signature" } } ], "edges": [ { "from": "c1.close", "to": "r1.in" }, { "from": "r1.out", "to": "k1.in" }, { "from": "k1.out", "to": "m1.in" } ]}Inputs and outputs
Section titled “Inputs and outputs”Only matching types connect: number series to number series (round pin), signal to signal (square), message to message (diamond).
| Direction | Pin | Type | Note |
|---|---|---|---|
| Input | Trigger | Signal (true/false) | required |
| Input | Message | Message | optional |
| Output | – | – | No outputs. |
Good to know
Section titled “Good to know”- Search also finds it under: notification, message, alert, teams, microsoft, team, channel.
Technical details
Section titled “Technical details”POST of an Adaptive Card to the workflow URL (*.powerplatform.com, signed with sig=). Teams answers 202 and does not report whether the post reached the channel; at most 25 posts per 5 minutes per workflow.
- Type in the chain:
core.teams· Version 1.0.0 · Category keyact - Settings in the chain:
url(Workflow URL),cooldown(At most every … hours),message(Message) - Pins in the chain: Input
in,message - Effect: notifies via Microsoft Teams
- How a node is built
Version 2026.10.21.23 · Changelog