Unusual Whales: Options Flow Alerts

Trigger Other

Triggers on unusual options activity via Unusual Whales. Captures sweeps, large premiums, and aggregated flow alerts in real-time via WebSocket. Optionally filter by ticker, minimum premium, option type, or sweep presence.

At a Glance

Field	Value
Trigger ID	unusual-whales-options-flow-alerts
Category	Other
Tags	options, flow, sweep, market-data, websocket, real-time

Trigger Configuration

Field	Type	Required	Description
tickers	array	No	Optional ticker filter. Only alerts for these tickers will trigger. If omitted, all tickers trigger.
minPremium	number	No	Optional minimum total premium in USD. Alerts below this threshold are ignored.
optionType	string	No	Optional option type filter. If omitted, both calls and puts trigger.
hasSweep	boolean	No	If true, only alerts containing sweep trades will trigger.

Trigger Result

Field	Type	Required	Description
id	string	Yes	Unique alert identifier
ticker	string	Yes	Underlying ticker symbol
optionChain	string	Yes	OSI option chain identifier
optionType	string	Yes	Option type: call or put
underlyingPrice	number	Yes	Spot price at alert time
totalPremium	number	Yes	Total dollar premium across trades
totalSize	integer	Yes	Total contracts traded
hasSweep	boolean	Yes	Whether the alert contains sweep trades
hasFloor	boolean	Yes	Whether the alert contains floor trades
hasMultileg	boolean	Yes	Whether the alert contains multi-leg trades
volume	integer	Yes	Session volume on the contract
openInterest	integer	Yes	Open interest
price	number	Yes	Last trade price
startTime	string	Yes	First trade timestamp (ISO 8601)
endTime	string	Yes	Last trade timestamp (ISO 8601)
tradeCount	integer	Yes	Number of trades in the alert
url	string	No	Deep link to the alert detail page

Workflow Root Example

json
{  "nodes": {    "root": {      "type": "unusual-whales-options-flow-alerts",      "payload": {        "tickers": [],        "minPremium": 1,        "optionType": "call",        "hasSweep": true      },      "children": [        "log_event"      ]    },    "log_event": {      "type": "log",      "payload": {        "message": "Triggered at {{$trigger.triggeredAt}}"      },      "children": []    }  }}

Downstream nodes can use {{$trigger.triggeredAt}} and any result fields listed above. Event triggers usually expose the raw source payload under a field such as event, body, trade, or raw.