Message template
Text with placeholders such as {{coin}} and {{price}}. Builds the text for connected actions. Placeholders: {{chain}}, {{values}}, {{price}}, {{pair}}, {{coin}}, {{time}} and {{a}} to {{d}} for the values at inputs A to D. Numbers and times appear in the recipient language.
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 | A a |
Number series | optional |
| Input | B b |
Number series | optional |
| Input | C c |
Number series | optional |
| Input | D d |
Number series | optional |
| Output | Message out |
Message | – |
Settings
Section titled “Settings”The settings appear on the right under “Properties” once the node is selected on the board. Those marked “More” appear after clicking “More”.
| Setting | Default | Allowed | Meaning |
|---|---|---|---|
Text text |
{{kette}}: {{werte}} |
any text, at most 1000 characters, multi-line | – |
Example
Section titled “Example”The template is connected to the action’s “Message” input. The trigger still comes from the comparison.
On the board it reads: {{coin}} is oversold: RSI {{a}} at {{price}}
Chain as JSON
To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.
{ "name": "Example: Message template", "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.message", "position": { "x": 480, "y": 170 }, "settings": { "text": "{{coin}} is oversold: RSI {{a}} at {{price}}" } }, { "id": "t1", "type": "core.telegram", "position": { "x": 700, "y": 40 }, "settings": {} } ], "edges": [ { "from": "c1.close", "to": "r1.in" }, { "from": "r1.out", "to": "k1.in" }, { "from": "r1.out", "to": "m1.a" }, { "from": "k1.out", "to": "t1.in" }, { "from": "m1.out", "to": "t1.message" } ]}Good to know
Section titled “Good to know”- Search also finds it under: text, message, template, placeholder.
Technical details
Section titled “Technical details”- Type in the chain:
core.message· Version 1.0.0 · Category keydata - How a node is built