CLOBr Alerts

Overview

Alerts fire when market conditions change so you don't have to watch charts all day. Set triggers on CLOBr Score movements, DCA pressure, or screener matches. Notifications go to Telegram, Discord, Email, or in-app.

Alert Sources

Three types of alert sources:

Watchlist Alerts

Triggers on tokens in your watchlists -- the ones you're actively trading or holding.

• Score Above: Alert when CLOBr Score exceeds your threshold (e.g., > 75)
• Score Below: Alert when CLOBr Score drops below your threshold (e.g., < 30)
• Score Increase: Alert when score rises by X points within Y minutes (e.g., +20 pts in 60min)
• Score Decrease: Alert when score drops by X points within Y minutes

Screener Alerts

Fires when tokens match your saved screener criteria. Good for discovering new tokens that fit your filters.

• Score Above: Alert when screener matches have score above threshold
• Score Below: Alert when screener matches have score below threshold

DCA Impact Alerts

Fires when DCA order pressure builds up. Spot large scheduled buy or sell pressure before it executes.

• Impact %: Set minimum price impact threshold (e.g., 5% means alert when DCA orders represent 5%+ expected price impact)
• Time Window: Choose look-ahead period (5min, 30min, 1hr, 6hr, or 24hr)
• Direction: Filter by buy pressure only, sell pressure only, or both

Delivery Channels

You can enable multiple channels and route different alert sources to different ones.

Telegram (Recommended)

Best for real-time alerts. Rich formatting, token info, and quick links.

• Start a chat with the CLOBr bot
• Send /start to receive a verification code
• Enter the code in CLOBr to link your account

Discord

Webhook to any channel you control. Works well for team trading rooms or personal server logging.

Email

Formatted HTML alerts. Better for less time-sensitive monitoring.

Desktop Notifications

Native Mac/PC notifications while your browser is running.

Webhook (Custom Integration)NEW

Structured JSON payloads to any HTTPS endpoint. Build custom integrations, trading bots, or connect to n8n, Zapier, Make, etc.

Use cases:

• Trading bots: Trigger automated trades based on alert conditions
• Custom alert routing: Forward alerts to Slack, Microsoft Teams, or other platforms
• Automation workflows: Connect to n8n, Zapier, Make, or other workflow tools
• Data logging: Store alerts in your own database for analysis

Setup:

• Go to Alerts > Channels > Webhook
• Enter your webhook endpoint URL (must be HTTPS)
• Generate a signing secret for request verification (recommended)
• Toggle "Enable Webhook" when ready
• Click "Test" to send a test payload

Webhook Payload Structure

{
  "version": "1.0",
  "delivery_id": "uuid",
  "event_type": "alert.triggered",
  "timestamp": "2025-12-09T...",
  "alert": { "title", "message", "category", "source_type", "pressure_type" },
  "token": { "address", "symbol", "name", "icon_url", "is_verified" },
  "metrics": { "clobr_score", "price_usd", "market_cap_usd", ... },
  "trigger": { "type", "threshold", "actual_value", "time_interval" },
  "dca_impact": { "timeline": [{ "period", "net_usd", "net_percent" }] },
  "formatted": { "price", "market_cap", "liquidity", ... },
  "links": { "clobr", "jupiter", "dexscreener", "birdeye", "solscan" },
  "audit": { ... }
}

Security Headers

All webhook requests include the following headers for verification:

• X-CLOBr-Event: Event type (e.g., "alert.triggered")
• X-CLOBr-Delivery-ID: Unique delivery ID for deduplication
• X-CLOBr-Timestamp: ISO timestamp of the request
• X-CLOBr-Signature: sha256=<HMAC signature> (if signing secret is configured)

Tip: Always verify the signature in production by computing HMAC-SHA256 of the raw request body using your signing secret and comparing it to the X-CLOBr-Signature header value.

Rate Limiting & Cooldowns

Built-in controls to keep alerts useful instead of noisy.

Per-Source Settings

• Cooldown: Minimum minutes between alerts for the same token from this source (default: 60 min)
• Max/Hour: Maximum total alerts per hour from this source, all tokens combined (default: 10)

Global Settings

• Pause All Alerts: Temporarily stop all notifications
• Quiet Hours: Set a daily time range when alerts are silenced (timezone-aware)

Setting Up Alerts

1. Connect a delivery channel: Go to Alerts > Channels and set up at least one channel (Telegram recommended)
2. Create a source: Either create a watchlist with tokens you want to monitor, or save a screener preset with your filter criteria
3. Configure triggers: Go to Alerts > Triggers, expand your watchlist/screener, and toggle on the triggers you want
4. Adjust thresholds: Set score thresholds, point changes, or time windows based on your trading style
5. Select channels: Click channel buttons to choose where each source sends alerts

Example Trigger Setups

For Swing Trading

• Score Above 70 (potential strength developing)
• Score Below 30 (potential weakness/exit signal)
• 60-120 minute cooldowns per token

For DCA Pressure Monitoring

• 5-10% impact threshold
• 1-6 hour time window
• Buy only (if looking for accumulation signals)

For Screener Discovery

• Score Above 65 on your preferred screener filters
• Higher max/hour (5-10) since these are new tokens
• Longer cooldowns (2-4 hours) per token once alerted

Managing Your Alert Feed

The Feed tab shows all received alerts:

• Filter by read/unread status or search by token symbol
• Click any alert to view token details
• Mark alerts as read individually or all at once
• Dismiss alerts you don't need
• Add noisy tokens to the Blocklist to stop future alerts for them

Troubleshooting

Not Receiving Alerts?

• Verify your channel is properly connected (test it)
• Check that triggers are enabled (toggle must be ON/blue)
• Check that channels are selected for your source (click channel buttons)
• Make sure "Pause All Alerts" is OFF in Settings
• Check Quiet Hours aren't blocking alerts during current time
• You may have hit your max/hour limit - wait or increase the limit

Getting Too Many Alerts?

• Raise score thresholds
• Increase cooldown times
• Reduce max/hour per source
• Disable some trigger types
• Add noisy tokens to your blocklist