Automation library · Alerts and monitoring

Monitor website uptime and latency with Slack and Data Tables

Started by a clock, and works across Slack and n8n data table. 58 steps, 4 branches, 1 loop or waits: large, and worth reading before you trust it with anything live.

Large

Download free
58 stepsLarge: read it before trusting it with anything live
4Branches: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 2Logic 36Service 20

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

  1. 1Run Scheduled Uptime ChecksSchedule triggerStarts it
  2. 2Send Daily Uptime SummarySchedule triggerStarts it
  3. 3Prepare Scheduled Check RunCodeLogic
  4. 4Prepare Daily Summary RunCodeLogic
  5. 5Configure Uptime MonitorsSetLogic
  6. 6Build Uptime ConfigurationCodeLogic
  7. 7Initialize Monitor State TableData TableService
  8. 8Initialize Check History TableData TableService
  9. 9Initialize Incidents TableData TableService
  10. 10Initialize Notification LedgerData TableService
  11. 11Build Uptime Storage ContextCodeLogic
  12. 12Route Uptime RunSwitchLogic
  13. 13Validate and Expand MonitorsCodeLogic
  14. 14Load Daily Check HistoryData TableService
  15. 15Prepare Configuration ErrorCodeLogic
  16. 16Loop Enabled MonitorsSplit In BatchesLogic
  17. 17Calculate Daily StatisticsCodeLogic
  18. 18Prepare Scheduled Check SummaryCodeLogic
  19. 19Prepare HTTP Request ContextCodeLogic
  20. 20Prepare Daily Summary MessageCodeLogic
  21. 21Perform HTTP Health CheckHttp RequestService
  22. 22Merge HTTP Context and ResponseMergeLogic
  23. 23Send Daily Slack SummarySlackService
  24. 24Normalize HTTP ResultCodeLogic
  25. 25Run Retention CleanupCodeLogic
  26. 26Prepare Normalized Check ContextCodeLogic
  27. 27Prepare Retention CutoffsCodeLogic
  28. 28Find Existing CheckData TableService
  29. 29Delete Old Check HistoryData TableService
  30. 30Prepare Check History RowCodeLogic
  31. 31Delete Old Recovered IncidentsData TableService
  32. 32Insert Check HistoryData TableService
  33. 33Delete Old Sent NotificationsData TableService
  34. 34Restore Check ContextCodeLogic
  35. 35Delete Old NotificationsData TableService
  36. 36Load Prior Monitor StateData TableService
  37. 37Prepare Retention SummaryCodeLogic
  38. 38Prepare Prior State ContextCodeLogic
  39. 39Prepare Daily Summary OutputCodeLogic
  40. 40Prior State Exists?IfLogic
  41. 41Prepare Existing Monitor StateCodeLogic
  42. 42Prepare Initial Monitor StateCodeLogic
  43. 43Merge Prior State BranchesCodeLogic
  44. 44Evaluate Monitor StateCodeLogic
  45. 45Upsert Monitor StateData TableService
  46. 46Restore Post-State ContextCodeLogic
  47. 47Prepare Incident RecordCodeLogic
  48. 48Should Persist IncidentIfLogic
  49. 49Persist IncidentData TableService
  50. 50Restore Notification ContextCodeLogic
  51. 51Prepare Notification EventCodeLogic
  52. 52Find Existing NotificationData TableService
  53. 53Should Send NotificationIfLogic
  54. 54Create Pending NotificationData TableService
  55. 55Restore Pending Notification ContextCodeLogic
  56. 56Group Slack AlertsCodeLogic
  57. 57Send Grouped Slack AlertSlackService
  58. 58Record Notification ResultData TableService

How it's built

Starts on
A clock
Steps
58, with 4 branches, 1 loop or waits
Size
Large: read it before trusting it with anything live
Connects to
Slack, n8n data table
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 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?

Take your time. At 58 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.

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