The flow
Starts it 1Logic 12Service 4
The steps in the order they run, from what starts it.
- 1Hourly TriggerSchedule triggerStarts it
- 2Create Jira IssueJiraService
- 3Fetch Raw LogsHttp RequestService
- 4Has Logs?IfLogic
- 5Parse & Flatten LogsCodeLogic
- 6Generate SummaryCodeLogic
- 7Batch LogsSplit In BatchesLogic
- 8Format Summary EmailSetLogic
- 9Deduplicate BatchCodeLogic
- 10Daily Summary EmailEmail SendService
- 11Any New Errors?IfLogic
- 12Assess SeverityCodeLogic
- 13Critical Errors?IfLogic
- 14Prepare Jira IssueCodeLogic
- 15Critical Alert EmailEmail SendService
- 16Rate Limit WaitWaitLogic
- 17Collect Issue KeysMergeLogic
How it's built
- Starts on
- A clock
- Steps
- 17, with 3 branches, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Email, Jira
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email and Jira 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. 17 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 17 steps before you point it at anything that matters.