Automation library · Alerts and monitoring

Website downtime alert with LINE and Supabase

Started by a clock, and works across Supabase. It hands the judgement calls to OpenAI. 12 steps, 1 branch, 2 loops or waits: a working afternoon to understand properly.

MediumCalls a model: OpenAI

12 stepsMedium: a working afternoon
1Branch: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 1Model 2Logic 6Service 3

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2OpenAI GPT-4o MiniLm Chat Open AiModel
  3. 3Get MonitorsUptime RobotService
  4. 4Filter Down MonitorsCodeLogic
  5. 5Loop Over MonitorsSplit In BatchesLogic
  6. 6If DownIfLogic
  7. 7Save to SupabaseSupabaseService
  8. 8Filter Status 9FilterLogic
  9. 9LLM Message FormatChain LlmModel
  10. 10Escape NewlinesCodeLogic
  11. 11Send to LINEHttp RequestService
  12. 12Wait 30 MinWaitLogic

How it's built

Starts on
A clock
Steps
12, with 1 branch, 2 loops or waits
Size
Medium: a working afternoon
Connects to
Supabase
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Supabase account, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

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.

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