TradingView

Receive signals from TradingView alert webhooks. The most common Signalync setup.

Prerequisites

You need a TradingView plan that supports webhook alerts. TradingView offers webhooks on its paid plans only: the free plan cannot call a webhook URL when an alert fires.

Already on a paid TradingView plan?

You can add your signal link to any existing alert. No new indicator or strategy is required.

Setup

Follow these steps to connect TradingView to Signalync. If you just signed up, the setup wizard on your dashboard walks you through the same flow.

  1. 1

    Create a TradingView source

    In the Signalync dashboard open Sources, click New source, and select TradingView as the kind.
  2. 2

    Name it

    Give the source a descriptive name, e.g. "TV: BTC strategy" or "TV: EURUSD scalper".
  3. 3

    Copy your signal link

    Create the source and Signalync reveals your personal signal link. Copy it right away: the full link is shown only once, and if you lose it you can rotate the key from the Sources page to get a fresh one. It looks like: https://signalync.com/api/inbound/YOUR_SOURCE_KEY
  4. 4

    Create a TradingView alert

    In TradingView, open the Alerts panel (clock icon) and click Create alert. Set your condition as usual.
  5. 5

    Paste the link into Webhook URL

    In the alert dialog open the Notifications tab, enable Webhook URL, and paste the signal link you copied from Signalync.
  6. 6

    Set the message body

    In the Message field, enter your signal text. See the signal format section below for examples.
TradingView calls your signal link with the message body the moment the alert condition triggers. Signalync receives it, parses the signal text, and routes it through your Flow to your MT5 destination.

Signal format

The message body you enter in TradingView's alert dialog is the signal payload. Signalync uses a compact, comma-separated format.

Minimal example

{{ticker}},buy,vol=0.1
signal

With stop loss and take profit prices

XAUUSD,buy,vol=0.1,sl=2340,tp=2360
signal

TradingView placeholders

Use {{ticker}} to insert the chart symbol automatically, and {{strategy.order.action}} to insert the strategy action (buy / sell) when firing from a Pine Script strategy.

Signalync accepts the full signal syntax, so you can already write richer signals like these:

Pips-based stop loss and take profit

{{ticker}},{{strategy.order.action}},vol=0.1,sl_pips=50,tp_pips=100
signal

Multi-TP with risk-based sizing

XAUUSD,sell,vol_pctbal_loss=1,sl_pips=40,tp1_pips=40,tp2_pips=80,tp3_pips=120
signal

Pending order

GBPUSD,buylimit,entry=1.2650,vol=0.5,sl_pips=30,tp_pips=60
signal

Advanced execution is coming soon

Advanced parameters like the ones above are accepted by the platform and stored with each signal, but they are not yet executed by the MT5 connector. Today the connector executes the action (buy, sell, close), the symbol, the volume in lots, and absolute stop loss and take profit prices. Pips-based distances, risk-based sizing, multiple take-profits, pending orders, trailing stops, and breakeven are coming soon. Watch the changelog to catch the moment they go live.

See the full signal format reference for all volume, stop loss, take profit, trailing stop, and order type parameters.

Shared secret (optional)

By default, anyone who knows your signal link can send signals to it. To restrict this, set a secret on the Source.

When a secret is set, Signalync requires every inbound request to include an X-Signalync-Secret header whose value matches the secret exactly. Requests without a matching header are rejected with 401.

TradingView cannot send custom headers

TradingView webhooks cannot attach custom headers, so a secret is only useful if you proxy TradingView alerts through your own server before forwarding them to Signalync. For most setups, the security of an unguessable signal link is sufficient.

Troubleshooting

Alert fired but no signal appeared in Signalync

Check that the TradingView alert is still Active (not expired or paused): open the Alerts panel and look for a warning icon. Also confirm the Source is switched on in Signalync (a disabled Source rejects incoming requests) and that the webhook URL in the alert is your current signal link.

Signal received but not parsed

Open the signal from the Signals page: the detail view shows the raw payload and the parse error. Check the signal format reference and make sure there are no stray spaces or unexpected characters in the message body.

401 Unauthorized

The signal link contains a wrong or outdated key. The full link is shown only once, so if you no longer have it, rotate the key from the Sources page and paste the fresh link into the TradingView alert.

Requests rejected after setting a secret

The X-Signalync-Secret header must match the secret exactly (the comparison is case-sensitive). TradingView cannot send custom headers at all, so remove the secret from any Source that receives TradingView webhooks directly.