Send a TradingView alert to a MetaTrader 5 terminal
Every other broker here hands over credentials and Tradeus connects outward. MetaTrader 5 is built the other way round: nothing is collected at all — no password, no server, no investor login. You put a small program into your own terminal, and that program asks Tradeus what to do. The upside is that your broker credentials never leave your machine. The cost is on this page too, in plain words, because it is real.
Checked against Tradeus on 15 October 2026.
Before you start
- A TradingView account with 2-factor authentication enabled.
- MetaTrader 5 installed on a machine that stays on. An Expert Advisor only runs while the terminal runs — a closed lid is a stopped copier.
- MetaEditor, which ships with MetaTrader 5. You compile the program yourself, so it fails in your editor rather than silently in ours.
- A Tradeus plan that includes the TradingView webhook — Algo or Unlimited.
The numbers
- Time TradingView waits for the receiver
- 3 seconds, then the request is cancelled
- Ports it will post to
- 80 and 443 only
- IPv6
- Not supported for webhooks
- Account requirement
- 2-factor authentication must be enabled
- What MetaTrader 5 asks for
- Nothing — no password, no server, no investor login
- Which way the connection runs
- The terminal asks us; we never reach into it
- Availability
- Only while the terminal is running
- Lot rules
- Stated by your terminal, per symbol; sizing follows them
Step by step
What to do, in order.
- 1
Download the program and compile it in MetaEditor
Tradeus hands you the source rather than a binary, and you press Compile in MetaEditor yourself. That is deliberate: a program you compiled is one you could read first, and a compile error lands in front of you instead of becoming a terminal that quietly does nothing.
- 2
Allow the address in the terminal's own settings
MetaTrader 5 refuses outbound requests to any address that is not on its allow-list, and it does so silently from the program's point of view. Add the address Tradeus shows you under Tools → Options → Expert Advisors. Skipping this is the single most common reason a correctly compiled program sits there doing nothing.
- 3
Attach it to a chart and watch it report in
Drag the program onto any chart in the terminal. It starts asking Tradeus for instructions on a short timer, and the connection appears as soon as the first of those arrives. Because the asking runs one way, silence here means the terminal is not running or not allowed out — it never means "nothing to do".
- 4
Paste the URL and the ready-made message into a TradingView alert
Open the alert dialog on your chart, put the webhook URL in the Notifications tab's Webhook URL field, and paste the strategy's own alert message into the message box. Use the message Tradeus shows on the strategy rather than an example from anywhere else: it already has your passphrase filled in and it already sends the two fields that make a repeated alert harmless.
- 5
Subscribe an account to the strategy
Until an account follows the strategy, signals are recorded and nothing trades. This is the step people miss, and it is the single most common reason a first alert arrives, shows green in the event log, and moves no money. A strategy with no subscribers is a working endpoint with nowhere to send anything.
- 6
Set the size on that subscription
Size belongs to the subscription — one account following one strategy — not to the strategy. That is what lets one signal put a single contract on an evaluation and four on a funded account. Choose the alert's own quantity times a factor, a fixed number of contracts, a dollar amount of risk per trade, or a percentage of the balance.
- 7
Arm a daily loss limit before the first live signal
A daily loss limit is the cheapest insurance in the product, and the right moment to set it is before anything has traded rather than after something has. It sits on the account, so it holds whether the order came from this strategy, another one, or the copier. It is checked about every five seconds rather than before each order, so a fast market can carry the loss past it before the account is locked and its positions are closed.
- 8
Fire one alert manually and read the event log
Every signal is recorded, including the refused ones, and each refusal names its own reason — invalid passphrase, no subscription, outside the trading window, rounds to 0 contracts. Send one deliberate test alert and read what the log says about it. If the signal is not in the log at all it never arrived, which is a TradingView-side problem rather than anything to change here.
What goes wrong
Named after the message you will see.
Each of these is a line from the event log or from TradingView, written as it appears — because that is the string you will paste into a search box at the moment you need this page.
The terminal is closed, so nothing happens
An Expert Advisor runs only while MetaTrader 5 runs. Close the terminal, shut the lid, let the machine sleep, and the copier stops — without an error, because there is nothing left to report one. This is the honest cost of the shape and the reason people run the terminal on a machine that stays awake.
The address was never allowed
Tools → Options → Expert Advisors carries an allow-list, and a request to an address that is not on it is refused by the terminal itself. The program looks healthy and simply never reaches us. Check this before anything else when a freshly attached program shows no connection.
Silence is not a message
Because the terminal does the asking, Tradeus cannot tell the difference between "nothing to report" and "nobody is listening" from a single quiet moment. The connection goes stale rather than erroring. If an account stops updating, look at the terminal before looking at the strategy.
Lot sizes are the terminal's rules, not ours
Minimum lot, step and maximum differ per broker and per symbol, so the terminal states its own rules and Tradeus sizes against those rather than guessing a number that happens to work at one broker. A size that rounds to nothing is rejected in the event log instead of being sent and bounced.
“no subscription” — the alert arrived and nothing traded
The strategy received the signal and no account was following it. Open the strategy, add the account, and re-send. This accounts for more first-run confusion than every other cause put together, because the webhook itself answers perfectly well.
“invalid passphrase” after everything worked yesterday
Somebody pressed New passphrase. The old one stops working immediately and the alert in TradingView still carries it. Copy the current message off the strategy into the alert again.
“rounds to 0 contracts”
Dollar-risk sizing divided your risk budget by the stop distance and got less than one contract, and less than one contract is no trade. A wide stop with a small budget does this every time. It appears in the event log as a rejection rather than as a fill that went missing.
The webhook fires but TradingView reports a failure
Check the three things TradingView itself limits: the receiver has three seconds to answer, only ports 80 and 443 are accepted, and IPv6 is not supported. A hosted endpoint clears all three by construction; a bridge running on your own machine has to clear them itself, on your home connection, while you are asleep.
Questions
Asked before buying, answered either way.
Why does it not just ask for my MT5 login?
Because then your broker credentials would sit on somebody else's server. In this shape nothing is collected: a small program inside your own terminal asks what to do and acts there. Your login never leaves the machine it was issued to.
What happens when I close my laptop?
The copier stops. An Expert Advisor runs only while the terminal runs, and no error is raised because there is nothing left running to raise one. If you need it to keep going, the terminal has to live on a machine that stays awake.
Do I have to compile it myself?
Yes, and it takes one press in MetaEditor. You get the source rather than a binary, so you can read what you are putting in your terminal, and a compile problem appears in front of you rather than as a program that silently does nothing.
In the handbook
The reference pages behind the steps above — one thing each, in full.
- MetaTrader 5 in your terminalA small program runs in your own MT5 and reports to Tradeus. No password leaves your machine — and copying stops when the machine does.
- Which brokers workSix you can connect today, what each one asks for, and which of them copy a trade you place by hand.
- Position sizeFour methods, set per account and not per strategy.
- Accounts and what their status meansSix states, which of them stop trading, and how to file, name and flatten your accounts.
Sources
Every claim above about somebody else's product, linked to the page it was read from. If one of them no longer says what this page says, this page is wrong and we want to know: tell us.
Checked against the live product on 15 October 2026. Broker screens and TradingView's own limits change; a step that no longer matches what you see is a step we need to fix.
Next
The neighbouring jobs.
Weighing this against another tool? All 7 compared, every row linked to the page it was read from.
The only step this page cannot do.
Everything above is mechanical and takes about ten minutes. Whether it behaves the way you expect on your own accounts is the part nobody can write down for you.