Core concepts
The five things you'll touch in Signalync, and how they fit together.
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).
Route
A Routeconnects one Source to one or more Targets, with an optional ordered pipeline of Steps in between. Routes 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."
Target
A Target is where a signal lands, usually an MT5 broker, but also Telegram channels, Discord channels, or generic HTTP webhooks. Each Target dispatches independently; if one is offline, the others still go through.
Step
A Stepis a single transformation or filter inside a Route. Steps run in order. Filter steps drop signals that don't match (wrong symbol, outside the configured time window). Transform steps modify signals (rename symbols, scale volumes, customize comments). Score steps annotate signals (e.g. AI confidence). See the step 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-Target Delivery record showing whether the trade landed at each broker.
Glossary
| Source | Where signals enter Signalync |
| Target | Where signals are dispatched (MT5 / Telegram / Discord / HTTP) |
| Route | One Source → many Targets, with an ordered Step pipeline |
| Step | A single filter / transform / score inside a Route |
| Signal | One trade instruction received from a Source |
| Delivery | Per-Target record of how a Signal was dispatched |
| Pairing key | Auth credential the MT5 EA uses to identify itself to its Target |
| Auth key | Per-Source URL token used for the inbound webhook |