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

# Polymarket: Trade on Market

Triggers whenever a trade happens on a specific Polymarket market. Useful for monitoring activity and reacting to trading in real time.

Trigger Markets

Triggers whenever a trade happens on a specific Polymarket market. Useful for monitoring activity and reacting to trading in real time.

## At a Glance

| Field | Value |
| --- | --- |
| Trigger ID | `polymarket-market-trade` |
| Category | Markets |
| Tags | `polymarket`, `prediction-market`, `trading`, `market-monitoring`, `websocket`, `real-time` |

## Trigger Configuration

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `marketId` | `string` | Yes | The Polymarket market identifier. Accepts a condition ID \(starts with 0x\) or a market slug. To find the slug: open the market on polymarket.com and copy the last part of the URL after /event/ \(e.g. polymarket.com/event/will-bitcoin-hit-100k → use 'will-bitcoin-hit-100k'\). |
| `outcome` | `string` | No | Optional: filter by outcome. Only trades for this outcome will trigger. |
| `minSize` | `number` | No | Minimum trade size \(in shares\) to trigger on. Only trades >= this size will trigger. |
| `side` | `string` | No | Filter by trade side. If not specified, triggers on both BUY and SELL trades. |

## Trigger Result

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `triggeredAt` | `string` | Yes | Timestamp when the trade was detected \(UTC, RFC3339 format\) |
| `market` | `object` | Yes | Market information |
| `trade` | `object` | Yes | Details of the detected trade |

## Workflow Root Example

```json
{
  "nodes": {
    "root": {
      "type": "polymarket-market-trade",
      "payload": {
        "marketId": "will-bitcoin-hit-100k"
      },
      "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`.