Can you use alertcondition in a TradingView strategy?

No. alertcondition() is disallowed in strategy scripts. To trigger alerts from a strategy, call the alert() function inside execution blocks or create an alert on the strategy using the "Order fills only" option in the TradingView alert dialogue.

How do I reference plot values in alertcondition messages?

Use {{plot_0}} for the first plot() statement in your script, {{plot_1}} for the second, and so on. Note that plotshape(), plotchar(), and bgcolor() do not count as plot indexes.

Why does my alert fire repeatedly on the same bar?

Your alert was configured with "Once Per Tick" or your condition evaluated true during an intra-bar spike. Guard your trigger expression with barstate.isconfirmed and configure the alert frequency to "Once Per Bar Close".

Can alertcondition send webhook JSON payloads?

Yes. You can write structured JSON strings inside the message parameter (e.g. {"action": "buy", "ticker": "{{ticker}}", "price": {{close}}}). When configuring the alert in TradingView, check the Webhook URL box.

Pine Script Alerts & Automation

Pine Script alertcondition: Complete Syntax, Placeholders, and Strategy Guide

In Pine Script, alertcondition() creates available trigger conditions in TradingViews Create Alert dialog for indicator scripts. It takes condition, title, and message arguments and supports dynamic placeholders such as {{plot_0}} and {{close}}. However, alertcondition() is strictly forbidden in strategy() scripts, where calling it causes a compiler error; strategies must use the alert() function instead.

Build Alert Scripts with AI Agent

alertcondition() syntax and parameters in Pine Script v6

The alertcondition() function enables an indicator to offer predefined alert events directly inside TradingViews native alert creation dialog. When a user right-clicks a chart and selects "Add Alert", any alertcondition registered by your script appears in the Condition dropdown menu. It requires a boolean series condition and optional display labels.

Parameter	Type	Description	Example
condition	series bool	The logical expression that triggers the alert when true	ta.crossover(fastEma, slowEma)
title	const string	The short name displayed in the TradingView alert dropdown	"Bullish Crossover"
message	const string	The default notification text or webhook JSON payload	"Buy signal triggered on {{ticker}} at {{close}}"

Dynamic message placeholders list for TradingView alerts

TradingView supports special string replacement placeholders inside the message argument of alertcondition() and alert(). When the condition triggers, TradingView replaces each token with current bar values before transmitting notifications or webhooks.

Placeholder token	Output description	Sample generated value
{{ticker}}	The exchange-qualified symbol of the current chart	NASDAQ:AAPL or BINANCE:BTCUSDT
{{close}}	The close price of the bar when the alert fired	185.42
{{open}}, {{high}}, {{low}}	Open, High, and Low prices of the triggering bar	184.20, 186.10, 183.90
{{volume}}	The trade volume recorded on the bar	4521000
{{time}}	Timestamp of the triggering bar in UTC format	2026-09-10T14:30:00Z
{{interval}}	Current chart timeframe resolution	60 or 1D
{{plot_0}}, {{plot_1}}	Numeric value of the 1st or 2nd plot() call in your script	183.15 (e.g. 20 EMA value)

Why alertcondition in strategy causes a compile error and how to fix it

One of the most frequent compiler errors encountered by Pine Script developers is "The function alertcondition cannot be called in a strategy". TradingViews compiler restricts alertcondition() strictly to indicator() scripts because strategies use a distinct order-simulation engine. To send alerts from a strategy, replace alertcondition() with the alert() function or utilize strategy alert configurations.

Pine Script v6: Correct alert() implementation inside a strategypinescript

//@version=6
strategy("Strategy Alert Master [v6]", overlay = true)

fastMa = ta.sma(close, 14)
slowMa = ta.sma(close, 28)

plot(fastMa, "Fast MA", color = color.blue)
plot(slowMa, "Slow MA", color = color.orange)

longCondition = ta.crossover(fastMa, slowMa)

if longCondition
    strategy.entry("Long", strategy.long)
    // alert() is valid inside strategy blocks; alertcondition() is not!
    alert("Strategy Long Entry executed for " + syminfo.ticker + " at " + str.tostring(close), alert.freq_once_per_bar_close)

Combining alertcondition with barstate.isconfirmed to prevent alert spam

If an alertcondition evaluates true on an unconfirmed bar, TradingView may dispatch notification emails, push notifications, or webhook payloads on every intra-bar price tick if "Once Per Bar" or "Every Tick" is selected. To protect against notification flood and false triggers, enforce bar close confirmation in your condition.

Pine Script v6: Non-spamming indicator alertcondition with barstate.isconfirmedpinescript

//@version=6
indicator("Clean Alerts [v6]", overlay = true)

rsiVal = ta.rsi(close, 14)
oversoldThreshold = input.int(30, "Oversold Level")

// Raw condition
isOversold = ta.crossunder(rsiVal, oversoldThreshold)

// Guard with barstate.isconfirmed so alert condition only fires when candle finishes
safeAlertCondition = isOversold and barstate.isconfirmed

plot(rsiVal, "RSI", color = color.purple)
hline(oversoldThreshold, "Threshold", color = color.gray)

alertcondition(safeAlertCondition, 
               title = "RSI Oversold Alert", 
               message = "RSI on {{ticker}} dropped to {{plot_0}} at close: {{close}}")

Where Pineify fits

Pine Script AI Coding Agent

Generate TradingView alertcondition scripts, fix strategy alert compilation errors, and configure webhook JSON payloads with the AI Coding Agent.

Also useful: Pine Script Error Lab. Diagnose and solve common TradingView alert errors, placeholder formatting issues, and version 6 syntax changes.

Build Alert Scripts with AI Agent

Related resources

Fix Repainting in Pine Script Convert Indicator to Strategy Combine Pine Script Indicators Pine Script Error Lab

Frequently asked questions

Technical programming documentation for Pine Script alert implementation. Network connectivity, webhook latency, and third-party alert dispatch failures can impact real-time execution timing.

Sources and verification

Last verified: 2026-09-10