1.  [](/)
2.  [Capabilities](/capabilities)
3.  Real-time Alerts

Back to Capabilities

# Real-time Alerts

Trigger notifications when retriever results match conditions on ingest, schedule, or demand

[Create Alert](/start)

### Why do anything?

Important content changes go unnoticed without proactive monitoring. Manual checking doesn't scale.

### Why now?

Real-time applications need instant notifications when relevant content appears.

### Why this feature?

Alert system with three execution modes: ON\_INGEST (real-time), SCHEDULED (cron), ON\_DEMAND (API trigger). Multiple notification channels.

## How It Works

Alert system monitors retriever results and triggers notifications based on conditions.

1

#### Trigger

ON\_INGEST, SCHEDULED, or ON\_DEMAND execution

2

#### Retriever Execution

Run associated retriever query

3

#### Condition Evaluation

Check if results match alert conditions

4

#### Notification

Send alerts via EMAIL, SLACK, or WEBHOOK

### Why This Approach

Multiple execution modes support different monitoring patterns. Retriever-based alerts leverage existing search logic.

## Where This Is Used

[

Media

#### Breaking Content Alerts



](/solutions/media-intelligence)

[

Security

#### Threat Detection Alerts



](/solutions/security)

## Integration

PythonAPI

alert = client.alerts.create(retriever\_id="...", execution\_mode="ON\_INGEST", channels=\[...\])

[View Documentation](https://mixpeek.com/docs/overview/concepts)

## Recent updates

[Full changelog](/changelog)

*   [Sep 27, 2026An alert's batch action runs as soon as the alert fires on uploadAn on-ingest alert can send its matches to a collection for further processing. When the alert fired at the moment an object was written, those matches were queued and waited for some unrelated batch to finish, or indefinitely in a namespace without one. They are now submitted when the alert fires.](/changelog)
*   [Sep 26, 2026Alerts fire when a match scores above 1Alert matches were validated to a score between 0 and 1, and retriever scores can land outside that range: cosine similarity on float32 returns 1.0000002 for a document matched against its own content, and BM25 has no upper bound. One such score dropped every match for the alert, so an on-ingest alert whose query was the document itself never fired. Scores are now clamped into 0 to 1 before validation.](/changelog)
*   [May 20, 2026Faster system alert evaluationAlert sweeps now read metrics in parallel and evaluate across orgs in a single pass, keeping large-tenant alert evaluation well within its window.](/changelog)

## Related Capabilities

[

often combined

#### Webhooks

Alerts can trigger webhooks



](/capabilities/webhooks)

[

prerequisite

#### Feature Search

Alerts use retrievers for monitoring



](/capabilities/feature-search)