CLOBr Logo

CLOBr Alerts

Get notified when market conditions change for tokens you're watching. Configure triggers, delivery channels (including webhooks for custom integrations), and rate limits.

Premium Feature: Alerts are available exclusively to premium subscribers.

What Are CLOBr Alerts?

CLOBr Alerts notify you when important market conditions change without constantly watching charts. Set up triggers based on CLOBr Score movements, DCA order pressure, or screener matches, and receive notifications via Telegram, Discord, Email, or in-app.

Alert Sources

Choose from three types of alert sources, each designed for different trading workflows:

Watchlist Alerts

Monitor specific tokens you've manually added to watchlists. Best for tokens you're actively tracking 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

Get notified when tokens match your saved screener criteria. Best for discovering new opportunities based on your filter preferences.

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

DCA Impact Alerts

Get notified when significant DCA (Dollar Cost Averaging) order pressure builds up. These alerts help you 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

Choose how you want to receive alerts. You can enable multiple channels and route different alert sources to different channels.

Telegram (Recommended)

Best for real-time alerts. Messages appear in your Telegram app with 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

Receive alerts via Discord webhook to any channel you control. Great for team trading rooms or personal server logging.

Email

Receive formatted HTML alerts to your email. Good for less time-sensitive alerts or daily summaries.

Desktop Notifications

Get native Mac/PC desktop notifications as long as your web browser is running.

Webhook (Custom Integration)NEW

Send structured JSON payloads to any HTTPS endpoint. Perfect for building custom integrations, trading bots, or connecting to automation platforms like n8n, Zapier, or Make.

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

Prevent alert fatigue with built-in controls. These settings help you receive meaningful alerts without getting overwhelmed.

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

Best Practices: Avoid Alert Fatigue

Too many alerts defeats the purpose. Quality over quantity will keep alerts actionable.

  • Raise thresholds: Score > 80 instead of > 60 reduces noise
  • Increase cooldowns: 2-4 hours instead of 1 hour per token
  • Reduce max/hour: 3-5 instead of 10 forces prioritization
  • Be selective: Only enable alerts on high-conviction watchlists
  • Use quiet hours: Mute overnight when you can't act anyway
  • Review and prune: Periodically disable triggers that aren't actionable

Effective Trigger Combinations

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. Use it to track what's triggered and take action:

  • 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