Analyze error logs with GPT-4o and create GitHub issues plus Slack alerts

Analyze error logs with AI and auto-create GitHub issues with fix suggestions

Who is this for

DevOps engineers, SREs, and development teams who want to automate error monitoring and reduce mean time to resolution (MTTR). Ideal for teams using GitHub for issue tracking and Slack for incident response.

What this workflow does

This workflow automates the entire error management lifecycle - from log ingestion to GitHub issue creation and Slack notification - using GPT-4o-powered root cause analysis. When an application error log is received, it parses the payload, checks for duplicates against existing GitHub issues, generates a structured root cause analysis with fix suggestions, creates a formatted GitHub Issue, and routes Slack notifications by severity. A 30-minute Wait node prevents notification flooding.

How to set up

1. Add your GitHub Personal Access Token (repo scope) credential
2. Add your OpenAI API credential to the AI analysis node
3. Add your Slack OAuth2 credential (chat:write scope) to all Slack nodes
4. Configure n8n Variables: GITHUB_OWNER and GITHUB_REPO
5. Update Slack channel names (#incident / #dev-alerts) to match your workspace
6. Activate the workflow and copy the webhook URL for your application logger

Requirements

• GitHub repository with Personal Access Token (repo scope)
• OpenAI API account with GPT-4o access
• Slack workspace with OAuth2 app installed
• Two Slack channels: one for critical incidents, one for general dev alerts

How to customize

Adjust the duplicate detection score threshold (default 60) in the Code node. Modify the GPT-4o prompt to focus on specific error categories. The Wait node duration (30 minutes) can be tuned to match your alerting policy.

Key features

• Scoring-based duplicate detection (no extra API calls required)
• GPT-4o structured JSON output with graceful fallback parser
• Severity-based Slack routing (#incident vs #dev-alerts)
• Dynamic GitHub labels: bug, auto-generated, environment, and critical
• n8n Variables used for GitHub owner and repo - no hardcoded values

Node List

Total: 14 nodes (+ 6 Sticky Notes)

Sticky Note Compliance

All sticky notes use H2 headings (## ) and follow n8n public guidelines.

Webhook payload schema

{
 "service": "payment-api",
 "level": "CRITICAL",
 "message": "NullPointerException at PaymentProcessor.java:142",
 "stack_trace": "java.lang.NullPointerException...",
 "environment": "production",
 "timestamp": "2025-01-15T09:23:45Z",
 "trace_id": "abc-123-xyz",
 "endpoint": "/api/v2/payments",
 "http_method": "POST",
 "status_code": 500,
 "user_id": "user_98765"
}

Required fields: service, level, message Optional fields: All others - missing values are handled gracefully with fallbacks.

How duplicate detection works

Threshold: Score ≥ 60 → duplicate detected → skip issue creation, notify Slack.

Tags

ai gpt-4 openai github slack error-monitoring devops automation