How to Use Workflow Analytics
Monitor how your Smart Workflows are performing with real trigger data, conversion rates, and actionable insights that help you optimize automation rules instead of guessing whether they are working.
Quick Summary
Go to Smart Workflows → Workflow Analytics to review trigger activity, work request generation rates, peak activity times, and sensor threshold insights.
Why Workflow Analytics Matter
Setting up automation rules is the easy part. Knowing whether those rules are doing useful work — or drowning your team in noise — requires ongoing visibility:
- Are your IoT-triggered workflows creating too many alerts? (alert fatigue)
- Are rules converting into actual work requests at a healthy rate?
- Which time periods see the most triggers? (staffing implications)
- Are sensor thresholds set correctly, or are they tripping on normal fluctuations?
Workflow Analytics answers these questions with actual operational data.
Before You Begin
- You need permission to view Smart Workflows
- Analytics are based on existing automation rules and their trigger history
- Date range filtering is available for focused analysis
Key Metrics (KPIs)
At the top of the analytics page, four key performance indicators summarize your automation health:
| KPI | What It Shows |
|---|---|
| Total Triggers | How many times automation rules fired in the selected period |
| Active Rules | Number of currently active rules (with percentage and disabled count) |
| Work Requests Generated | How many triggers converted into work requests (with conversion rate) |
| Peak Period Triggers | Busiest trigger period for staffing awareness |
Each KPI includes trend data comparing to the prior period so you can spot changes.
Analytics Sections
Trigger Activity Trend
A daily chart showing trigger volume over time with anomalies highlighted. Use this to:
- spot sudden spikes that may indicate a sensor issue or environmental event
- confirm that seasonal patterns align with expectations
- identify days with unusually low activity (sensor offline? rule disabled?)
Work Request Generation
Shows the relationship between triggers and actual work requests:
- Work Requests Created — total with conversion rate
- Pending Assignment — requests awaiting team pickup (may indicate staffing gap)
- Assigned / In Progress — workforce handling load
- Projected next week — estimated upcoming work request volume
Peak Activity Times
A heatmap showing when triggers fire across the day:
| Period | Time Range |
|---|---|
| Morning | Typical work start hours |
| Afternoon | Midday operational period |
| Evening | End-of-day transition |
| Night | Off-hours and overnight |
Use this to align staffing with automation output. If most triggers fire during night hours but your team only works days, work requests pile up.
Trigger Insights
A table showing threshold vs. actual sensor values for each rule:
| Column | Description |
|---|---|
| Rule Name | The automation rule |
| Location | Where the sensor is installed |
| Sensor | Which sensor triggered |
| Triggers | Number of times this rule fired |
| Status | Normal, Warning, or Alert Fatigue |
| Parameters | Threshold, Min, Avg, Max values |
Click any row to expand parameter details and see how actual readings compare to your configured thresholds.
Actionable Insights
Workflow Analytics surfaces three types of operational insights:
Alert Fatigue Risk
Rules that trigger more than 50 times per day on average are flagged. When alerts fire too frequently, teams start ignoring them — which defeats the purpose of automation.
Action: Click Review Thresholds to adjust the trigger conditions so only meaningful events create work.
Silent Rules
Rules that have not triggered recently may indicate:
- a sensor that went offline
- a threshold set too high to ever trip
- a rule that was disabled and forgotten
Action: Click View Inactive Rules to review and reactivate or remove stale rules.
Repeat Offenders
Assets that trigger automation frequently may need planned maintenance rather than reactive workflows.
Action: Click Investigate Assets to review which assets are generating the most automation activity and consider preventive maintenance scheduling.
Filtering and Export
- Use date range shortcuts (This Month, Last Month, Last 30 Days, Last 7 Days) to focus the analysis
- Click Export Report to download the analytics data for offline review or reporting
Real-World Example
Optimizing HVAC Temperature Alerts
Situation: Your building has 40 temperature sensors with automation rules that create work requests when readings exceed 28°C. The team is getting 60+ alerts per day and has started ignoring them.
How Analytics Helps:
- Open Smart Workflows → Workflow Analytics
- The Alert Fatigue Risk insight flags 8 rules firing >50 times/day
- The Trigger Insights table shows these sensors have an average reading of 27.5°C — very close to the 28°C threshold
- The Peak Activity Times heatmap shows most triggers fire between 2-4 PM when ambient temperature naturally peaks
Solution: Raise the threshold to 30°C for non-critical areas and add a sustained-duration condition (trigger only if temperature stays above threshold for 15 minutes). Keep the 28°C threshold for server rooms and critical equipment.
Result: Alerts drop from 60+ to 8 per day. Each alert now represents a genuine operational issue. The team starts paying attention again.
Related Articles
Need help? Contact Infodeck Support