Monitor GitHub Deployment Health
Scan GitHub Actions pipelines every 4 hours to assess deployment health, and receive a structured scorecard via email with failure details and recommended actions.
GitHub ActionsDevOps MonitoringPipeline HealthEmail Notifications
What It Does
Runs every 4 hours and scans all your GitHub Actions workflow runs across all repositories. An AI agent classifies the overall deployment health as HEALTHY, DEGRADED, or CRITICAL, generates a per-repository breakdown table, and delivers a structured scorecard to your inbox. Zero failures means a single "All Clear" email to reduce unnecessary noise.
How It Works
- Scheduled Trigger: Fires every 4 hours to initiate the workflow.
- GitHub Node: Fetches all completed workflow runs from the last 4 hours across every repository the authenticated user can access.
- AI Agent: Analyzes the workflow data, counts successes and failures, assigns an overall health status, builds a per-repository breakdown, lists failed workflows, and provides three recommended actions.
- Gmail Node: Delivers the scorecard with the health status in the subject line for at-a-glance triage.
What You Get
| Scorecard Detail | Description |
|---|---|
| Health Status | HEALTHY (zero failures), DEGRADED (non-main branch failures), or CRITICAL (main branch failures) |
| Summary Metrics | Total number of workflows that ran, passed, and failed |
| Breakdown Table | Per-repository status displaying a pass and fail breakdown |
| Failure Log | Detailed list of every failed workflow including the repository name, branch, and timestamp |
| Action Plan | Three specific recommended actions tailored to the detected failure patterns |
Who It Is For
- DevOps engineers and site reliability engineers managing multiple repositories and continuous integration pipelines.
- Tech leads who want deployment awareness without checking GitHub manually throughout the day.
- Engineering managers who need pipeline health visibility across the entire organization.
- On-call engineers who want proactive alerts before end-users report failures.
Setup Guide
- Connect your GitHub account using a Personal Access Token with repository and user read scopes.
- Connect your Gmail account, granting all necessary permissions for ongoing access.
- Publish the workflow to start running automatically on its 4-hour schedule.
- Check your inbox for the first scorecard within 4 hours of publishing.
Customization Options
- Modify the scheduled trigger for hourly monitoring if your team deploys frequently.
- Update the AI agent prompt to define what qualifies as a CRITICAL failure based on your specific team guidelines.
- Add a Slack node in parallel with Gmail to post the scorecard directly to an engineering team channel.
Timezone Note
- The default schedule fires at 12:00 AM, 4:00 AM, 8:00 AM, 12:00 PM, 4:00 PM, and 8:00 PM UTC.
Want to showcase your own workflows?
Become a Needle workflow partner and turn your expertise into recurring revenue.