Full Alert Setup Guide
From a fresh account to a live automated trade. Every step, every setting that matters, and the mistakes that cause most failed alerts.
On this page
Before you start
You need three things in place. None of them take long, but skipping the TradingView plan check is the most common way to get stuck at the last step.
A supported broker account
Futures: Tradovate, ProjectX (TopstepX), Rithmic, or NinjaTrader 8. Forex and CFDs: TradeLocker, cTrader, or MT4/MT5. Crypto: Coinbase, Bitunix, or DXtrade. Prop firm accounts connect through whichever of these platforms your firm issues.
A TradingView plan with webhooks
Webhook alerts start at Essential, TradingView's entry paid tier. Any plan above it works too. Webhooks are not available on the free Basic plan.
A strategy or indicator that fires alerts
Anything that can fire a TradingView alert works. If your strategy emits its own JSON through alert() calls, Ghost accepts it directly.
Step 1. Connect your broker
Open Ghost settings and pick your broker
Go to Ghost, then Settings, then the Brokers tab. Each broker has its own connection method:
| Broker | Market | How you connect |
|---|---|---|
| Tradovate | Futures | OAuth login, with a prop firm or personal account toggle |
| ProjectX (TopstepX) | Futures | API key and username |
| Rithmic | Futures | Select your system, then username and password |
| NinjaTrader 8 | Futures | Free NinjaTrader add-on, paired with a one-time connection key |
| TradeLocker | Forex and CFDs | Email, password, and server name |
| cTrader | Forex and CFDs | OAuth login |
| MT4/MT5 | Forex and CFDs | Expert Advisor in your MetaTrader terminal, paired with a one-time connection key |
| Coinbase | Crypto | API key |
| Bitunix | Crypto | API key and secret |
| DXtrade | Crypto prop firms | Username, password, and your firm's DXtrade server |
Choose the right account type on Tradovate
Tradovate asks whether this is a prop firm account or a personal live account, and it matters: prop firm accounts and personal accounts live on different Tradovate infrastructure. Most users here are on prop firm accounts, which is the default. Pick wrong and your accounts list comes back empty or shows the wrong accounts.
You can connect more than one Tradovate login, which is how traders with accounts at several firms run them all from one Ghost account.
Confirm your accounts appear
After connecting, your accounts should be listed under that broker. Use Refresh from Broker if a newly funded account is missing. You can give any account a nickname so the dashboard reads like your fleet rather than a list of numbers.
Step 2. Add a ticker
A ticker in Ghost is one automated configuration: a symbol, its risk settings, its account routing, and its own webhook URL. Go to Ghost, then Tickers, then add the symbol you want to trade.
Give it a strategy name if you plan to run more than one system on the same symbol. The name is what separatesMNQ running your ORB strategy from MNQ running a mean reversion system, each with its own webhook and its own settings.
Tickers are grouped by market category automatically. You can also create named groups to organize a large list.
Step 3. Configure size, stop, and target
These settings decide what actually gets sent to your broker. The stop and target are sent with the entry as a native bracket order, so they live at the broker rather than depending on anything staying online.
| Setting | What it does |
|---|---|
| Contracts | Position size for this ticker. Forex and crypto accept decimals for lots and units. |
| Use Stop Loss and Take Profit | Master switch. When on, Ghost calculates the stop and target and sends them to the broker with the entry. When off, no stop or target is sent or recorded at all. |
| SL points / TP points | Distance from entry, in points, for the stop and the target. |
| Pips mode | Forex pairs only. Enter the stop and target in pips instead of price distance. JPY pairs are handled correctly. |
| Use Webhook SL/TP | Lets the sl and tp values in your alert override the configured distances. Requires Use Stop Loss and Take Profit to be on. |
| Webhook Controls Contracts | Lets qty in your alert override the configured size. |
| No Take Profit | Sends the stop but no target, for strategies that let winners run and exit on their own signal. |
Turning off Use Stop Loss and Take Profit means no stop
With that switch off, Ghost sends a bare entry with no protective order at the broker. That is a legitimate choice for strategies that manage their own exits, but it is not a default worth drifting into. If you want a stop, leave it on.
Step 4. Select accounts
Open the ticker settings and choose which broker accounts this ticker trades. Selecting nothing means the alert has nowhere to go, which is a common cause of a signal that logs but never fills.
Turn on Copy Trader for that ticker to select several accounts at once, including accounts at different brokers. One incoming alert then fans out to every selected account, and each account result is recorded separately in your logs.
There is no per account charge, so a fleet of prop accounts costs the same as one.
Step 5. Copy your webhook URL
Each ticker has its own webhook URL with a secret embedded in it. Copy the whole thing from the ticker settings, exactly as shown. It looks like this:
https://quantcrawler.com/api/ghost/webhook/<ticker-id>?secret=<your-secret>Copy the whole URL, including the secret
The part after ?secret= is what authenticates the alert. Without it, or with it truncated, Ghost rejects the request and nothing trades. Do not paste the symbol name into the URL: the path segment is the ticker ID, not the ticker symbol.
Treat the URL like a password. Anyone who has it can send signals to that ticker. Ghost has a privacy mode that masks secrets on screen if you record or stream your desktop.
Step 6. Build the TradingView alert
Create the alert on your strategy or indicator
In TradingView, open your chart, click the alarm clock icon, and set the condition to your strategy or indicator.
Set the condition to alert() function calls only
This is the setting that causes more failed setups than anything else. When your strategy emits JSON through alert() calls, choose alert() function calls only. If you leave it on order fills, TradingView sends its own description of the fill instead of your JSON, and Ghost rejects it because there is no action in the message.
Paste the webhook URL
Open the Notifications tab of the alert dialog, tick Webhook URL, and paste the full URL from step 5.
Write the message body as JSON
The Message box is what Ghost receives. It has to be valid JSON. The simplest working pair of alerts is an entry and an exit:
{"action":"buy","price":{{close}}}{"action":"exit"}Ghost also has an Alert Message Builder in the ticker settings that writes these for you, including versions with stop and target values.
The number one cause of rejected alerts
A message body that is not JSON. TradingView's default alert text (something like "Order buy @ 1 filled on MNQ") is not JSON, so Ghost has no action to read and rejects it. Set the alert to alert() function calls only, and make sure the Message box contains your JSON rather than the default template.
Step 7. Test before going live
Do not let a real fill be the first proof that your wiring works. There are three ways to check, from safest to most complete.
Demo Mode
In Ghost settings, turn on Demo Mode. Signals are fully processed and appear in your logs, but nothing reaches the broker. This proves the alert arrives, authenticates, and is interpreted the way you expect.
The Test Webhook button
Ticker settings has a test button that sends a sample signal to your own webhook so you can confirm the plumbing without touching TradingView.
Per signal dry run
Adding "test":true to a payload runs the entire validation pipeline, including your stop and target maths, and logs exactly what would have been sent, without contacting the broker. The rest of your automation keeps trading normally.
{"action":"buy","price":{{close}},"test":true}Step 8. Turn Ghost on and monitor
Ghost has a master switch on the dashboard. While it is off, nothing executes, including exits. Turn it on when your ticker is configured and tested.
For the first live session, keep two pages handy. The Dashboard shows open positions with live profit and loss, and the Logs page shows every signal that arrived and what Ghost did with it. If something looks wrong, the log row has the exact payload that was received.
Turn on push notifications for entries, exits, and order failures so you find out about a problem without watching a screen.
Optional controls worth setting
None of these are required to place a trade, but each one removes a way for an automated system to hurt you while you are not watching.
| Control | Where | Why you want it |
|---|---|---|
| Daily Loss Limit | Settings, General | Optional. Blocks new entries once broker-confirmed realized losses hit your number, until the 5:00 PM ET session reset. Ghost stays on and exits are never blocked. |
| Trading Hours | Ticker settings | Up to three windows in Eastern time. Alerts outside them are logged and skipped. |
| Session Close | Ticker settings | Flattens that ticker at a set time, which matters if your firm requires you flat before the close. |
| Max Daily Trades | Ticker settings | Caps entries per day, which contains a misbehaving strategy. |
| Direction Filter | Ticker settings | Long only or short only, if you only trust one side of a system. |
Troubleshooting
| What you see | What it means and how to fix it |
|---|---|
| Nothing in Logs at all | The request never reached Ghost. Re-copy the full webhook URL including the secret, and confirm the alert is actually firing in TradingView. |
| Missing action | The message body was not JSON. Set the alert to alert() function calls only and put JSON in the Message box. |
| Literal placeholder text received | An indicator alert used strategy placeholders. Use a strategy alert, or hardcode the action. |
| Signal rejected, missing entry price | Entries need a price. Add "price":{{close}} to the payload. |
| Invalid authentication | The secret is wrong or truncated. Copy the URL again. |
| Ticker not found | The URL contains a symbol instead of the ticker ID. Copy the URL from the ticker settings rather than typing it. |
| Signal logged but no order | Usually Ghost is stopped, Demo Mode is on, no accounts are selected on the ticker, the alert arrived outside your trading windows, or a daily limit is active. The log row names which one. |
| Duplicate detected | An identical signal arrived within sixty seconds and was ignored on purpose, which protects you from TradingView retries. |
Failed rows on the Logs page have a Diagnose with AI button that reads the actual payload and explains the failure in plain language.
Frequently Asked Questions
Which TradingView plan do I need?
Any paid plan. Webhook alerts start at Essential, TradingView's entry paid tier, so you do not need one of their higher plans to automate with Ghost. Webhooks are not available on the free Basic plan.
Should I use a strategy or an indicator alert?
Either works, but they behave differently. A strategy can use alert() calls to emit exact JSON, which is the most reliable setup. An indicator can also fire alerts, but it cannot use strategy placeholders such as strategy.order.action, so hardcode the action in the message instead.
Can one ticker receive alerts from more than one strategy?
It can, but it is usually better to create a separate ticker with its own strategy name for each strategy. Each ticker gets its own webhook URL, its own sizing, and its own risk settings, which keeps the logs readable and stops two strategies fighting over one position.
How do I test without risking money?
Turn on Demo Mode in Ghost settings. Signals are fully processed and logged but no orders reach the broker. You can also add "test":true to a single alert payload to dry run just that one alert while the rest of your automation stays live.
Why did my first alert do nothing?
Check the Logs page in Ghost. If no row appeared, TradingView did not reach Ghost, which is almost always a wrong or missing secret in the webhook URL. If a row appeared with a rejection reason, the reason names the fix. The most common one is a message body that is not JSON.
Does the webhook URL expire?
No. The URL and secret stay valid for the life of the ticker. If you ever need to invalidate one, delete the ticker and create a new one, which issues a new URL and secret.
Continue Learning
Risk Disclosure: Trading involves substantial risk of loss and is not suitable for all investors. This content is for educational purposes only and does not constitute financial advice.
Last updated: November 2026