Signals & Automation

IIF Alerts and Webhook Payloads

Every framework event can fire as a TradingView alert carrying a clean, flat JSON payload, ready for webhooks, trading bots, journals, and downstream review systems.

Updated Publisher Alien_AlgorithmsCurrent release

How alerting works

IIF uses TradingView's alert() dispatch model: you toggle the events you care about inside the indicator settings (10 Alerts - Any Events), then create one alert on the indicator with the condition Any alert() function call. Every enabled event flows through that single alert, each with its own JSON body.

This page covers the alerts IIF sends. For webhooks from any TradingView indicator or strategy, see our guides to the webhook JSON payload and to alerts whose webhook never arrives, and send a test alert to the free TradingView webhook tester.

  • All events dispatch once per bar close, consistent with the framework's confirmed-bar, no-repaint design.
  • Bullish and bearish variants toggle independently, so a webhook can subscribe to exactly one side.
  • The Confluence Engine fires through the same channel, with your custom rule name as the event.

Event catalog

10 Alerts - Any Events
SettingDefaultWhat it does
Bull / Bear OB Created-A new OrderBlock qualified and is now tracked.
Bull / Bear OB Tapped-Price entered an active OrderBlock for the first time.
Bull / Bear OB Mitigated-Every internal gap filled and price closed outside. The block fully resolved.
Bull / Bear Exhaustion-The Block Exhaustion signal fired (heavily filled block + CVMI extreme).
Bull / Bear Sweep-The Block Sweep signal fired (edge swept, zone reclaimed, closes confirmed).
Bull / Bear Failure-A block’s structural break level was breached. Bull = bearish OB broken upward; Bear = bullish OB broken downward.
Bull / Bear Squeeze-A Squeeze Candle printed: a single-bar momentum extreme out of compression.
Shift Detected / Broken-A new Structural Shift level appeared, or an existing one was broken.
Trend Change-The structural trend flipped direction.

Event names arrive in the payload exactly as listed (e.g. "Bullish Sweep", "Shift Broken"), so downstream routing is a simple string match.

Setting up an alert

  1. 1
    Toggle the events you want

    In the indicator settings, open 10 Alerts - Any Events and enable the specific bull/bear events (or configure a Confluence rule instead).

  2. 2
    Create one TradingView alert

    Right-click the chart → Add alert. Condition: the IIF indicator → Any alert() function call. Leave the message field as-is; the script supplies the JSON body.

  3. 3
    Point it at your endpoint

    For automation, enable the Webhook URL notification and paste your endpoint. For discretionary use, app/popup/email notifications carry the same JSON text.

One alert, many events

Because dispatch is centralized, you rarely need more than one TradingView alert per chart, which is useful on plans with low alert limits. Route by the event field on your server instead.

The JSON payload

Payloads are intentionally flat, with no nesting and no arrays, so they parse trivially in any webhook receiver, spreadsheet importer, or no-code tool:

Example: Bullish Exhaustion on BTC 12Hjson
{
  "event": "Bullish Exhaustion",
  "ticker": "BTCUSD",
  "exchange": "COINBASE",
  "tf": "720",
  "htf": "1W",
  "osc": 18.5,
  "time": 1779246306000
}
Payload fields (10 Alerts - JSON Payload)
SettingDefaultWhat it does
eventalwaysThe event name, or your Confluence rule’s Alert Name.
ticker / exchangeOnSymbol and exchange prefix, from the “Symbol & Timeframe” toggle.
tf / htfOnChart timeframe and the SOMM detection HTF (TradingView notation: minutes, or D/W/M).
oscOnCVMI at dispatch: the normalized 0-100 reading when normalization is on, the raw index otherwise.
timeOnUnix millisecond timestamp of dispatch.

Each optional field group can be excluded from the payload via its toggle if your receiver wants a minimal body.

Automation patterns

  • Bot gating: rather than executing on raw signals, many users feed osc into their bot as a regime filter: only take longs delivered with osc below 30, for example.
  • Journaling: pipe payloads into a sheet or database; the flat schema means every field becomes a column. Over time you get a personal hit-rate dataset per event type, per symbol, per session.
  • Multi-timeframe dashboards: run IIF on several charts with one webhook endpoint; the tf/htf fields keep streams separable.
  • Confluence-first automation: the cleanest pattern is to encode the entire entry condition in the Confluence Engine so the webhook only ever receives decision-grade events.
Automation is your responsibility

Alert payloads are analytical events, not trade instructions. Anything you build downstream (sizing, risk, execution) is outside the indicator's scope. Test against paper endpoints first.

Webhook troubleshooting

When the alert fires on the chart but nothing reaches your server, the cause is almost always one of TradingView's own webhook requirements:

  • Two-factor authentication: TradingView only sends webhooks from accounts with two-factor authentication turned on.
  • Ports 80 and 443 only: if the URL names a port, it must be one of these. Requests to any other port are rejected.
  • Three-second limit: a request is cancelled when your server takes longer than three seconds to process it. Reply with 200 first and do slow work afterwards.
  • IPv4 only: IPv6 is not supported, so the endpoint must be reachable over IPv4.
  • Sender addresses: if your firewall uses an allowlist, TradingView sends from 52.89.214.238, 34.212.75.30, 54.218.53.128 and 52.32.178.7.
  • Content type: a message that is valid JSON arrives as application/json, anything else as text/plain. IIF builds the JSON itself, so leave the alert's message field as the script supplies it.

Deliveries can occasionally fail. The Webhook status column in the alert log shows whether each one arrived. Do not put credentials or passwords in a webhook body. Source: TradingView's guide to webhook alerts.

To see exactly what IIF sends, point a test alert at our free TradingView webhook tester: it shows each request with its JSON, content type and sender. When the alert fires and nothing arrives, the guide TradingView alert fired, but the webhook never arrived? goes through each step of the route.

For webhooks from any indicator or strategy, with every TradingView placeholder and a minimal receiver, read the guide to TradingView webhook JSON payloads.

Institutional Imbalance Framework is analytical software. It offers no guarantee of financial gain, and nothing in these docs is financial advice. © Alien_Algorithms.

Also from us: Sentalysis, market sentiment research.