Core concepts

The five things you'll touch in Signalync, and how they fit together.

SOURCETradingView · Telegram · APIFLOWordered Rule pipelineMT5 brokerTelegram channelDiscord / HTTP webhook

Source

A Sourceis where signals come from. Each Source has an authentication key and (optionally) an HMAC secret. The four kinds are TradingView (webhook), Telegram (bot listening to a channel), REST API (anything that can POST JSON), and Manual (the dashboard's "Send signal" page).

Flow

A Flowconnects one Source to one or more Destinations, with an optional ordered pipeline of Rules in between. Flows are how you express "when this Source fires, send the signal to these brokers and broadcast it to that Telegram channel, but only on weekdays and only for EURUSD."

Destination

A Destination is where a signal lands, usually an MT5 broker, but also Telegram channels, Discord channels, or generic HTTP webhooks. Each Destination dispatches independently; if one is offline, the others still go through.

Rule

A Ruleis a single transformation or filter inside a Flow. Rules run in order. Filter rules drop signals that don't match (wrong symbol, outside the configured time window). Transform rules modify signals (rename symbols, scale volumes, customize comments). Score rules annotate signals (e.g. AI confidence). See the rule catalog for the full list.

Signal

A Signal is one trade instruction, what to do, on which symbol, with what risk parameters. Signalync logs every signal received plus a per-Destination Delivery record showing whether the trade landed at each broker.

Glossary

SourceWhere signals enter Signalync
DestinationWhere signals are dispatched (MT5 / Telegram / Discord / HTTP). API name: target
FlowOne Source → many Destinations, with an ordered Rule pipeline. API name: route
RuleA single filter / transform / score inside a Flow. API name: step
SignalOne trade instruction received from a Source
DeliveryPer-Destination record of how a Signal was dispatched
Pairing keyAuth credential the MT5 EA uses to identify itself to its Destination
Auth keyPer-Source URL token used for the inbound webhook

Building against the API?

The REST API, webhook payloads, and signal format keep the original technical names: route, target, and step. Only the product UI and these docs use the plain-language names.