Automation library · Customer support

Error log monitor with SSH and Slack

Started by a clock, and works across Jira and Slack. 10 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 2Logic 4Service 4

The steps in the order they run, from what starts it.

  1. 1Manual TriggerManual triggerStarts it
  2. 2Schedule Every 5minSchedule triggerStarts it
  3. 3Set ConfigSetLogic
  4. 4Read Error LogsSshService
  5. 5Wait For All LogsWaitLogic
  6. 6Parse LogsCodeLogic
  7. 7IF Critical ErrorIfLogic
  8. 8Send Slack AlertSlackService
  9. 9Create Jira TicketJiraService
  10. 10Send Non-Critical AlertSlackService

How it's built

Starts on
A clock
Steps
10, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Jira, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Jira and Slack 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. 10 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.

Before you run it

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 10 steps before you point it at anything that matters.