TheConnector Relay: test the product without a paid TradingView plan

What it's for

TradingView's native webhook field — the one that lets TradingView itself POST an alert to a URL — requires a paid Essential plan or higher. TheConnector Relay is a browser extension that reads the pop-up TradingView shows in your open chart tab when an alert fires, and forwards its message to your TheConnector webhook instead. It exists so you can test TheConnector end to end, with real history in your dashboard, before committing to a paid TradingView plan.

It is not a replacement for TradingView's native webhook. Treat it as a test/discovery mode: useful to validate your payload, your account routing and your MT4/MT5/cTrader connection, with the browser tab open in front of you.

How it works

• Create your TradingView alert with the same message you would use for a native webhook — /docs/command-syntax-reference and /first-alert both apply unchanged. Leave TradingView's own "Webhook URL" field empty; it is not used.
• In the alert's notifications, keep the pop-up enabled ("Show pop-up"). The extension relays only the pop-up shown when the alert fires, never the alerts log, which also lists alerts that fired hours or days ago.
• Alerts already on screen when the page loads are remembered without being sent: opening or reloading the tab never replays an old signal.
• While the chart tab is visible, it pings the extension's background worker every 20 seconds. That keeps the worker awake and the connection to TheConnector open, so sending an alert takes a single round trip.
• Your access key travels with the request, exactly like a native TradingView webhook, to the same endpoint your account already uses.

{
  "action": "buy",
  "symbol": "{{ticker}}",
  "volume": 0.10,
  "sl": 1.0820,
  "tp": 1.0910
}

You do not need to add an accessKey field yourself; the extension adds it before sending. If you include one anyway, it is respected.

Check that it is listening

Open the TradingView chart, or reload it (F5) if it was already open. A badge appears at the top of the chart:

• en écoute des alertes — the extension is loaded in this tab and waiting for alerts
• à configurer — consent or settings are missing
• rechargez cette page (F5) — the extension was updated or reloaded after the tab was opened
• dernière alerte envoyée ✓ — the last alert went out to your account
• non livrée ✗ or ignorée — the exact reason is in the extension's window

The extension's window, opened by clicking its logo, tells you whether a TradingView tab is connected and lists the last alerts seen: sent, not delivered with the reason returned by the server, or ignored with the reason and what to fix — consent missing, message in the wrong format, alert seen only in the log.

Reliability, on purpose

A failed send is retried up to 3 times in under 5 seconds (immediately, then +400 ms, then +1.5 s), then abandoned and reported. There is no later retry. That is deliberate: TheConnector measures an order's freshness from the moment it receives it, so an alert replayed minutes later would look brand new and be executed on a signal that is no longer valid, at a price that no longer matches it. A refused key or a rejected message is reported at once: sending it again would get the same answer.

• Every detected alert is written to local storage before any network attempt, so a lost connection or a restart of the background worker never loses an alert already captured.
• A duplicate alert (same message, same time shown by TradingView) is filtered twice over: once in the page, once in the persistent queue, which still blocks it after a reload or a browser restart. With several TradingView tabs open, an alert is sent only once.
• A failure is never silent: the extension icon turns red and its window shows the reason.

What it does not do

Read this before relying on it for anything but testing:

• It needs your browser open on the TradingView chart for the whole time you want alerts relayed. Closing the tab or the browser stops everything.
• An alert whose pop-up is turned off is not sent: it only reaches the log, and the extension's window says so.
• An alert not delivered within 5 seconds is dropped and reported, never replayed later.
• It cannot relay anything while your computer sleeps: set sleep to "Never" for the duration of your test.
• It is less reliable than TheConnector's native server-side webhook, which does not depend on any browser being open. That is why it stays scoped to testing and discovery, not live trading.

Security and permissions

The extension keeps only two settings: your webhook address and your account's access key — the same ones you already use for your MT4/MT5/cTrader connector or a native TradingView webhook. It never reads or stores a TradingView login, a broker login or any other credential. On the TradingView page it only reads the text and time of alerts, never your positions or account details.

Permissions match what it actually does: storage and alarms for its queue and scheduling, plus host access limited to tradingview.com and your TheConnector webhook host. No tabs, no notifications, no broad host access. All the code ships inside the extension package — no remote script, no eval.

The options page requires an explicit, timestamped consent before anything is sent, and the extension's window permanently reminds you this is a test/discovery tool. That reminder cannot be dismissed.

Browser compatibility

• Chrome — validated on real triggered alerts; one-click install from the Chrome Web Store, updates included
• Edge — same Chromium package, installed from that same Chrome Web Store listing
• Firefox — validated on real triggered alerts, with its own package signed by Mozilla: one click to install, and updates arrive on their own

Get it from your dashboard

TheConnector Relay is available from the downloads page of your client area (Download the robot in the menu), on every plan, including the free Basic plan. On Chrome and Edge, clicking Install opens the Chrome Web Store listing and Google keeps the extension up to date by itself afterwards; on Firefox, the Mozilla-signed package installs in one click too. If you had already loaded a copy in developer mode, remove it first: the two copies are two different extensions and would each relay the same alert, so twice. Then open the extension's options, accept the test-mode notice, paste your webhook address and access key, trigger an alert and watch it arrive in your Alert history.

The complete guide — installation on each browser, linking to your account, preparing the alert, keeping the TradingView tab from being closed and reopening everything after a restart — is at /docs/browser-extension.

One detail before you click: Tester la connexion (test the connection) checks your key without placing any order, but it counts as one alert of your daily quota and shows up as a rejected alert in your history. One test is enough.

Responsible use

TheConnector Relay reads a message TradingView already displays in a page you opened; it does not bypass any TradingView protection or change how TradingView works. Using automated tools on TradingView remains governed by TradingView's own terms of use, and stays the user's responsibility.