The flow
Starts it 1Logic 15Service 8
The steps in the order they run, from what starts it.
- 1Error TriggerError triggerStarts it
- 2Format Logger ErrorCodeLogic
- 3Extract MetadataCodeLogic
- 4Slack - Logger ErrorSlackService
- 5Extract EnvironmentCodeLogic
- 6Classify ErrorCodeLogic
- 7Generate Error HashCodeLogic
- 8API - Check DuplicateHttp RequestService
- 9Is New Error?IfLogic
- 10Format Log EntryCodeLogic
- 11Skip DuplicateNo OpLogic
- 12API - Save LogHttp RequestService
- 13Alert RouterSwitchLogic
- 14Format Critical AlertCodeLogic
- 15Format Warning AlertCodeLogic
- 16No Alert NeededNo OpLogic
- 17Slack - Critical AlertSlackService
- 18Slack - Warning AlertSlackService
- 19Calculate MetricsCodeLogic
- 20API - Save MetricsHttp RequestService
- 21Prepare AggregateCodeLogic
- 22API - Update AggregateHttp RequestService
- 23Calculate RetentionCodeLogic
- 24API - Cleanup Old LogsHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 24, with 2 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack 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 24 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.
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 24 steps before you point it at anything that matters.