Looking for beta testers: Polymarket prediction market node with trading, whale tracking, and AI agent support

Built with n8n
,
1

Been building a community node for Polymarket and looking for feedback from people who trade prediction markets or want to automate against them.

What it does

n8n-nodes-polymarket-tools connects n8n to Polymarket’s API. 12 operations covering market search, pricing with order books, EIP-712 signed trading, and whale tracking via the Data API. Three polling triggers. Both nodes support `usableAsTool` for the AI Agent node.

Market: Search, Get

Price: Get (midpoint, spread, order book), Get History

Trading: Place Order (EIP-712 signed), Cancel Order, Get Open Orders

Data: Get Leaderboard, Get Wallet Positions, Get Wallet Trades, Get Market Holders

Market data and whale tracking work without credentials. Trading needs CLOB API keys from Settings | Polymarket .

15 templates included

Whale alerts, copy trading, sportsbook edge detection, AI news matching, tax reports, market making, and more. Each template is a real workflow you can import and run.

What I need

Feedback on the operations, the templates, and anything that breaks. If you trade on Polymarket or have been looking for prediction market automation in n8n, give it a try and let me know what’s missing.

**Install:** Settings > Community Nodes > `n8n-nodes-polymarket-tools`

2

This looks like a useful addition for prediction market automation. The whale tracking and AI agent node support are really interesting. One question: are there rate limits from Polymarket’s API that workflows should be aware of when building high-frequency triggers or polling patterns?

1 Like
3

Good question. Yes, Polymarket enforces rate limits via Cloudflare throttling (requests get queued, not rejected). Here are the numbers:

Gamma API (market search, metadata):

4,000 requests per 10 seconds. Generous for polling. A workflow that searches markets every 30 seconds will never come close.

CLOB API (pricing, order books, trading):

9,000 requests per 10 seconds for reads. Order placement is 3,500/10s burst with 36,000/10min sustained. Order cancellation is 3,000/10s burst. Unless you’re running a high-frequency market maker, these won’t be a constraint.

Data API (leaderboard, wallet positions, trades):

Tighter limits here. 1,000/10s general, but /trades is 200/10s and /positions is 150/10s. If your workflow polls multiple wallets on a fast interval, this is where you’ll hit the ceiling first.

What this means for n8n workflows:

Polling triggers at 1-5 minute intervals are fine across all APIs. Even at 1 minute, you’re making 1 request per poll, well under any limit.

Where it gets tight: if you’re iterating over the leaderboard and checking each wallet’s trades (like the Smart Money Radar template does), you’re making N+1 requests per cycle. With 10 wallets at 5 trades each, that’s 11 requests per poll. At a 2-minute interval, still fine. At a 10-second interval across 50 wallets, you’d hit the Data API’s

/trades limit. The node handles 429 responses by extracting the Retry-After header and surfacing it in the error message so you know exactly how long to wait. But the better approach is to set your polling interval wide enough that you never hit it.

Rule of thumb: poll every 1-5 minutes for most workflows. Drop to 30 seconds only for single-market price monitoring. The templates ship with conservative defaults.

Appreciate the question! Don’t hesitate to DM me if you try it and run into any issues!