> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Hyperliquid User Fill

Triggers when a specific Hyperliquid user receives an order fill. Optionally filter by coin, side, fill direction, size, notional, or whether the order crossed the spread.

Trigger Other

Triggers when a specific Hyperliquid user receives an order fill. Optionally filter by coin, side, fill direction, size, notional, or whether the order crossed the spread.

## At a Glance

| Field | Value |
| --- | --- |
| Trigger ID | `hyperliquid-user-fill` |
| Category | Other |
| Tags | `hyperliquid`, `perps`, `fills`, `wallet-monitoring`, `websocket`, `real-time` |

## Trigger Configuration

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `user` | `string` | Yes | Hyperliquid user wallet address to monitor |
| `dex` | `string` | No | DEX venue for TradFi markets \(TSLA, SP500, GOLD\). Leave as default for crypto perps. |
| `coin` | `string` | No | Optional coin filter \(e.g., BTC, ETH for crypto; TSLA, SP500 for trade.xyz\) |
| `side` | `string` | No | Optional fill side filter |
| `direction` | `string` | No | Optional Hyperliquid fill direction filter |
| `minSize` | `number` | No | Optional minimum filled base size |
| `minNotional` | `number` | No | Optional minimum fill notional in USDC |
| `crossed` | `boolean` | No | Optional filter for fills that crossed the spread |

## Trigger Result

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

## Workflow Root Example

```json
{
  "nodes": {
    "root": {
      "type": "hyperliquid-user-fill",
      "payload": {
        "user": "0x0000000000000000000000000000000000000000"
      },
      "children": [
        "log_event"
      ]
    },
    "log_event": {
      "type": "log",
      "payload": {
        "message": "Triggered at {{$trigger.triggeredAt}}"
      },
      "children": []
    }
  }
}
```

**Reference trigger output**

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`.