Alerts System
The Alerts system enables proactive monitoring of your workflows by notifying you when specific conditions occur. Built on top of saved views, alerts help you stay informed about critical events, performance issues, or unusual activity patterns without constant manual monitoring.
Key Features
Automated notifications based on saved view criteria
Email alerts for workflow events
Customisable alert conditions
Integration with Activity saved views
Team-wide alert management
Real-time monitoring capabilities
Understanding Alert Prerequisites
Saved Views Requirement
Alerts are created from saved views in the Activity tab:
You must first create a saved view with specific filters
The saved view defines what conditions trigger the alert
Alerts monitor for any activity matching the saved view criteria
⚠️ You cannot create alerts without first setting up a saved view in the Activity tab.
How to Create Alerts
Step 1: Prepare Your Saved View
Go to the Activity tab
Apply filters for the conditions you want to monitor
Save the view with a descriptive name
Ensure the view captures the exact criteria for your alert
Step 2: Navigate to Saved Views
Click on the "Saved Views" tab in the navigation
You'll see a list of all your saved views
Each saved view displays its filters and creation details
Step 3: Create an Alert
Find the saved view you want to create an alert for
Look for the bell icon next to the saved view
Click the bell icon to open alert configuration
Configure your alert settings:
Alert name
Notification recipients
Frequency settings
Save the alert configuration
💡 Name your alerts clearly to indicate what they monitor, such as "Failed Production Workflows" or "Long-Running API Calls".
How to Manage Existing Alerts
Viewing Active Alerts
In the Saved Views tab, alerts are indicated by active bell icons
Click on an alert to view its configuration
See when the alert was last triggered
Review the underlying saved view criteria
Modifying Alerts
Click on the bell icon of an existing alert
Update the alert configuration:
Change recipients
Modify notification settings
Update the alert name
Save changes to update the alert
Disabling or Deleting Alerts
Click on the active bell icon
Choose to either:
Disable temporarily (alert can be re-enabled)
Delete permanently
Confirm your action
⚠️ Deleting an alert is permanent, but the underlying saved view remains intact.
Understanding Alert Notifications
What Triggers Notifications
Alerts send notifications when:
New activity matches your saved view criteria
The specified conditions are met
Based on your configured frequency settings
Notification Contents
Alert emails include:
Alert name and description
Number of matching activities
Direct link to view the activities
Summary of the filter criteria
Timestamp of the alert
💡 Click the link in alert emails to go directly to the filtered activity view.
Common Alert Scenarios
Performance Monitoring
Saved View: Workflows with run time > 5 minutes Alert Purpose: Identify performance degradation Action: Investigate and optimise slow workflows
Error Tracking
Saved View: Failed workflows in production Alert Purpose: Immediate notification of failures Action: Quick response to production issues
Usage Monitoring
Saved View: Specific workflow executions Alert Purpose: Track usage of critical processes Action: Ensure important workflows are being used
Security Monitoring
Saved View: Workflows run by external users Alert Purpose: Monitor external access Action: Verify authorised usage
💡 Create multiple alerts for comprehensive monitoring coverage across different aspects of your operations.
How to Use Saved Views Effectively
Accessing Saved Views
Click on a saved view name to apply it instantly
The Activity tab opens with pre-selected filters
All relevant data is displayed immediately
Modify filters further if needed
Managing Saved Views
Edit saved view names for clarity
Delete unused saved views to reduce clutter
Share saved views with team members
Create views specifically for alert purposes
⚠️ Deleting a saved view will also delete any associated alerts.
Best Practices
For Alert Creation
Create specific, focused saved views for alerts
Test saved views thoroughly before creating alerts
Use descriptive names for both views and alerts
Document what each alert monitors and why
For Alert Management
Review alerts regularly for relevance
Update recipient lists as team changes occur
Disable rather than delete alerts during testing
Consolidate similar alerts to reduce noise
For Team Collaboration
Share alert configurations with team members
Document response procedures for each alert
Assign alert ownership for accountability
Regular review meetings for alert effectiveness
For Optimal Monitoring
Balance coverage with alert fatigue
Start with critical alerts, expand gradually
Set appropriate frequency to avoid spam
Use different recipients for different severity levels
💡 Well-configured alerts transform reactive troubleshooting into proactive system management, significantly improving workflow reliability.
Last updated