> ## Documentation Index
> Fetch the complete documentation index at: https://ekso.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Configure scheduled notifications that alert user groups, email addresses, Slack, Teams, or HTTP endpoints when items match your conditions.

## Overview

Notifications send scheduled alerts when items match conditions you define. Unlike [webhooks](/guide/concepts/webhooks) (which fire immediately on events), notifications run on a recurring schedule, evaluate a set of filter conditions, and deliver matching items to your chosen recipients.

You manage notifications under **Settings > Notifications**.

## How notifications work

Each notification follows a three-step cycle:

1. **Evaluate** — on the configured interval, Ekso evaluates the notification's filter conditions against items in the selected containers
2. **Match** — items that satisfy the conditions are collected for delivery
3. **Deliver** — matching items are sent to all configured recipients

This cycle repeats on the interval you set, continuously monitoring for items that match your criteria.

## Notification settings

| Property    | Description                                                                                    |
| ----------- | ---------------------------------------------------------------------------------------------- |
| Name        | Display name for the notification                                                              |
| Description | What the notification monitors and why                                                         |
| Active      | Whether the notification is currently running                                                  |
| Container   | Which containers to evaluate (select one or more)                                              |
| Interval    | How often to check for matches (default: every 3 hours)                                        |
| Limiter     | How many times the same item triggers this notification — `0` for unlimited, `1` for once only |

<Note>
  The default interval is **3 hours** (180 minutes). Set a shorter interval for time-sensitive alerts like SLA breaches, or a longer interval for daily digest-style notifications.
</Note>

### Frequency limiter

The limiter controls repeat delivery for the same item:

| Value | Behavior                                                                              |
| ----- | ------------------------------------------------------------------------------------- |
| 0     | No limit — the item is included every time the notification runs and it still matches |
| 1     | Send once — after the item is delivered for this notification, it is not sent again   |

Use a limiter of `1` for one-time alerts (e.g., "notify when an item is overdue"). Use `0` for recurring digests where you want to see all currently matching items each time.

## Conditions

Conditions define which items trigger the notification. They use the same AND/OR group model as [rules](/guide/concepts/rules#conditions):

* **Within a group** — conditions are joined with AND (all must match)
* **Between groups** — groups are joined with OR (any group can match)

Each condition specifies a field, operator, and value. For example:

* `Status Equal Blocked` AND `Priority Equal High` — notify when high-priority items are blocked
* `DueDate LessThan TODAY` — notify when items are past their due date

## Recipients

Notifications support four recipient types. You can combine multiple types on a single notification.

### User groups

Select one or more user groups. Every member of the group receives the notification. Use the **Everyone** group to notify all users in the tenant.

### Email addresses

Add specific email addresses for recipients who may not have Ekso accounts — for example, external stakeholders or distribution lists.

### Slack and Teams

Connect to Slack or Microsoft Teams by specifying a pre-configured connection ID. Notifications are delivered as messages to the connected channel.

<Tip>
  Configure your Slack or Teams integration first, then reference the connection in your notification recipient configuration.
</Tip>

### HTTP endpoints

Send notification payloads to an HTTP endpoint for custom integrations. This is useful for routing notifications to external systems, dashboards, or automation workflows.

## Use cases

| Scenario                | Configuration                                                                                                                          |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| SLA breach alert        | Condition: `ClockStatus Equal Red`. Interval: 30 minutes. Limiter: 1. Recipients: Support team group.                                  |
| Daily overdue digest    | Condition: `DueDate LessThan TODAY` AND `Status Not Equal Closed`. Interval: 24 hours. Limiter: 0. Recipients: Project managers group. |
| Blocked item escalation | Condition: `Status Equal Blocked`. Interval: 1 hour. Limiter: 1. Recipients: Team leads group + Slack channel.                         |
| Customer ticket monitor | Condition: `Crm Equal Example Inc` AND `Priority Equal High`. Interval: 1 hour. Limiter: 0. Recipients: account manager email.         |