📊 Detect team burnout with Groq AI analysis of GitHub activity for wellness reports

⚡ 98 views · 📊 Market Research & Insights

💡 Pro Tip — If you need GitHub data beyond what the REST API gives you, ScraperNode has a repository scraper that extracts metadata at scale without token rate limits.

View All Scrapers

Description

Team Wellness - AI Burnout Detector Agent devex github

🎯 Demo

Demo

output

output

output

How it works

🎯 Overview

A comprehensive n8n workflow that analyzes developer workload patterns from GitHub repositories to detect potential software engineering team burnout risks and provide actionable team wellness recommendations. This workflow automatically monitors team activity patterns, analyzes them using AI, and provides professional wellness reports with actionable recommendations which will automate GitHub issue creation and do email notifications for critical alerts.

✨ Features

🏗️ Architecture

1. Data Collection Layer

2. Pattern Analysis Engine

3. AI Analysis Layer

📊 Sample Output

# 📊 Team Health Report

## 📝 Summary
Overall, the team is maintaining a healthy delivery pace, but there are emerging signs of workload imbalance due to increased after-hours activity.

## 🔢 Health Score
- **Value:** 68 / 100
- **Confidence:** 87%
- **Limitations:** Based solely on commit and PR activity; meeting load and non-code tasks not captured.

## 🔍 Observed Patterns
- ⏰ **After-hours activity**
  - 29% of commits occurred between 10pm–1am (baseline: 12%).
  - Confidence: 0.90

## ⚠️ Systemic Risks
- Sustained after-hours work may indicate creeping burnout risk.
  - Evidence: 3 consecutive weeks of elevated late-night commits.
  - Confidence: 0.85

## ✅ Recommendations
- 📌 Facilitate a team discussion on workload distribution and sprint commitments. *(Priority: Medium)*
- 🔔 Introduce automated nudges discouraging late-night commits. *(Priority: Low)*
- 🛠️ Rotate PR review responsibilities or adopt lightweight review guidelines. *(Priority: High)*

🚀 Quick Start

Prerequisites

Setup Instructions

  1. Import Workflow

    # Import the workflow JSON file into your n8n instance

  2. Configure Credentials

    • GitHub API: Create a personal access token with repo access
    • Groq API: Get your API key from Groq Console
    • Gmail OAuth2: Set up OAuth2 credentials for email notifications

  3. Update Configuration

    {
  "repoowner": "your-github-username",
  "reponame": "your-repository-name",
  "period": 7,
  "emailreport": "your-email@company.com"
}

  4. Test Workflow

    • Run the workflow manually to verify all connections
    • Check that data is being fetched correctly
    • Verify AI analysis is working

  5. Schedule Automation

    • Enable the schedule trigger for weekly reports
    • Set up monitoring for critical alerts

🔧 Configuration

Configuration Node Settings

AI Model Settings

📈 Metrics Analyzed

Repository-Level Metrics

Work Pattern Signals

Developer-Level Activity

🛡️ Privacy & Ethics

Professional Guardrails

Data Protection

🔄 Workflow Nodes

Core Nodes

  1. Schedule Trigger: Weekly automation (configurable)
  2. Config: Repository and email configuration
  3. Github Get Commits: Fetches commit history
  4. Github Get Workflows: Retrieves workflow runs
  5. Get Prs: Pulls pull request data
  6. Analyze Patterns Developer: JavaScript pattern analysis
  7. AI Agent: Groq-powered analysis with guardrails
  8. Update Github Issue: Creates wellness tracking issues
  9. Send a message in Gmail: Email notifications

Data Flow

Schedule Trigger → Config → Github APIs → Pattern Analysis → AI Agent → Actions

🚨 Alert Levels (Optional and Prompt configurable)

Critical Alerts (Health Score < 90)

Warning Alerts (Health Score 90-95)

Normal Reports (Health Score > 95)

🔧 Troubleshooting

Common Issues

  1. GitHub API Rate Limits

    • Solution: Use authenticated requests, implement rate limiting
    • Check: API token permissions and repository access

  2. AI Analysis Failures

    • Solution: Verify Groq API key, check model availability
    • Check: Input data format and prompt structure

  3. Email Notifications Not Sending

    • Solution: Verify Gmail OAuth2 setup, check email permissions
    • Check: SMTP settings and authentication

  4. Workflow Execution Errors

    • Solution: Check node connections, verify data flow
    • Check: Error logs and execution history

🤝 Contributing

Development Setup

  1. Fork the repository link above demo part
  2. Create a feature branch
  3. Make your changes
  4. Test thoroughly
  5. Submit a pull request

Testing

📄 License

This project is licensed under the MIT License

🙏 Acknowledgments

📞 Support

Getting Help

Contact

⚠️ Important: This tool is designed for team wellness monitoring and should be used responsibly. Always respect team privacy and use the insights constructively to improve team health and productivity.

🔗 Nodes Used

GitHub, HTTP Request, Schedule Trigger, AI Agent, Groq Chat Model

📥 Import

Download workflow.json and import into n8n: Workflow menu → Import from File

📖 Importing guide · 🔑 Credential setup