The flow
Starts it 1Logic 8Service 5
The steps in the order they run, from what starts it.
- 1Daily TriggerSchedule triggerStarts it
- 2Certification URL ConfigCodeLogic
- 3Split In BatchesSplit In BatchesLogic
- 4Scrape Requirement DataScrapegraph AiService
- 5Scrape Error?IfLogic
- 6Fetch Previous DataGitlabService
- 7Merge Current & PreviousMergeLogic
- 8Detect ChangesCodeLogic
- 9Requirement Changed?IfLogic
- 10Prepare GitLab FileSetLogic
- 11Log No-Change IssueGitlabService
- 12Save Updated RequirementGitlabService
- 13Craft Alert MessageSetLogic
- 14Send a messageSlackService
How it's built
- Starts on
- A clock
- Steps
- 14, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- GitLab, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitLab and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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. 14 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 14 steps before you point it at anything that matters.