Monitors
Monitors watch X accounts on a schedule and record new tweets as hits. They are a core product alongside the API — not billed against API quota.
Concepts
- Monitor task — one @username (optional keyword filter)
- Baseline — first successful poll stores
lastTweetIdwithout creating hits - Hit — a tweet newer than the baseline, stored in Dashboard and optionally sent via webhook
- Check interval — minimum seconds between polls (plan-dependent)
Dashboard usage
- Go to Dashboard → Monitors
- Enter
@usernameand optional keywords (comma-separated) - Click Check now to establish baseline
- New tweets appear under Recent hits; Dashboard shows cross-monitor activity
Keyword filter
If keywords are set (e.g. bitcoin, eth), only tweets containing at least one keyword (case-insensitive) become hits. Leave empty to capture all new tweets.
Check intervals by plan
| Plan | Monitors | Min interval |
|---|---|---|
| Free | 1 | 300s (5 min) |
| Starter | 3 | 120s (2 min) |
| Growth | 8 | 60s (1 min) |
| Pro | 20 | 30s |
| Scale | 50 | 15s |
How polling works
XFlux checks your monitors automatically on your plan's schedule (see intervals below). You can also click Check now on any monitor to poll immediately — useful right after creating a monitor or when testing.
First check = baseline
The first successful poll records the latest tweet ID without creating hits. Only tweets posted after that appear as hits in your Dashboard.Account availability
Most public X accounts work reliably. A small number of restricted or high-profile accounts may fail to poll. If you see an error, try another account or contact support.