Signals

Signals Overview

What TradingForge Signals are, how the relay works, and how to get started sending automated trade instructions to your bot from any source.

TradingForge Signals is a real-time webhook relay system that lets external tools — trading view alerts, custom scripts, third-party signal providers, or your own automation — send trade instructions directly to your running bot. When a signal arrives, the bot can immediately execute a buy, sell, DCA, stop-loss override, or a range of other actions on your behalf.

How It Works

Signals uses a cloud relay hosted at signals.tradingforge.net built on Cloudflare Workers and Durable Objects. Your bot maintains a persistent WebSocket connection to this relay. When a signal provider sends an HTTP POST to your unique webhook URL, the relay immediately forwards the payload over the WebSocket to your bot.

›Relay — signals.tradingforge.net hosted on Cloudflare globally. Your bot connects once; the relay keeps the connection alive automatically.
›Webhook URL — a unique URL tied to your license. Only payloads sent to your specific URL reach your bot.
›License-bound — your signal token is generated when you activate your license and is unique per license key.
›Zero port-forwarding — your bot connects outbound to the relay. No inbound ports need to be opened on your machine or router.

Signals requires an active TradingForge license. The signal token is generated automatically during license activation and can be regenerated at any time from the Settings → Signals tab.

What Can Signals Do?

Once connected, signals can trigger any of the following actions on your bot:

›buy — open a new position on a pair
›sell — close an open position immediately
›cancel — cancel a pending signal before it triggers a buy
›close_all — sell all open positions at once
›dca — force a DCA safety order on an open position
›set_stop_loss — override the stop-loss percentage for a specific pair
›set_take_profit — override the take-profit target for a specific pair
›pause — pause trading on a specific pair
›resume — resume trading on a paused pair

See the Supported Actions article for full payload schemas for each action type.

Relay Architecture

Signal Token

Your signal token is a UUID generated by the License Server when your license is activated. It is stored server-side and validated every time a provider sends a webhook. The token serves two purposes: it identifies which bot instance to route the signal to, and it authenticates the request so that only your providers can send signals to your bot.

WebSocket Connection

The bot connects to wss://signals.tradingforge.net/connect?token=YOUR_TOKEN on startup (if Signals is enabled). The relay uses Cloudflare's WebSocket Hibernation API, which means the connection survives even during relay updates or temporary network interruptions — the bot reconnects automatically with exponential backoff.

Webhook Endpoint

Providers POST signals to https://signals.tradingforge.net/webhook/YOUR_TOKEN. The relay validates the token, then forwards the JSON payload to your connected bot immediately. If the bot is not connected, the signal is not queued — it is dropped. Rate limiting is applied (configurable in Settings) to prevent runaway signals.

The relay does not queue or store signals. If your bot is offline when a signal arrives, the signal will be dropped. Make sure TradingForge is running and connected before activating signal-dependent strategies.

Getting Started

›1. Activate your license — a signal token is generated automatically.
›2. Open Settings → Signals and enable Signals.
›3. Copy your Webhook URL from the Settings → Signals tab.
›4. Paste the URL into your signal provider (TradingView alert webhook, custom script, etc.).
›5. Choose your Signal Mode — Signal for full automation or Hybridto require a signal before the bot's normal buy conditions trigger.

Continue reading: Webhook Setup →

Error Message Reference

Webhook Setup