Automation library · Alerts and monitoring

Monitor from SSL with Google Sheets and Jira

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

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
3Services it connects to

The flow

Starts it 1Logic 1Service 8

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

  1. 1Cron TriggerCronStarts it
  2. 2HTTP Website CheckHttp RequestService
  3. 3Is Website Down?IfLogic
  4. 4Create Jira IssueJiraService
  5. 5Find Existing Jira IssueJiraService
  6. 6Slack Alert - DownSlackService
  7. 7Close Jira IssueJiraService
  8. 8Log to Google Sheets - DownGoogle SheetsService
  9. 9Slack Alert - RecoveredSlackService
  10. 10Log to Google Sheets - UpGoogle SheetsService

How it's built

Starts on
A clock
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
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 Sheets, 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.