# Assess GitHub bus-factor risk in GitHub with Claude and Slack: n8n workflow

> Started by another system calling it, and works across Slack. It hands the judgement calls to Claude.

Source: https://millionrounds.com/workflow/assess-github-bus-factor-risk-in-github-with-claude-and-slac (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Customer support](https://millionrounds.com/workflows?category=Customer+support#library)

# Assess GitHub bus-factor risk in GitHub with Claude and Slack

Started by another system calling it, and works across Slack. It hands the judgement calls to Claude. 22 steps, 1 branch: large, and worth reading before you trust it with anything live.

Large Calls a model: Claude

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fassess-github-bus-factor-risk-in-github-with-claude-and-slac)

**22 steps** Large: read it before trusting it with anything live

**1** Branch: places the flow splits

**0** Loops or waits

**1** Service it connects to

## The flow

Starts it 4 Model 2 Logic 10 Service 6

The steps in the order they run, from what starts it.

- 1 **On GitHub Push Event** Webhook *Starts it*
- 2 **On Pull Request Merged** Webhook *Starts it*
- 3 **Every Contributor Baseline Scan** Schedule trigger *Starts it*
- 4 **Every Batch Processing Window** Schedule trigger *Starts it*
- 5 **Claude Bus-Factor Model** Lm Chat Anthropic *Model*
- 6 **Normalize Push Signal** Code *Logic*
- 7 **Normalize Review Signal** Code *Logic*
- 8 **Fetch Org Repositories** Http Request *Service*
- 9 **Fetch Buffered Ownership Signals** Http Request *Service*
- 10 **AI Bus-Factor Risk Agent** Agent *Model*
- 11 **Merge Normalized Ownership Signals** Merge *Logic*
- 12 **Fetch Contributor Stats** Http Request *Service*
- 13 **Compute Bus-Factor Risk Scores** Code *Logic*
- 14 **Apply AI Risk Resolution** Code *Logic*
- 15 **Post Signal to Ownership Buffer** Http Request *Service*
- 16 **Normalize Contributor Signal** Code *Logic*
- 17 **Check for Ambiguous Clusters** If *Logic*
- 18 **Merge Risk Results** Merge *Logic*
- 19 **Pass Clear Risk Clusters** Code *Logic*
- 20 **Build Knowledge-Transfer Tasks** Code *Logic*
- 21 **Post to Ticketing System** Http Request *Service*
- 22 **Send Slack Notification** Slack *Service*

## How it's built

- **Starts on:** Another system calling it
- **Steps:** 22, with 1 branch
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** Slack
- **Model:** Claude

## Questions

What does it need to run?

An n8n account, plus your own Slack account, and a key for Claude. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls Claude. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 22 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 22 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fassess-github-bus-factor-risk-in-github-with-claude-and-slac)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[Slack](https://millionrounds.com/workflows?service=Slack#library)

## Workflows like it

Also customer support, with the same services where possible, closest in size first.

- [**AI-powered ticket triage with OpenAI and Postgres** 22 steps · calls a model · Postgres, Slack](https://millionrounds.com/workflow/ai-powered-ticket-triage-with-openai-and-postgres)
- [**Route support tickets with SLA and Slack** 22 steps · Gmail, Slack](https://millionrounds.com/workflow/route-support-tickets-with-sla-and-slack)
- [**AI email support system: Gmail, Gemini, GPT-4, Slack & Google** 23 steps · calls a model · Gmail, Google Drive](https://millionrounds.com/workflow/ai-email-support-system-gmail-gemini-gpt-4-slack-and-google)
- [**Automated Slack IT helpdesk with OpenAI and Supabase** 21 steps · calls a model · Slack, Supabase vectors](https://millionrounds.com/workflow/automated-slack-it-helpdesk-with-openai-and-supabase)
- [**Generate GEO-optimized support replies from Gmail** 21 steps · calls a model · Gmail, Slack](https://millionrounds.com/workflow/generate-geo-optimized-support-replies-from-gmail)
- [**Route and triage multi-channel support tickets with OpenAI** 23 steps · calls a model · Gmail, Google Sheets](https://millionrounds.com/workflow/route-and-triage-multi-channel-support-tickets-with-openai)