The flow
Starts it 1Model 1Logic 8Service 8
The steps in the order they run, from what starts it.
- 1When GitLab MR Event OccursGitlab triggerStarts it
- 2Check MR for RN InputsIfLogic
- 3Check Release LabelIfLogic
- 4Read RSS FeedRss Feed ReadService
- 5Post Linear Labels to GraphQLHttp RequestService
- 6Filter Labels Starting With v2CodeLogic
- 7Set Various FieldsSetLogic
- 8Parse Linear Version LabelsCodeLogic
- 9Post Linear Issues to GraphQLHttp RequestService
- 10Check Linear Issues ExistIfLogic
- 11Generate Summary with LinksCodeLogic
- 12Generate Summary with Linear DetailsCodeLogic
- 13Post No Issues Note to GitLabHttp RequestService
- 14Post Summary to GitLab MRHttp RequestService
- 15Claude AI MessageAnthropicModel
- 16Update GitLab MR LabelHttp RequestService
- 17Post AI Suggestions to GitLabHttp RequestService
- 18Fetch GitLab MR LabelsHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 18, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- RSS
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own RSS 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. 18 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 18 steps before you point it at anything that matters.