Core concepts

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

SOURCETradingView · ManualFLOWordered Rule pipelineMT5 brokerTelegram channel (soon)Discord / HTTP (soon)

Source

A Source is where signals come from. Each Source has an authentication key and, optionally, an HMAC secret. Two kinds are live today: TradingView (webhook alerts) and Manual (the dashboard's "Send signal" page).

Two more kinds, Telegram (a bot listening to a channel) and REST API (anything that can POST JSON), are built and visible in the app with a "Coming soon" chip. They cannot be enabled for new setups yet.

Flow

A Flow connects 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 MT5 accounts, but only on weekdays and only for EURUSD."

Destination

A Destination is where a signal lands. Today that means an MT5 account, linked through the Signalync Receiver EA running in your terminal, or an HTTP webhook pointed at your own system. Each Destination dispatches independently; if one is offline, the others still go through.

Telegram channels and Discord webhooks are built as Destination kinds too. They show in the app with a "Coming soon" chip and cannot be enabled yet.

Rule

A Rule is a single filter or transformation 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). 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 a Signal is dispatched. MT5 and HTTP webhook Destinations are live today; Telegram and Discord Destinations are coming soon. API name: target
FlowOne Source feeding one or more Destinations through an ordered Rule pipeline. API name: route
RuleA single filter or transform inside a Flow. API name: step
SignalOne trade instruction received from a Source
DeliveryPer-Destination record of how a Signal was dispatched
Pairing keyCredential shown once when an MT5 Destination is created. You paste it into the Receiver EA's <code>LicenseKey</code> input to pair your terminal with the 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.