The flow
Starts it 1Logic 5Service 6
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Define Incident MetadataSetLogic
- 3Combine Incident & Jira DataMergeLogic
- 4Create Jira Incident TicketJiraService
- 5Format Incident Alert for SlackCodeLogic
- 6Validate Jira Ticket Creation SuccessIfLogic
- 7Alert On-Call Team in SlackSlackService
- 8Log Jira Creation Failures to Error SheetGoogle SheetsService
- 9Generate Incident Timeline ReportCodeLogic
- 10Convert Timeline to Text FileConvert To FileService
- 11Log Incident to Status Tracking SheetGoogle SheetsService
- 12Archive Incident Timeline to DriveGoogle DriveService
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, Google Sheets, Jira, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive, Google Sheets, Jira and Slack accounts. 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. 12 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 12 steps before you point it at anything that matters.