The flow
Starts it 1Service 20
The steps in the order they run, from what starts it.
- 1Get an issue changelogJira ToolService
- 2Create an issueJira ToolService
- 3Delete an issueJira ToolService
- 4Get an issueJira ToolService
- 5Get many issuesJira ToolService
- 6Create an email notification for an issueJira ToolService
- 7Get the status of an issueJira ToolService
- 8Update an issueJira ToolService
- 9Add an attachment to an issueJira ToolService
- 10Get an attachment from an issueJira ToolService
- 11Get many issue attachmentsJira ToolService
- 12Remove an attachment from an issueJira ToolService
- 13Add a commentJira ToolService
- 14Get a commentJira ToolService
- 15Get many commentsJira ToolService
- 16Remove a commentJira ToolService
- 17Update a commentJira ToolService
- 18Create a userJira ToolService
- 19Delete a userJira ToolService
- 20Get a userJira ToolService
- 21Jira Software Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 21
- Size
- Large: read it before trusting it with anything live
- 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?
Take your time. At 21 steps it is large: read it before trusting it with anything live.
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 21 steps before you point it at anything that matters.