Trading bot

Actions

Trigger
Message

Trading bot

3Commas · buy · at most every 4 h

This is how the node looks on the board: inputs on the left. As an action it sits at the end of the chain.

Signal to your own trading bot. Sends the alert as a signal to your own trading bot, in the format it expects: 3Commas, WunderTrading, TradersPost, Alertatron, OctoBot or a custom format. Your bot trades, Bellchain never does: Bellchain knows no credentials of your exchange and gives no investment advice. Set the direction and amount here or in the bot. Test alerts do not go to the bot, so that no test places a real order. Trading bots come with the Trader plan and up. Example: “RSI 14 below 30” with “Buy” and 100 USDT to a signal bot in 3Commas.

What it looks like

signal true
alert goes out
held back
cooldown running

The alert comes when the trigger switches from false to true. If it stays true, no second one comes. If it switches again during the cooldown, Bellchain holds the alert back (circle); the replay counts such cases as “held back by the cooldown”.

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.

Bot

Default: 3Commas

Which bot Bellchain formats the signal for. What to set up in the bot is described with each choice and in the docs under “Trading bots”.

3Commas (default): Signal bot with the start condition “API request”: URL https://3c.wtalerts.com/bot/custom, the action’s code from 3Commas in the Code field. Add Bellchain’s sender IP in 3Commas (see the docs).
WunderTrading: Signal bot with the start condition “API request”: URL https://wtalerts.com/bot/custom, the action’s code in the Code field. Add Bellchain’s sender IP (see the docs).
TradersPost: Webhook URL of your strategy; the pair is sent as BTCUSDT, the direction as buy, sell or exit.
Alertatron: Webhook URL from Alertatron; write the command, such as MyKeys(BTCUSDT) { market(side=buy, amount=10%); } #bot, into the Code field.
OctoBot: URL of your OctoBot webhook; exchange and pair come from the candle, the token goes into the Code field.
Custom format: For any other bot: content with placeholders under “More”.

URL

Default: empty · any text, at most 500 characters, must be filled in before activating, empty when you export a chain

Your bot’s webhook URL, starting with https://. Chat services such as Discord or Slack have their own nodes. Some bots keep the secret in the URL; that is why it stays empty when you export the chain.

Code

Default: empty · any text, at most 1,000 characters, empty when you export a chain

Whatever your bot expects as its secret: for 3Commas and WunderTrading the action’s code (buying uses a different one than closing), for OctoBot the token, for Alertatron the whole command. Leave empty if the URL carries the secret (TradersPost). It stays empty when you export the chain.

Direction

Default: Buy / long

What the bot should do. For entry and exit, add two actions, each with its own condition.

Buy / long (default): Entry: buy or open a long.
Sell / short: Sell or open a short, depending on the bot.
Close position: Close the open position; for 3Commas and WunderTrading with the exit code.

Amount

Default: 0 · from 0 to 1,000,000,000

How much per signal, in the unit below. Required for entries with 3Commas and WunderTrading; 0 means: as set in the bot.

Unit

Default: Quote currency

What the amount refers to. Not every bot knows every unit; OctoBot only takes base currency and percent.

Quote currency (default): Such as 100 USDT for BTC/USDT.
Percent of balance: Such as 10 for 10% of the available balance.
Base currency: Such as 0.01 BTC for BTC/USDT.

Content

Default: empty · any text, at most 2,000 characters, multi-line · under “More”

Your own content instead of the template, as JSON or text, with placeholders such as {{symbol}} (BTCUSDT), {{pair}}, {{action}}, {{price}}, {{time}}, {{token}} or {{amount}}. Leave empty for the selected bot’s template. Secrets belong in the Code field, here only {{token}}.

Test alerts

Default: Do not send · under “More”

Whether test alerts, for example from the test signal, go to the bot.

Do not send (default): Test alerts only go to the history, with the content that would have been sent.
Send: Test alerts go to the bot as well, for example for a paper account. A live bot then really trades.

At most every … hours

Default: 4 h · from 0 to 168 h

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

Default: {{chain}}: {{values}} · any text, at most 1,000 characters, multi-line

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

On RSI below 30, sends a buy signal over 100 USDT to a signal bot in 3Commas; the trade happens there, not in Bellchain (Trader plan).

How to connect the nodes:

Candle (Price) → RSI (Value)
RSI (RSI) → Compare (Value)
Compare (true/false) → Trading bot (Trigger)

On the board it reads: 3Commas · buy · 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: Trading bot",
  "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": "b1", "type": "core.bot", "position": { "x": 700, "y": 40 }, "settings": { "bot": "3commas", "url": "https://3c.wtalerts.com/bot/custom", "token": "enter-long-code", "action": "buy", "amount": 100, "amountType": "quote" } }
  ],
  "edges": [
    { "from": "c1.close", "to": "r1.in" },
    { "from": "r1.out", "to": "k1.in" },
    { "from": "k1.out", "to": "b1.in" }
  ]
}

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

Search also finds it under: notification, message, alert, bot, trading, signal, automation, 3commas, wundertrading, traderspost, alertatron, octobot.

Technical details

POST over IPv4 from the fixed address in the docs (for bots that accept only listed IPs), https only, no redirects. Retries only on 429, 503 and connection errors before sending, for at most 2 minutes, so that no order is placed twice. Placeholders in the content: {{token}}, {{action}}, {{ACTION}}, {{symbol}}, {{pair}}, {{base}}, {{quote}}, {{exchange}}, {{price}}, {{time}}, {{timestamp}}, {{amount}}, {{amount_type}}, {{chain}}, {{message}}, {{id}}.

Type in the chain: core.bot · Version 1.0.0 · Category key act
Settings in the chain: bot (Bot), url (URL), token (Code), action (Direction), amount (Amount), amountType (Unit), body (Content), tests (Test alerts), cooldown (At most every … hours), message (Message)
Pins in the chain: Input in, message
Effect: notifies via Trading bot
How a node is built

Version 2026.10.21.23 · Changelog