Notifications

​

Overview

Notifications send scheduled alerts when items match conditions you define. Unlike 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

​

Frequency limiter

The limiter controls repeat delivery for the same item: 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:

• 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.

​

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