The flow
Starts it 1Logic 4Service 5
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2API to Check existing merge requestHttp RequestService
- 3Is ExistsIfLogic
- 4Create New Merge RequestHttp RequestService
- 5Loop Over ItemsSplit In BatchesLogic
- 6Add Custom Notes To Merge RequestHttp RequestService
- 7API to CLOSE existing Merge RequestHttp RequestService
- 830 secs wait to approve merge request and pipeline to finish1WaitLogic
- 9setValueForMergeSetLogic
- 10Merge When Pipeline SucceedsHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 10, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. 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. 10 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 10 steps before you point it at anything that matters.