TradingView Alerts
Turn a compatible TradingView alert into a defined MT5 workflow.
Atlas can receive a compatible TradingView alert and pass it to the copier using your selected channel policy. The direct route does not wait for a Telegram message; optional result notifications are handled separately.
Check what the indicator actually sends
An indicator's display and its alert can contain different information. Start by checking the direction, symbol, entry and required stop or target values in the actual alert. A visible setting alone does not establish that the alert includes its price.
- Use an indicator output or alert condition that explicitly identifies the intended direction.
- Keep each source distinct when several indicators share a symbol and timeframe.
- Recreate relevant alerts when their indicator or connector settings change.
Apply the policy you selected
The direct route uses an enabled channel policy for sizing, target allocation, protection and limits. The selected account and trading worker must be ready. Receiving an alert does not override a pause, an account mismatch or an invalid price.
- Choose a single target or supported allocation across the supplied targets.
- Review the total signal size before splitting it into positions.
- Check the processing result and broker confirmation separately from notification delivery.
Match the route to the available data
A complete, compatible alert can use the documented direct workflow. If required prices exist only on the chart, the native reader route still needs qualification. If the source has no such prices, an explicit, qualified exit policy is needed before use.
- Atlas does not infer a protected indicator's logic from its name.
- Old events are not replayed to compensate for downtime.
- TradingView alert permissions and broker symbol compatibility remain setup requirements.
FAQ
Is Telegram required for the direct TradingView route?
The direct route passes an alert to the copier without waiting for a Telegram channel message. It still uses a selected, enabled channel policy. Optional Telegram result notifications have their own access requirements and do not determine the broker outcome.
Does every TradingView indicator work with Atlas?
No. The indicator must expose compatible alert information or a supported output. Source rights, direction, prices and identity need review. A private indicator with incomplete alerts may depend on the reader route, which is still being qualified.
Does alert acceptance mean a trade was opened?
No. Acceptance means the event entered processing. The account, current prices, policy and broker checks still apply. Use the copier result and broker position confirmation to determine the trading outcome.
Can I distribute one signal across several targets?
Supported target allocation can divide the total signal size across supplied targets. Each part must satisfy the broker's minimum volume, volume step and your position limits. Atlas does not increase your selected size to force an invalid split through.
Continue exploring
Start with the right setup.
Review your source, account and requirements before choosing a solution.