How to Set Up TradingView Indicator Alerts

A TradingView indicator alert is useful when its saved setup matches the chart you intend to review. An old profile, wrong interval or duplicate alert can create confusing notifications even when the indicator is working as designed. This guide provides a configuration record, an AGProLabs candidate-alert example and a troubleshooting sequence.

Configure the event before configuring the notification. Decide whether you want candidate discovery, a confirmed directional transition or a specific structural event. A chart score, a visible level and an alert event are different outputs.

1. Define the analytical event

For Crypto Setup Planner, a candidate alert directs attention to a qualifying market in the selected group. Entry, stop, target and position size remain separate. For Trading Suite, choose the particular directional, structural or portfolio event you intend to review using the conditions exposed by your installed version.

Write one sentence describing the event. For example: “Notify me when a newly qualified long candidate appears in my selected basket under the reviewed profile.” This is more useful than “notify me whenever the market is bullish,” because it identifies a transition and a defined universe.

Decide whether the event must wait for a completed candle. Check that event’s documentation; a live preview and a confirmed transition should not share an ambiguous label in your alert inventory.

2. Record the configuration that will be saved

TradingView stores a server-side copy of the script, inputs, chart symbol and timeframe when a script alert is created. Later chart or input changes do not update that running copy. Create a replacement after a relevant change. See TradingView’s alert documentation.

Before opening the alert dialog, record the installed script version, full symbol, chart interval, profile, scan timeframe, selected group, direction controls and optional pinned-symbol participation. Include the notification channel and your own alert name. Save this record beside the alert’s creation time.

On a narrow screen, swipe the table horizontally.

3. Set up a Planner candidate alert

1. Add the current accessible script to the intended chart. Verify that its panel loads without a runtime or unsupported-timeframe warning.
2. Choose one active group and the workflow profile. Review the panel’s actual source timeframe. Changing the Custom scan input does not override a preset profile.
3. Check direction controls. Review Enable Long Candidate Alerts, Enable Short Candidate Alerts and Include Pinned Symbol Alerts. Confirm which outputs you want.
4. Inspect qualification before creating the alert. Confirm that data is available and understand any Quality block. A high Score alone does not make a candidate eligible.
5. Open TradingView’s Create Alert dialog. Select this indicator instance as the condition source, then select its dynamic-call condition, displayed in English as Any alert() function call.
6. Check the displayed interval and notification settings. Use a clear inventory name such as CSP | Group 1 | Intraday 1H | Long | version, replacing “version” with your actual installed release.
7. Create the alert and retain its configuration record. Verify the saved alert’s status. Creation confirms that the setup was saved; a later log entry is separate evidence that an event actually triggered.

The dynamic-call option uses the conditions and frequency coded into the script. Individual named indicator conditions are a different alert mechanism. TradingView explains both in its indicator-alert FAQ. Choose the actual option available for your installed script rather than a similarly named price alert.

Planner candidate delivery uses completed-candle evaluation and source-clock transitions. It is not a repeating report of every row currently visible. Existing qualified rows need not produce an immediate notification when a new alert starts. Cooldown, enabled direction, pinned-symbol inclusion and qualification can also affect delivery.

4. Match the chart and source timeframe

Planner requires the chart interval to be equal to or lower than its scan interval. A 1H scan on a 5m chart still analyzes completed 1H source candles. A 4H chart with a 1H scan is unsupported; correct the interval instead of lowering quality thresholds.

The Intraday Early Warning profile has a specific 5m workflow. It requires a 5m chart and matching 5m alert interval. Its EARLY WATCH and QUALIFIED CANDIDATE controls describe different attention states; neither generates a complete trade plan.

Use the group and profile setup guide before applying the same routine to stocks, ETFs or supported custom commodity feeds. Verify sessions and source data. A closed market or unavailable feed can produce no new candidate event.

5. Replace changed configurations without confusing duplicates

Use a clear change record when updating the script, switching groups, changing a profile or revising event controls. Configure the intended chart first, create the replacement alert with a distinct name, and compare its saved details against your record.

Once the replacement configuration is verified, pause the superseded alert so two saved setups do not produce indistinguishable notifications. Retain your old configuration notes if you need an audit trail. This guide does not require deleting unrelated price or portfolio alerts.

Account alert capacity and available notification features depend on the current TradingView plan. Check the actual account interface before planning a large multi-group inventory. One selected group in a script instance does not silently monitor all other groups.

Troubleshoot from the event to the notification

1. Check the saved status. Look for an inactive, expired or errored alert before changing the indicator.
2. Check the saved configuration. Compare symbol, interval, script version, group and profile with your written record.
3. Check event eligibility. Inspect source-candle confirmation, Quality, direction controls, threshold and cooldown. A blocked candidate can correctly generate no alert.
4. Check the alert log. No recorded event and an event recorded without a device notification are different problems.
5. Check delivery settings. If the log contains the event, inspect the selected notification channel and relevant device permissions.

Do not turn off liquidity, history or structure checks simply to make notifications appear. First identify the actual missing condition. Record the full symbol, source time, event text and saved configuration when reporting a discrepancy.

Return every notification to chart review

An alert is an attention marker. Verify the current market, location, data quality and execution assumptions when you return to the chart. A notification can arrive after price has moved, and an earlier qualifying event does not establish that the present setup remains suitable.

Continue with the Planner dashboard walkthrough or the Trading Suite session worksheet. For timing differences, read the live versus confirmed-candle guide.

Review Crypto Setup Planner’s interface, supported workflow and access → Check how invite-only access works if the purchased script is not available on the intended TradingView account.