The flow
Starts it 1Logic 6Service 9
The steps in the order they run, from what starts it.
- 1When Issue Opened in GitHubGithub triggerStarts it
- 2Filter Opened IssuesCodeLogic
- 3Fetch Open GitHub IssuesGithubService
- 4Prepare Issue Data for AICodeLogic
- 5Post to Claude Duplicate CheckHttp RequestService
- 6Extract Data from Claude JSONCodeLogic
- 7Check If Duplicate IssueIfLogic
- 8Tag Issue as DuplicateGithubService
- 9Assign AI Labels to IssueGithubService
- 10Notify Duplicate in CommentsGithubService
- 11Determine Need for Repro InfoIfLogic
- 12Retrieve Original GitHub IssueGithubService
- 13Request Repro Steps in CommentsGithubService
- 14Update Original Issue SummaryCodeLogic
- 15Revise Original IssueGithubService
- 16Add Merge Info to CommentsGithubService
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, with 2 branches
- 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. 16 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.
Before you run itNothing 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 16 steps before you point it at anything that matters.