Signal page
- Trigger
- Message
public · at most every 4 h
Alert public on your signal page. Shows the alert publicly on your signal page, with an RSS feed and a widget to embed. Set up the page once under Notifications: short name, title, description and disclosure. The signal page comes with the Community plan. Write about rules and prices, not buy or sell recommendations; every page says “Not investment advice”. Good for creators: your group or website links to the page, and anyone sees the signals without an account. Example: BTC’s “RSI 14 below 30” appears with price and time on your page and in the widget.
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.
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”Shows the alert publicly on your signal page, in the feed and in the widget (Community plan).
How to connect the nodes:
- Candle (Price) → RSI (Value)
- RSI (RSI) → Compare (Value)
- Compare (true/false) → Signal page (Trigger)
On the board it reads: public · 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: Signal page", "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": "p2", "type": "core.page", "position": { "x": 700, "y": 40 }, "settings": {} } ], "edges": [ { "from": "c1.close", "to": "r1.in" }, { "from": "r1.out", "to": "k1.in" }, { "from": "k1.out", "to": "p2.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, public, page, feed, rss, widget, creator.
Technical details
Section titled “Technical details”The alert with this action’s message appears at app.bellchain.app/signals/{short name}, in feed.xml (RSS 2.0), atom.xml and the widget. Other actions of the same chain stay private. Test alerts appear on the page for 15 minutes marked “Test”, never in the feed.
- Type in the chain:
core.page· Version 1.0.0 · Category keyact - Settings in the chain:
cooldown(At most every … hours),message(Message) - Pins in the chain: Input
in,message - Effect: publishes on the signal page
- How a node is built
Version 2026.10.25.16 · Changelog