The flow
Starts it 1Service 18
The steps in the order they run, from what starts it.
- 1Create a fileGitlab ToolService
- 2Delete a fileGitlab ToolService
- 3Edit a fileGitlab ToolService
- 4Get a fileGitlab ToolService
- 5List filesGitlab ToolService
- 6Create an issueGitlab ToolService
- 7Create a comment on an issueGitlab ToolService
- 8Edit an issueGitlab ToolService
- 9Get an issueGitlab ToolService
- 10Lock an issueGitlab ToolService
- 11Create a releaseGitlab ToolService
- 12Delete a releaseGitlab ToolService
- 13Get a releaseGitlab ToolService
- 14Get many releasesGitlab ToolService
- 15Update a releaseGitlab ToolService
- 16Get a repositoryGitlab ToolService
- 17Get issues of a repositoryGitlab ToolService
- 18Get a user's repositoriesGitlab ToolService
- 19GitLab Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 19
- 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 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. 19 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 19 steps before you point it at anything that matters.