Polymarket: Trader Places Bet
Triggers when a specific Polymarket user places a new trade. Great for copy-trading strategies. Identify the trader by username or wallet address.
Trigger Markets
Triggers when a specific Polymarket user places a new trade. Great for copy-trading strategies. Identify the trader by username or wallet address.
At a Glance
| Field | Value |
|---|---|
| Trigger ID | polymarket-user-bet |
| Category | Markets |
| Tags | polymarket, prediction-market, trading, copy-trading, bet, user-monitoring |
Trigger Configuration
| Field | Type | Required | Description |
|---|---|---|---|
user | string | Yes | The Polymarket user to monitor. Enter a wallet address (0x...) or a Polymarket username (e.g., 'gabagool22'). Usernames are automatically resolved to wallet addresses. |
minSize | number | No | Minimum trade amount in USDC to trigger on. Only trades with USDC value >= this amount will trigger the workflow. |
side | string | No | Filter by trade side. If not specified, triggers on both BUY and SELL trades. |
marketIds | array | No | Optional list of market/condition IDs to filter. Only trades in these markets will trigger. |
keywords | array | No | Filter by market keywords. Only trades on markets whose title or description contain any of these keywords will trigger. Case-insensitive substring match. |
minPrice | number | No | Minimum trade price (0-1 range, e.g. 0.30 = 30¢). Only trades at or above this price will trigger. |
maxPrice | number | No | Maximum trade price (0-1 range, e.g. 0.80 = 80¢). Only trades at or below this price will trigger. |
Trigger Result
| Field | Type | Required | Description |
|---|---|---|---|
triggeredAt | string | Yes | Timestamp when the trade was detected (UTC, RFC3339 format) |
trade | object | Yes | Details of the detected trade |
Workflow Root Example
json{ "nodes": { "root": { "type": "polymarket-user-bet", "payload": { "user": "0x37c1874a60d348903594a96703e0507c518fc53a" }, "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.