50 lines
1.0 KiB
Markdown
50 lines
1.0 KiB
Markdown
# 📅 Day 4 — Implementing Intelligent Alerts
|
|
|
|
## 🎯 Goal
|
|
Make the workflow proactive — detect critical issues and send immediate alerts.
|
|
|
|
---
|
|
|
|
## 🧩 Tasks
|
|
|
|
### 1. Branch the Workflow
|
|
- After Python node, split into two paths:
|
|
- **Reporting/Storage**
|
|
- **Alerts**
|
|
|
|
---
|
|
|
|
### 2. Define Alerting Logic
|
|
- Add **If Node** with conditions:
|
|
- `avg_sentiment_score < -0.4`
|
|
- `num_negative_reviews > 5`
|
|
|
|
---
|
|
|
|
### 3. Craft Alert Message
|
|
- Add a **Set Node** on the True branch:
|
|
🚨 URGENT: Negative Sentiment Spike!
|
|
Product: {{ $json.product_name }}
|
|
Avg Sentiment: {{ $json.avg_sentiment_score }}
|
|
Please investigate immediately.
|
|
|
|
yaml
|
|
Copy code
|
|
|
|
---
|
|
|
|
### 4. Configure Alert Notification
|
|
- Add **Slack Node** connected to alert message.
|
|
- Send to **high-priority channel** (`#ecommerce-alerts`) with `@channel` mentions.
|
|
|
|
---
|
|
|
|
## ✅ Deliverable
|
|
- Workflow detects predefined issues.
|
|
- Sends urgent alerts separately from daily summary.
|
|
|
|
---
|
|
|
|
## 💡 Solution
|
|
- Proactive monitoring is in place.
|
|
- Stakeholders receive alerts for anomalies immediately. |