IANews
GuidesTrends

Trend alerts

Configure real-time alerts with conditions and destinations.

Trend alerts

Alerts notify you automatically when trends match your conditions. Instead of checking the trends page manually, define rules and receive notifications via email, Slack, Discord, or webhook the moment a matching trend is detected.

How alerts work

The system continuously processes new and updated trends in real time. For each trend, it evaluates all active alert rules. When a trend matches an alert's conditions, a notification is dispatched to every destination configured on that alert. Evaluation and dispatch happen within seconds of trend detection.

Creating an alert

Open the Alerts page

Navigate to Alerts in the sidebar and click New Alert.

Set conditions

Define what triggers the alert. All conditions are combined with AND logic -- a trend must match every condition to trigger the alert.

  • Score threshold -- Minimum trend score to trigger (e.g., score > 75). Higher thresholds reduce noise.
  • Category -- One or more categories (e.g., Technology, AI). Only trends in these categories match.
  • Keyword -- A text pattern the trend title must contain (e.g., "quantum computing", "GPT").
  • Country -- One or more countries (e.g., US, France). Only trends from these countries match.
  • Lifecycle -- One or more lifecycle stages (e.g., only "emerging" or "growing"). Useful for catching trends early.

Set destinations

Choose one or more places to receive notifications. You can combine multiple destinations on a single alert.

  • Email -- Sends a formatted email to your account address.
  • Webhook URL -- POSTs a JSON payload to your endpoint. Useful for integrating with custom tools or automation platforms.
  • Slack -- Posts to a Slack channel via an incoming webhook URL.
  • Discord -- Posts to a Discord channel via a webhook URL.

Name and save

Give the alert a descriptive name (e.g., "AI Breakthroughs - High Score") and click Save. The alert becomes active immediately.

Webhook payload

When an alert fires to a webhook destination, the payload looks like this:

{
  "alert_id": "alert_123",
  "alert_name": "AI Breakthroughs",
  "trend": {
    "id": "trend_456",
    "title": "GPT-5 Announcement",
    "score": 89,
    "lifecycle": "peaking",
    "category": "ai",
    "country": "US"
  },
  "triggered_at": "2026-02-21T10:30:00Z"
}

Your endpoint should respond with a 2xx status code. Failed deliveries are retried with exponential backoff.

Managing alerts

On the Alerts page, each alert card shows its name, conditions summary, and recent trigger count. You can:

  • Edit -- Update conditions or destinations at any time. Changes take effect immediately.
  • Pause / Resume -- Temporarily disable an alert without deleting it. Paused alerts do not evaluate or fire.
  • Delete -- Permanently remove an alert and its trigger history.
  • View history -- See a log of every time the alert fired, including the trend that triggered it and the timestamp.

Start with broad alerts (one category + a high score threshold like 70+) and observe what triggers them. Then refine by adding keywords or tightening the score threshold to reduce noise.

Alert limits by plan

PlanMax alerts
Free3
Pro25
Business100
EnterpriseUnlimited

What's next?

On this page