Turning signals into a filter
A single indicator fires often and is often wrong. These entry controls decide how much agreement a trade needs before it opens — and how to safely accept a signal from outside the platform.
Consensus and confirmation
- •N-of-M consensus — require N of your M indicators to agree before entering. A higher N is stricter: fewer entries, higher conviction.
- •Confirmation bars — require the signal to hold for N bars, filtering one-candle flukes.
- •AND/OR builder — combine indicators in AND blocks (all must hold) and OR blocks (any one suffices), for logic beyond “all at once.”
- •Cross-system signals — trigger a trade from another system’s event, chaining systems into one strategy.
The TradingView webhook — and its guards
You can open or close on an external signal from TradingView. Because that signal comes from the open internet, use the guards:
- •HMAC signature — verifies each webhook against a secret and rejects forged requests. Essential if the URL could ever leak.
- •Max lag — reject a signal that arrives too late to be valid.
- •Max price deviation — reject if price has already moved too far from where the signal fired.
- •Cooldown — a minimum gap between triggers, so a noisy feed can’t spam entries.
The pitfall
An unguarded webhook is both a security hole and a slippage trap. Without HMAC, anyone who finds the URL can trigger trades on your account; without the lag, deviation and cooldown guards, a delayed or duplicated alert fires at a bad price. Turn on the signature and all three guards before you trust an external feed.
Next
Learn the filters themselves in Indicators, and see why the deterministic Risk Gate still has the final say on going live.