n8n Workflow: GitHub Bus-Factor Risk with Claude, Tickets & Slack
n8n Workflow: GitHub Bus-Factor Risk with Claude, Tickets & Slack
Regular price
£26.99
Regular price
£26.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n Workflow: GitHub Bus-Factor Risk with Claude, Tickets & Slack
Regular price
£26.99
Regular price
£26.99
Sale price
Unit price
/
per
Detect GitHub “bus-factor” risk automatically—and turn it into Claude-reviewed tickets and Slack updates
This n8n workflow analyzes GitHub push activity, merged pull requests, and contributor baselines to identify repositories/components with elevated bus-factor risk. It batches ownership signals, resolves borderline cases with Anthropic Claude, then creates or updates knowledge-transfer tasks via an HTTP ticketing API and posts a clear summary to Slack.
What this workflow does
- Ingest GitHub signals: Receives GitHub push and pull_request webhooks, and also runs a scheduled GitHub API scan to collect contributor statistics.
- Normalize ownership data: Converts commit/PR activity and contributor stats into a shared “ownership-signal” structure containing repo, component, contributor, and timestamp fields.
- Batch through an external buffer: Sends each normalized ownership signal to an external ownership-buffer API for later batch processing.
- Compute risk weekly: On a weekly schedule, fetches the buffered window and computes metrics such as commit-concentration and active-contributor counts per repo/component.
- Route confident outcomes: Clearly healthy and clearly critical clusters are routed directly.
- Use Claude for ambiguous cases: Borderline clusters are classified by an Anthropic Claude agent as critical-risk or acceptable.
- Create tickets + notify Slack: Merges resolved results, creates/updates critical-risk knowledge-transfer documentation tasks via HTTP API, and posts a summary message to Slack.
Use cases
- SaaS teams monitoring GitHub repositories to prevent “single-person” maintenance risk.
- Automation engineers generating repeatable bus-factor audits without manual spreadsheets.
- Platforms teams triggering knowledge-transfer workstreams when contributors become too concentrated.
Technical details
-
GitHub webhooks for
pushandpull_requestevents - HTTP Header Auth using a GitHub PAT for GitHub API access
- Nodes/blocks: if, code, merge, slack, webhook, sticky note
- External ownership-buffer API for batching ownership signals
- Anthropic Claude for classification of ambiguous risk clusters
