Hyperliquid Transfer

Trigger Other

Triggers when a Hyperliquid user deposits, withdraws, transfers funds, or gets liquidated. Detect large fund movements and liquidations in real-time. Covers deposits from L1, withdrawals to L1, internal transfers, spot sends, vault operations, and position liquidations.

At a Glance

Field	Value
Trigger ID	hyperliquid-transfer
Category	Other
Tags	hyperliquid, transfers, deposits, withdrawals, whale-monitoring, websocket, real-time, liquidations

Trigger Configuration

Field	Type	Required	Description
user	string	Yes	Hyperliquid user wallet address to monitor for fund movements
transferType	string	No	Optional transfer category filter. Leave empty to match all types.
minUsdc	number	No	Optional minimum USDC value to trigger on. Filters out small movements.

Trigger Result

Field	Type	Required	Description
triggeredAt	string	Yes	Timestamp when the transfer was detected (UTC, RFC3339 format)
user	string	Yes	Monitored Hyperliquid user wallet address
transfer	object	Yes	-

Workflow Root Example

json
{  "nodes": {    "root": {      "type": "hyperliquid-transfer",      "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.