MSLSI — TradingView Alert Setup Guide
Created by Nouman Ahmed (ahmednouman188@[Link]) For: Phase 3 Trading —
Miss Rissa Version: Compatible with Indicator v8.6.4+ and Scanner v3.9+
Overview
This guide walks you through setting up TradingView alerts that send signals from the
MSLSI indicator to your private scanner dashboard. Once configured, every signal that fires
on your chart will automatically deliver to your subscribed Discord channels and Telegram
users.
Prerequisites
Before you start, make sure you have:
1. TradingView Premium subscription ($49.95/month or higher) — webhooks
require a paid plan
2. MSLSI Indicator v8.6.4 added to your TradingView account (Pine Script saved and
added to a chart)
3. Scanner running at your server URL (currently [Link]
4. Webhook secret if your scanner has one configured (check SETTINGS tab in
dashboard)
Part 1 — Configure the Indicator for Alerts
Step 1: Open the indicator settings
1. Open your TradingView chart with the MSLSI indicator
2. Click the settings cog (⚙️) next to ◆ MSLSI v8.6.x in the indicator name
3. The settings panel opens
Step 2: Enable the signals you want to alert on
The indicator has many toggleable features. Make sure these are configured the way you
want BEFORE creating alerts, because alert behavior follows your settings.
Required for alerts to fire:
Section Setting Recommendation
Inputs ID (Inside Day) ON if you want Inside Day
signals
Section Setting Recommendation
Inputs OD (Outside Day) ON if you want Outside Day
signals
Inputs CIB Up / CIB Down ON for CIB signals
Inputs 3DL / 3DS ON for 3-Day Long/Short
signals
Inputs FRD / FGD ON for First Red/Green Day
signals
Trap Detection Enable Trap Detection ON for trap signals (the ⭐
system)
Round Numbers 00’s, 25/75’s, 50’s toggles ON if you want round-
number-based traps
Step 3: Configure trap tier filtering
In the Trap Detection group, you can filter which trap tiers generate alerts.
• Show trap labels at all tiers — visual labels on the chart
• The scanner’s MIN TIER setting controls which traps DELIVER to subscribers
• This means a 3⭐ trap will fire and appear on your chart, but if the scanner’s MIN
TIER is set to 4, only 4⭐ and 5⭐ traps will be sent to your community
Step 4: Save your settings
Click Defaults → Save as Default at the bottom of the settings panel. This locks in your
configuration so all future chart applications use these settings.
Part 2 — Create a TradingView Alert
This is where most setup errors happen. Follow each step carefully.
Step 1: Right-click your chart and select Add Alert
Or use the keyboard shortcut Alt+A (Windows) / Option+A (Mac).
Step 2: Configure the Condition
In the alert dialog box:
1. Condition dropdown: Select ◆ MSLSI v8.6.x
2. Sub-condition dropdown: Select Any alert() function call
⚠️Important: Do NOT pick individual alert conditions like “Bull Trap” or “CIB Up”. The
MSLSI indicator uses a unified alert() system. Picking individual conditions only delivers
ONE signal type and misses others.
Step 3: Configure Alert Settings
Field Value Notes
Alert name MSLSI [SYMBOL] (e.g., For your reference
MSLSI NAS100)
Trigger Once Per Bar Close Required — fires only after
the bar closes
Expiration Open-ended Alert never expires (no end
date)
⚠️Critical: “Once Per Bar Close” is mandatory. If you select “Once Per Bar” instead, alerts
may fire multiple times per bar and produce duplicate signals.
Step 4: Configure the Notification
This is where the alert connects to your scanner.
1. Scroll down to the Notifications section
2. Webhook URL → Toggle ON
3. Enter your webhook URL:
[Link]
4. Message → Paste this exact template:
{{alert_message}}
That’s it. The indicator generates the full JSON payload internally — TradingView
just relays it through {{alert_message}}.
Step 5: Click Create
Your alert is now active. The next time a signal fires, it will be delivered to your scanner.
Part 3 — Set Up Alerts for Multiple Tickers
If you want to track signals across multiple instruments (NAS100, US30, XAUUSD, etc.), you
need ONE alert per ticker.
The Right Way
1. Open chart for NAS100
2. Apply the MSLSI indicator
3. Create an alert (follow Part 2)
4. Switch the chart to US30
5. Make sure MSLSI indicator is applied
6. Create a NEW alert (follow Part 2 again)
7. Repeat for each ticker you want to track
The Wrong Way
❌ Do not try to put multiple symbols in one alert — TradingView only sends signals for the
ticker the alert is created on.
How Many Alerts Can I Have?
TradingView limits depend on your subscription: - Pro: 20 active alerts - Pro+: 100 active
alerts - Premium: 400 active alerts
Each ticker uses 1 alert slot. If you track 30 instruments, you need at least Pro+ tier.
Part 4 — Verify Alerts Are Working
Test 1: Check the alert status
1. Open the Alerts panel in TradingView (bell icon in the right sidebar)
2. Your MSLSI [SYMBOL] alerts should appear with a green dot (active)
3. If you see a red dot, the alert is paused or expired — click to reactivate
Test 2: Check the scanner dashboard
1. Open your dashboard: [Link]
2. Go to the SIGNALS tab
3. Recent signals should appear here as they fire
Test 3: Trigger a manual test
You can manually fire a test signal using PowerShell or terminal:
curl -X POST [Link] \
-H "Content-Type: application/json" \
-d
'{"ticker":"NAS100","timeframe":"15","signal_code":"CIB_LONG","signal_
name":"CIB Long","side":"BUY","tier":0,"price":29000,"session":"NEW
YORK","source":"manual_test"}'
If you see the test signal in your SIGNALS tab, the webhook is working correctly.
Part 5 — Troubleshooting
Problem: “Delivery failed” error in TradingView
This is cosmetic only — TradingView displays this when the webhook responds with
anything other than HTTP 200. Your signals are actually being received and processed
correctly. Verify by checking the SIGNALS tab in your dashboard.
Problem: Alerts fire but no signals appear in dashboard
Causes: 1. Webhook URL has a typo — must be exactly
[Link] 2. Message field is wrong — must be exactly
{{alert_message}} 3. Server is down — check [Link] opens
Fix: Recreate the alert following Part 2 carefully.
Problem: I see signals on the chart but they don’t fire alerts
Cause: The alert was created with the wrong “Sub-condition”. You picked an individual
condition like “Bull Trap” instead of “Any alert() function call”.
Fix: Delete the alert and create a new one with sub-condition = “Any alert() function call”.
Problem: Same signal appears multiple times in dashboard
Causes: 1. You have multiple TradingView accounts/devices firing the same alert 2. Alert
trigger is set to “Once Per Bar” instead of “Once Per Bar Close”
Fix: Use deduplication settings in the scanner (SETTINGS tab → Signal Deduplication → ON,
cooldown 30 min). This silently suppresses repeated identical signals.
Problem: Latest signal on chart shows BUY but screener panel shows SELL
This is normal and expected behavior. Here’s why:
The chart labels show the most recent BUY or SELL signal at that price area. The screener
panel (the right-side table showing all tickers) shows the CURRENT bias based on the
latest higher-timeframe context — which may differ from a fresh intraday trap signal.
Example: - Daily bias on NAS100 is bearish (PDC below opening price, etc.) → screener
shows “SELL” - A 15-minute Bull Trap fires → chart shows “BUY” label - These are not
conflicting — the BUY is a short-term counter-trend trade, the SELL is the daily bias
If you want them to match exactly, you can: - Disable trap detection on lower timeframes -
Or only follow signals at one specific timeframe
This is intentional design — different timeframes give different signals.
Problem: I changed indicator settings but old signals don’t reflect those changes
The scanner stores signals as they were received when the alert fired. Changing indicator
settings later does NOT update historical signal data — it only affects signals going
forward.
If you want to test new settings: 1. Update the indicator settings 2. Wait for new signals to
fire under the new settings 3. Use the PERFORMANCE tab to compare old vs new signal
performance
Part 6 — Webhook Security (Optional but Recommended)
If your scanner has webhook security enabled (set in SETTINGS tab → “Shared webhook
secret”), all alerts must include the secret in the request.
When you need this
You need this only if you’ve set a webhook secret in the dashboard. Otherwise skip this
section.
How to add the secret
In your TradingView alert message field, the indicator’s payload automatically includes the
secret if you set it as an input parameter in the indicator. Alternatively, you can append the
header in the webhook URL field:
[Link]
Replace YOUR_SECRET_HERE with your actual secret. The scanner will reject any incoming
webhook that doesn’t include the matching secret.
Quick Reference Card
Webhook URL: [Link] Message template:
{{alert_message}} Trigger: Once Per Bar Close Condition: Any alert()
function call Expiration: Open-ended
TradingView account tier needed: Pro (20 alerts), Pro+ (100), Premium (400)
Dashboard URL: [Link] Signup page:
[Link]
Need Help?
If you run into any issues during setup, document: 1. Screenshot of your alert configuration
in TradingView 2. Screenshot of the SIGNALS tab in dashboard 3. The ticker and timeframe
you’re using
Send these to Nouman (ahmednouman188@[Link]) and the issue can usually be
resolved quickly.
End of Alert Setup Guide