You want one alert that fires when your trend filter and your momentum trigger agree. You open the alert dialog, pick the first indicator, and then look for the place to add the second one. There isn't one.
This page explains how TradingView alerts actually work, what the plan limits are, why two separate indicators cannot be AND-ed together in the alert dialog, and the four ways round it, with and without Pine Script. It is written by an indicator vendor, not by TradingView. Their help centre is the authority on their product, and their interface changes; treat this as a practical map, not documentation.
In short: a TradingView alert takes one condition from one source, so two separate indicators cannot be AND-ed together in a single alert. Four ways round it: two alerts you correlate by hand, one Pine script holding both conditions, an indicator that compounds the conditions internally, or a webhook consumer that applies the logic downstream. Trade Symbiotic, an invite-only TradingView indicator from TradeSymbiotic, a one-person company registered in the Netherlands (KvK 90052471), takes the third route: fourteen slots, seven entry and seven exit, each holding up to three conditions combined with AND, OR, 2-of-3 or a per-condition NOT, all built from dropdowns rather than Pine. The honest cost: every condition has to come from this one indicator, so it cannot AND itself with somebody else's script either. The script is published on TradingView as Trade Symbiotic - Premium, so you can check it exists before reading another line.
An alert is a condition, a trigger setting, and a notification route. The condition comes from a source you choose in a dropdown: the symbol itself (price crossing a level, a percentage move), a drawing on the chart, or an indicator loaded on that chart. When you pick an indicator as the source, the second dropdown lists only the conditions that indicator has explicitly published for alerting, plus its plotted series. That list is written by whoever coded the script. If a condition isn't in the list, no amount of clicking will produce it.
The important structural fact: the alert doesn't run in your browser. Once saved, it lives on TradingView's servers and keeps evaluating with your tab closed, your laptop shut, and your phone in a drawer. That's also why the alert is bound to the symbol and the chart timeframe it was created on, and why the notification arrives when their queue gets to it rather than the instant the bar closes.
No. A single TradingView alert reads one condition from one source, so two separate indicators cannot be AND-ed together in the alert dialog. There is no second condition row, no logic operator, no “and also” box.
That is the answer people are usually hunting for. There is no advanced tab.
The dialog isn't broken and you aren't missing a setting. Compound logic has to exist inside a script before the alert dialog can see it, or it has to be assembled somewhere downstream of the alert. Those are the only two places it can live.
Do you need Pine Script for this? You need it if you want an arbitrary combination of two arbitrary indicators; you don't if the script you're already using exposes the compounding itself. The four approaches below cover both cases, and each one costs you something.
“Can't I just fire both and eyeball it?” You can, and plenty of people do, but be clear about what you're signing up for: you become the AND operator, in real time, on whatever screen happens to be nearest. That is the first of the four, not an alternative to them.
One alert on the trend filter, one alert on the trigger, and you decide whether they landed close enough together to count. The honest cost: two notifications arriving eleven minutes apart is a judgement call, and you'll make it differently when you're tired.
Recreate or import both calculations in a single script, express the logic with and, and expose the result via alertcondition or alert(), so the logic lives in one place with nothing to correlate by hand and nothing to keep in sync. The honest cost: you now maintain code. You need the underlying logic of both indicators, which you don't have if either is closed-source, and a subtle mistake in a re-implementation is invisible until it fires on a bar it should not have.
Some scripts let you assemble conditions in their own settings and publish a single ready-made alert condition for the result, so the compounding happens inside the script and TradingView only ever sees one condition. The honest cost: you're limited to the conditions that script's author chose to expose, and you're tied to their vocabulary rather than your own.
Fire both alerts at a small service you control, hold state there, and only notify yourself when both have fired inside your window. The honest cost: you're now running infrastructure, and a server you forgot to pay for fails silently.
A free TradingView account is enough to run the indicator and set alerts. Free plans cap how many alerts can be active at once. That's TradingView's limit, not ours. Higher tiers raise the cap; the current numbers are on their pricing page and they change, so check there rather than trusting a figure on a vendor's site.
Real-time alerts require TradingView's Essential plan or higher (their requirement, not ours). On Basic, alerts can still be set with a one-bar delay. On the daily that is a long wait; on the 5-minute it is five minutes. Worth knowing before you conclude something is broken.
(Some links to TradingView on this site are affiliate links: if you create a TradingView account or subscribe through them, we may earn a commission at no additional cost to you. This never changes our pricing, and it never affects what we build or recommend. We run on the TradingView platform but are not endorsed by or sponsored by TradingView.)
Every alert can carry more than one route at once, and the routes behave differently from each other.
The webhook is the one worth setting up if you care about latency, because it goes straight to a machine instead of a human. It's also the one that fails quietly when the receiving service changes its URL format.
Usually the active-alert cap: delete or expire an old one and try again. Otherwise the source indicator isn't on the chart you're saving from, or the chart was reloaded after the dialog opened, and the alert now points at nothing.
Check the condition is actually reachable. Two conditions that are each true weekly may still never be true on the same bar. Then check the symbol and timeframe on the alert itself, not on the chart you're looking at, and check the alert's expiry date in the alert manager.
That's level mode. Many scripts expose a toggle for this. On (edge): fires only on the bar your conditions first become true. Off (level): fires on every bar the conditions stay true. If the script has no such toggle, the trigger-frequency dropdown (“Once per bar”, “Once per bar close”, “Only once”, among others) is the next place to look.
Sound plays through an open TradingView tab or the running app, not from their servers. A closed browser, a muted tab, or OS-level notification permissions are the usual three. Email and webhook keep working regardless.
Alerts can carry an expiry date, and the alert manager shows it for each one; when it passes, the alert stops. How long you get, and whether you can set an alert to run open-ended, is set by your plan, and that is TradingView's rule, not ours, so check the date on your own alert and their pricing page rather than a number on a vendor's site. An “Only once” trigger also stops the alert after the first fire, by design, and it sits in the manager until you restart it.
The alert inherited the chart timeframe it was created on. Anything the script computes from bars is computed from those bars, so the same configuration on a 5-minute chart and a 1-hour chart are two different alerts, and you need one of each.
The alert message is a template, and the placeholders inside it are only substituted if they are spelled the way TradingView expects. A misspelled placeholder is passed through as literal text rather than erroring, which is why an empty-looking Discord post is nearly always a typo in the message box rather than a fault in the indicator. Send one test alert to yourself before you point it at a webhook.
Alerts fire from TradingView's servers, so they can be delayed, duplicated, or missed. Trade Symbiotic is not an execution system, and no alert should be the only thing standing between you and an order.
We'd rather say that plainly than let you find out on a gap. Build your risk management so a missed notification costs you nothing structural.
Ours is the third approach above. Fourteen slots, seven entry and seven exit, each holding up to three conditions combined with AND, OR, 2-of-3 or a per-condition NOT, all from dropdowns, across the three tiers. One alert covers the seven entry slots, one covers the seven exit slots. Four steps:
⋯ menu) and choose Add alert on Trade Symbiotic.Re-tune the slots whenever you like, and the same two alerts reflect the change. The tiers are Ripple, Wave and Tide. Wave and Tide are rebuilt from a rolling window of your own bars, so they are a live approximation of those higher timeframes, not a copy of the higher-timeframe chart. That is what lets you watch them form; it also means they will not match a 4-hour chart tick for tick.
“I don't want a 3am buzz for a move in a session I don't trade.” Then switch on the session filter and set your hours. Outside them, nothing fires.
You are still limited to our condition vocabulary, which is the honest cost of not writing Pine. Every operand, band and preset is written up in the public documentation, and the whole catalogue is clickable in the no-account Sandbox first. The Sandbox runs on illustrative data, so it's for shaping the alert logic, not a live backtest. The script itself is publicly listed, so you can confirm it exists before you deal with us: Trade Symbiotic - Premium.
Assemble the compound condition in the Sandbox, watch it fire, and carry it across with a share code (it starts with TS1). No account, no card, and it runs the real alert engine on illustrative data, so it shapes the logic rather than proving anything about the signals. The documentation is complete and unpaywalled, so you can read the whole builder manual before paying anything, then get started when it suits you.
Two honest costs of buying, before you do. Access is granted by hand to the TradingView username you give at checkout, because TradingView gives vendors no API for it: usually within an hour or two, occasionally up to 24 hours. And nothing here is a trial run: what you get instead is a 7-day money-back guarantee, offered in addition to any statutory cancellation rights you have. Email us within 7 days of purchase for a full refund.
Assemble the conditions in the no-account Sandbox, then carry them across with a share code. The paid indicator gives you fourteen slots, seven entry and seven exit, up to three conditions each, one alert covering the entries and one covering the exits: $59 per month excluding VAT, backed by a 7-day money-back guarantee.
Decide what we may use. Strictly necessary cookies keep the site working and can't be switched off. Read our cookie policy
Security, your saved preferences, and remembering this very choice. No tracking, ever.
Privacy-friendly, aggregated usage stats so we can improve the experience. Off by default.
Measuring campaigns and tailoring offers. Off by default.