Hyperliquid Liquidation
Triggers when a monitored Hyperliquid user is liquidated. Optionally filter by minimum liquidated notional.
Trigger Other
Triggers when a monitored Hyperliquid user is liquidated. Optionally filter by minimum liquidated notional.
At a Glance
| Field | Value |
|---|---|
| Trigger ID | hyperliquid-liquidation |
| Category | Other |
| Tags | hyperliquid, perps, liquidation, wallet-monitoring, websocket, real-time |
Trigger Configuration
| Field | Type | Required | Description |
|---|---|---|---|
user | string | Yes | Hyperliquid user wallet address to monitor |
minNotional | number | No | Optional minimum liquidated notional in USDC |
Trigger Result
| Field | Type | Required | Description |
|---|---|---|---|
triggeredAt | string | Yes | Timestamp when the liquidation was detected (UTC, RFC3339 format) |
user | string | Yes | Monitored Hyperliquid user wallet address |
liquidation | object | Yes | - |
Workflow Root Example
json{ "nodes": { "root": { "type": "hyperliquid-liquidation", "payload": { "user": "example-user" }, "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.