Slack
- Trigger
- Message
Slack · at most every 4 h
Message to a Slack channel. Sends the alert via webhook to a channel in your Slack workspace, for example for your team. Create the webhook once in Slack: create an app at api.slack.com/apps, turn on “Incoming Webhooks”, “Add New Webhook”, pick the channel and copy the webhook URL. Slack comes with the Community plan. Example: the alert “BTC Dip Buyer: RSI 14: 28.7 · Price: $81,616” appears as a message 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.
Webhook URL
Section titled “Webhook URL”The webhook URL from Slack; it starts with https://hooks.slack.com/services/. Treat it like a password: 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 message via webhook to your team’s Slack channel (Community plan).
How to connect the nodes:
- Candle (Price) → RSI (Value)
- RSI (RSI) → Compare (Value)
- Compare (true/false) → Slack (Trigger)
On the board it reads: Slack · 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: Slack", "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": "s1", "type": "core.slack", "position": { "x": 700, "y": 40 }, "settings": { "url": "https://hooks.slack.com/services/T0123ABCD/B0456EFGH/abcdefghijklmnopqrstuvwx" } } ], "edges": [ { "from": "c1.close", "to": "r1.in" }, { "from": "r1.out", "to": "k1.in" }, { "from": "k1.out", "to": "s1.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, slack, team, channel.
Technical details
Section titled “Technical details”POST to hooks.slack.com with mrkdwn text, no link previews; <, > and & are escaped, mentions such as @channel ping nobody. The delivery log keeps only team and hook.
- Type in the chain:
core.slack· Version 1.0.0 · Category keyact - Settings in the chain:
url(Webhook URL),cooldown(At most every … hours),message(Message) - Pins in the chain: Input
in,message - Effect: notifies via Slack
- How a node is built
Version 2026.10.21.23 · Changelog