Trade with the trend, not against it.
A TradingView trend filter blocks signals that fight the market. SignalForge Auto-Trend adds multi-timeframe confirmation to any alert with just {{interval}}. This guide explains why trading with the trend matters and how to set it up step by step.
The usual approach vs. SignalForge.
The usual way to handle trend and signals requires two alerts per symbol: one for trading and another to update direction with role:"trend". Auto-Trend needs only one webhook message, because the timeframe itself tells the server what to do.
- Duplicate alert logic in TradingView
- Manual
role:"trend"field - Easy to mismatch timeframes
- More webhook messages to debug
{{interval}} decides the routing- Same alert fires signals and trend updates
- No manual role or layer index
- Timeframe match is automatic
- Less noise, fewer mistakes
Why a trend filter pays.
Most losing trades share one trait: they fight the prevailing move. A trend filter removes those entries before they reach MetaTrader 5, so you only take signals that align with the market.
- Fewer false breakouts. Counter-trend entries look tempting but fail more often.
- Better risk/reward. Entries with the move have more room to run.
- Less emotion. The filter decides, not your gut, after three consecutive losses.
- Clear rules. Every active layer must agree before a signal becomes a trade.
Pick your trend timeframes.
Open the Trend Filter section in the Trader Dashboard. For each symbol you trade, choose up to three timeframes that define your directional bias.
- Layer 1: usually the entry chart (e.g., M15).
- Layer 2: a higher confirmation (e.g., H1).
- Layer 3: the macro bias (e.g., H4 or D1).
You do not have to use all three. One layer is enough to start; two or three layers make the filter stricter. The server only requires that every active layer agrees before a signal becomes a buy or sell.
Match the timeframes to the ones you already watch in TradingView. If your strategy looks at H1 and H4, set those two layers. Keep Layer 3 off until you need it.
Add {{interval}} to your alert.
In TradingView, open the alert dialog for your strategy or indicator. In the Message field, include the {{interval}} placeholder wherever you want. SignalForge will receive the current chart timeframe when the alert fires.
Valid examples:
The placeholder works on every TradingView plan, including free accounts. It returns values like 15m, 1h, 4h or 1D, which SignalForge normalizes automatically.
How the server decides.
When the webhook arrives, SignalForge parses the interval and checks it against the trend layers you configured for that symbol.
- Match found: the alert updates that layer's direction. It is treated as a trend update, not a trading signal.
- No match: the alert is treated as a trading signal. The server checks all active layers, and only forwards the order if every layer agrees.
This means you can fire the same alert from multiple timeframes. A M15 alert may execute a trade; an H1 alert from the same strategy may only update Layer 2. The server separates them automatically.
Enable the trend filter in MT5.
In the SignalForge EA inputs, turn on the Trend Filter. The EA reads the active layers from your account and blocks any signal that disagrees with the current bias.
- Trend Filter: On/Off.
- Action on mismatch: choose Close to exit opposing positions, or Block to ignore the signal.
- Symbol matching: layers are stored per symbol, so EURUSD layers do not affect GBPUSD.
You do not need to hardcode timeframes in the EA. The layers come from the dashboard, and the interval comes from TradingView. Changing your bias is now a dashboard action, not a code change.
Check the dashboard.
After a few alerts fire, open the Trader Dashboard to confirm everything is routing correctly.
- Trend layers show the right direction for each timeframe.
- Signals received from non-trend timeframes appear in the signal log.
- Blocked signals show a trend-mismatch reason.
- Telegram notifications fire when a layer flips.
If a layer is not updating, verify that the alert interval matches exactly. TradingView sends 15m for a 15-minute chart, and the dashboard expects the canonical form M15. SignalForge normalizes common formats, but the configured layer must represent the same timeframe.
Stack it with the News Filter.
Trend and news are two independent filters. A signal can have trend approval and still be blocked if a high-impact event is about to hit. Using both together protects you from two different types of risk:
- Trend Filter: blocks entries against the higher-timeframe bias.
- News Filter: pauses entries around events like NFP, CPI or FOMC.
In the dashboard, set the minutes before and after each event, the impact level to watch, and whether to close opposing positions. The EA applies both filters automatically.
Start with the Trend Filter. Once it is stable, add the News Filter for event risk. The two filters do not overlap: one handles direction, the other handles timing.
Quick questions.
Email [email protected] if yours isn't here.
Let the timeframe do the work.
Auto-Trend turns a single TradingView alert into both your trend engine and your signal source. Configure your layers, add {{interval}}, and the server handles the rest. No dual alerts, no manual routing, fewer mistakes.
Trade with the trend.
Multi-timeframe confirmation for your TradingView → MT5 bridge. One alert, automatic routing.