The flow
Starts it 1Logic 8Service 6
The steps in the order they run, from what starts it.
- 1Github TriggerGithub triggerStarts it
- 2Commit Message BreakdownCodeLogic
- 3Check for PR commandsIfLogic
- 4Get task details for PRJiraService
- 5Check for task completed commandIfLogic
- 6Check if PR existsHttp RequestService
- 7Get Task Details without PR.JiraService
- 8Invalid commit messageStop And ErrorLogic
- 9Check whether a PR already existsIfLogic
- 10Check if task existsIfLogic
- 11Check if task existIfLogic
- 12Request to create PRHttp RequestService
- 13Update the task status without PRJiraService
- 14JIRA Task does not existStop And ErrorLogic
- 15Update task status after PRJiraService
How it's built
- Starts on
- An event in a connected app
- Steps
- 15, with 5 branches
- Size
- Medium: a working afternoon
- Connects to
- Jira
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Jira 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. 15 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 15 steps before you point it at anything that matters.