The flow
Starts it 2Model 3Logic 6Service 4
The steps in the order they run, from what starts it.
- 1When Executed by Another WorkflowExecute Workflow triggerStarts it
- 2Get Latest IssuesTool WorkflowModel
- 3Add Issue CommentTool WorkflowModel
- 4Get Issue CommentsTool WorkflowModel
- 5OperationSwitchLogic
- 6Github MCP ServerMcp triggerStarts it
- 7Get Many IssuesGithubService
- 8Get Single IssueGithubService
- 9Create CommentGithubService
- 10Simplify IssuesSetLogic
- 11Get CommentsHttp RequestService
- 12Get ResponseSetLogic
- 13Aggregate ResultsAggregateLogic
- 14Simplify CommentsSetLogic
- 15Aggregate CommentsAggregateLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 15, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- GitHub
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 15 steps is enough that you should read each one before running it.
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.
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 15 steps before you point it at anything that matters.