Skip to main content
Notifications keep you informed when critical events occur in your systems. Configure custom rules to receive alerts through your preferred channels.

​
Notification Rules

Notifications Create rules to define when and how you want to be notified about events in your fleet.

​
Creating a Notification Rule

  1. Name your rule - Give it a descriptive name (e.g., “Critical Temperature Alerts”)
  2. Filter by criteria - Define which events trigger this notification:
    • System - Select a specific system or leave empty for all systems
    • Trigger - Choose which trigger activates the notification or leave empty for all triggers
    • Priority - Filter by event priority level
    • Labels - Add custom labels to refine targeting (optional, add as many as needed)
  3. Choose notification channels - Select where you want to receive alerts:
    • InApp - Notifications within the Heex platform
    • By email - Email notifications to your registered address
    • By Slack - Direct messages in your connected Slack workspace
Empty fields act as wildcards. For example, leaving “System” empty will apply the rule to all systems in your workspace.

​
Managing Rules

  • Edit - Modify rule parameters at any time
  • Delete - Remove rules you no longer need
  • Rules are applied in real-time once saved

​
Connected Applications

Connected Applications Manage third-party applications that can receive your notifications.

​
Available Applications

  • Slack - Send notifications to Slack channels or direct messages
  • More integrations coming soon

​
Connecting an Application

  1. Click Connect next to the application you want to add
  2. Authenticate with the application (e.g., sign in to Slack)
  3. Grant Heex permission to send notifications
  4. Configure destination channels (Slack channel, email address, etc.)

​
Disconnecting an Application

Disconnecting an application will stop all notifications configured to use it. Notification rules will remain but won’t deliver alerts through the disconnected channel.
To disconnect an application:
  1. Click Delete next to the connected application
  2. Confirm the disconnection
  3. Update your notification rules to use alternative channels

​
Best Practices

  • Use specific rules for critical alerts - Configure high-priority events with multiple notification channels
  • Filter by labels - Use labels to create granular rules for specific subsystems or test environments
  • Test your rules - Create a test notification rule and verify it works before deploying to production
  • Keep applications connected - Regularly check that your connected applications are active to ensure notifications are delivered