Alerts & Webhooks

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.

• 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

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.

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:

{
  "event": "Bullish Exhaustion",
  "ticker": "BTCUSD",
  "exchange": "COINBASE",
  "tf": "720",
  "htf": "1W",
  "osc": 18.5,
  "time": 1779246306000
}

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.