TradingView Alert Presets: What They Save, and Why You Still Enter the Webhook URL

TradingView alert presets save most of an alert's setup as a reusable template, but not the Webhook URL. Since 29 January 2026, you can store up to five presets holding conditions, trigger frequency, expiry, the alert name and message template, and your notification choices. TradingView's Help Center states plainly that "Webhook URLs are NOT saved in presets", and that value fields and drawing-tool conditions are not saved either.

For an alert that sends instructions to PineConnector, that has two consequences. An alert created from a preset reaches PineConnector only after you tick Webhook URL and paste the address again. And the saved message template travels unchanged, so a License ID, symbol or trade size typed into it goes to every chart you apply the preset to. This guide lists what a preset carries, what you still enter, and a check to run before you press Create.

What changed

TradingView announced alert presets on 29 January 2026 (the post was last updated on 25 March 2026)^[1]. Before that, every alert was configured from scratch in the alert dialog. Now you configure an alert once, click the preset button next to the close (✕) button and choose Save alert preset. You name the preset and pick which settings it keeps; if you tick none, the Help Center says every setting is saved^[2].

Later, you open the create-alert dialog, pick the preset from the dropdown, and the applied preset is highlighted. Reset changes returns the dialog to the settings it had when you opened it. Three limits apply^[2]:

• You can keep up to five presets.
• "You cannot edit an already created preset." To change one, delete it with the bin icon and save a new one.
• Deleting a preset is permanent.

What a preset saves, and what it leaves out

The Help Center's list is more detailed than the announcement^[2]. Notification schedules, added in July 2026, can also be included by ticking their box when you save the preset^[3].

Setting	Saved?	What to do
Condition structure and timeframe	Yes	Check it suits this chart
Value fields, such as a price	No	Enter the value each time
Drawing-tool conditions	No	Create them from the drawing
Trigger frequency	Yes	Match it to the message
Expiration	As a period	Check the new expiry date
Alert name	If changed	Rename each alert
Message template	If changed	Read every field again
App, toast, email, sound, plain text	Yes	No action
Webhook URL	No	Tick it and paste the address
Notification schedule	If ticked	Check it is 24/7

Three rows deserve a note. The condition structure covers the series, plot, operator, bands and timeframe, so a preset for "price crossing 1.0850" comes back without 1.0850. Expiry is stored as a period (the gap between the earliest date the dialog allows and the date you picked) or as open-ended, so each new alert gets its own expiry date rather than the original one^[2]. And the name and message are saved only when they differ from TradingView's defaults. A message typed for PineConnector differs from the default, so it is saved word for word whenever the message setting is included. Scripts that build their message with alert() keep it in the script rather than in the Message template^[6].

Why the missing Webhook URL matters for PineConnector

PineConnector receives TradingView alerts through the webhook. TradingView sends a POST request to the address you enter, with the alert message as the body of the request^[4]. Without the address, the alert can trigger, appear in the Alerts log and ping your phone, while PineConnector receives nothing.

The announcement says the same thing: a preset keeps every preference from the Notifications tab apart from the Webhook URL^[1]. Neither page says whether the Webhook URL box stays ticked when a preset is applied, so check both the tick and the address. PineConnector's address is https://webhook.pineconnector.com, entered in the Webhook URL field, not in the message^[8]. TradingView allows webhook alerts only when two-factor authentication is enabled^[4].

The message template goes wherever you apply the preset

Because the message is saved as text, a preset repeats every detail you typed into it. The example below illustrates that risk; it is not a template to copy. Suppose you built a preset on a EURUSD chart with this message:

LicenseID,buy,EURUSD,vol_lots=0.01,sl_pips=20

A week later you apply the preset to a gold chart. The condition now watches gold, but the message still says EURUSD, 0.01 lots and a 20-pip stop. When the alert triggers, PineConnector is asked to buy EURUSD. Three parts of a saved message need a fresh look on each chart:

• License ID. PineConnector's Syntax reference notes that "One ID can address several accounts"^[5]. A preset built while testing on demo carries the demo ID, and one built for a live connection carries that ID into every test.
• Symbol. The message needs the exact broker symbol. TradingView's {{ticker}} placeholder inserts the chart's ticker, and PineConnector's guide says to use it "only when TradingView’s ticker matches your broker’s symbol"^[6].
• Size and stops. PineConnector defines a pip as 10 symbol quoting points, and its Syntax reference warns that "The same 20 pips can mean a different distance"^[5]. In its own examples, sl_pips=20 is 0.00200 on a five-decimal EURUSD quote but 2.00 on a two-decimal gold quote.

If Signal Authentication is on, the message also carries your secret= value. PineConnector's guide warns that changing the key in Portal does not change the key inside your TradingView alerts^[9], and a preset saved with the old key keeps it too. Signal Authentication is a PineConnector Plus and Pro feature.

If your connection runs on PineConnector Edge, the hosted EA currently uses fixed default settings^[10]. Write size and stops with explicit units such as vol_lots= and sl_pips=, as PineConnector recommends for new messages, rather than relying on a legacy parameter whose meaning comes from EA settings^[5].

A preset can bring a notification schedule with it

When a preset includes a notification schedule, applying it sets those active hours on the new alert along with its conditions and triggers^[3]. Outside those hours TradingView logs triggers but blocks every notification channel, including the webhook. A preset saved for manual alerts with "Standard working hours" can quietly give an automated alert the same window. The full behaviour is in TradingView notification schedules: why an alert can fire without sending its webhook.

Limitations and common mistakes

• Treating the preset as the alert. TradingView describes presets as templates applied when you create an alert. Neither page describes a change to a preset reaching alerts already created from it, so check each running alert on its own.
• Expecting a script change to reach alerts already created. An alert keeps the script and inputs it was created with. After changing a script, recreate the alert, as explained in why an alert still uses old Pine Script settings.
• Saving everything by default. If you tick no boxes, every setting is saved. Decide whether the message template should be part of a preset used across different symbols.
• Using a preset for a price or drawing alert. The price level and the drawing are not saved, so the condition is incomplete until you add them.
• Same name on every alert. A saved name repeats. PineConnector's best-practice guide suggests naming each alert after its script, symbol, timeframe and intended destination^[7].

Check before you press Create

Run this on every alert created from a preset that will send to PineConnector:

1. Condition. The symbol and timeframe are the ones you mean. Enter any value field again, and create drawing alerts from the drawing itself.
2. Frequency and expiry. The trigger frequency suits the message, and the expiry date shown is sensible for this alert.
3. Message. Read the whole message in TradingView's Message field: License ID for the intended connection, exact broker symbol, explicit size and stop values that suit this instrument, and secret= if authentication is on. The format is LicenseID,Command,Symbol,Parameters^[5].
4. Webhook. Webhook URL is ticked and the address is exactly https://webhook.pineconnector.com.
5. Schedule. The notification schedule is 24/7, unless a narrower window is deliberate and also covers the exits.
6. Name. The alert has its own name, showing the script, symbol, timeframe and destination.
7. Test. Create the alert once, then follow PineConnector's demo test workflow. Confirm the trigger in the TradingView Alerts log and the processing result in PineConnector's Bridge. Then check in the broker account whether the order was accepted, whether a deal filled it and what position resulted^[8]. A received signal is not proof of a broker fill, and an accepted order is not a fill either.

Reviewed 23 September 2026. Facts were checked against the linked sources on that date. No preset was created in a TradingView account for this article; the saved and not-saved lists come from TradingView's documentation, and the message shown illustrates a risk; it is not a template or a tested trade.

Related reading

• TradingView updates for alert-based automation: a practical index
• TradingView notification schedules: why an alert can fire without sending its webhook
• How to set up TradingView webhook alerts
• TradingView alert syntax: format messages for automation
• I changed my Pine Script, but the alert still uses the old settings

Sources

1. TradingView Blog – Speed up your workflow with alert presets, published 29 January 2026, updated 25 March 2026, accessed 23 September 2026.
2. TradingView Help Center – Alert presets, accessed 23 September 2026.
3. TradingView Help Center – Notification schedule for alerts, accessed 23 September 2026.
4. TradingView Help Center – How to configure webhook alerts, accessed 23 September 2026.
5. PineConnector Docs – PineConnector Syntax, accessed 23 September 2026.
6. PineConnector Docs – Connect your strategy, accessed 23 September 2026.
7. PineConnector Docs – Best Practices & Tips, accessed 23 September 2026.
8. PineConnector Docs – Test your setup, accessed 23 September 2026.
9. PineConnector Docs – Protect signals with a secret key, accessed 23 September 2026.
10. PineConnector Docs – Connect your MT5 account (Edge), accessed 23 September 2026.

PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.