Telegram bot alert feeding off Start Security page (https://start9.com/security-status)

ruxal · November 4, 2026, 6:43pm

How it works:

Import the JSON into n8n.
In the Telegram node, create their own bot credential.
In the Settings node, fill in:
- chatId
- packages (optional): e.g. Core Lightning, LNbits; empty means every service on the page
- includeStartTunnel: true/false
Activate it. It runs every hour at :07 and sends one “started” message with what’s still open, then only new entries and status changes. Each message includes the severity, Start9’s “What to do” advice and a link. If the page can’t be read, it sends one , then when it works again.

Tests:

I ran it against today’s live Start9 page in 8 scenarios: first run (a long list gets split over two messages), no repeats when nothing changed, a status change, a new entry, a broken page with no repeated warning, the page coming back, and the package filter.
It imports cleanly into a fresh n8n 2.x.

Not tested yet: a real run with a bot actually sending messages. For that, you can import it into your n8n, inactive and with your bot. You’d press “Test workflow” once and see the “started” message in Telegram.

https://gist.github.com/alru78/815d7d37b7400bfa1408a81dc6600d8f

README.md

# Start9 security watch for n8n (Telegram)

An n8n workflow that watches Start9's public [security status page](https://start9.com/security-status/)
and sends you a Telegram message when:

- Start9 lists a **new** security issue that affects StartOS, StartTunnel or a service you care about
- the status of an entry **changes** (for example *in progress* → *fixed in 1.6.2:4*)
- the page can't be read any more (one ⚠️ message, then ✅ when it works again)

Every message includes the severity, the affected items with their status, Start9's "What to do" advice,

This file has been truncated. show original

build-alerts.js

// Start9 security status → Telegram (community version, no SSH, no secrets in the workflow).
// Fetches https://start9.com/security-status/, diffs it against workflow staticData and returns
// one item per Telegram message. Runs as an n8n Code node ("Run Once for All Items").
const START9_URL = 'https://start9.com/security-status/';
const settings = $('Settings').first().json;
const packages = String(settings.packages || '').split(',').map((s) => s.trim()).filter(Boolean);
const platforms = ['StartOS', ...(settings.includeStartTunnel ? ['StartTunnel'] : [])];

const decode = (s) => String(s ?? '').replace(/<[^>]+>/g, '').replace(/&#39;/g, "'").replace(/&quot;/g, '"')
  .replace(/&lt;/g, '<').replace(/&gt;/g, '>').replace(/&amp;/g, '&').replace(/\s+/g, ' ').trim();

This file has been truncated. show original

start9-security-watch.json

{
  "name": "Start9 security watch (Telegram)",
  "nodes": [
    {
      "parameters": {
        "content": "## Start9 security watch → Telegram\n\nChecks https://start9.com/security-status/ every hour and sends a Telegram message when Start9 lists a **new issue** or **changes a status** (e.g. in progress → fixed).\n\n**Setup (2 minutes)**\n1. **Telegram node:** create a *Telegram API* credential with your bot token (from @BotFather).\n2. **Settings node:**\n   - `chatId`: your chat ID (message @userinfobot, or use your group/channel ID)\n   - `packages`: optional, comma-separated service names exactly as Start9 lists them (e.g. `Core Lightning, LNbits, Nextcloud`). Empty = every service.\n   - `includeStartTunnel`: true if you run StartTunnel\n3. **Activate** the workflow. The first scheduled run sends one \"started\" message with what is still open; after that only changes.\n\nNotes\n- State is kept in the workflow's static data, which n8n only saves on *scheduled* (active) runs. \"Test workflow\" runs always behave like a first run.\n- If Start9 changes the page layout you get one ⚠️ message, and ✅ when it parses again.\n- Nothing is installed or read on your server; it only fetches the public page.\n",
        "height": 620,
        "width": 520
      },
      "id": "e05dae7b-866f-429a-9393-a161763e96b2",

This file has been truncated. show original

There are more than three files. show original

Telegram example:

Start9: Compromised eMudhra certificate authorities

Critical · overall in progress · status changed

Core Lightning (cranky-malls 26.6.10:0 ): fixed in 26.6.10:0 (was: Monitoring)

What to do: Update StartOS to 0.4.0.3 or later, StartTunnel to 1.4.0 or later, and the services marked fixed. Fixes for the services marked in progress are on the way, and those marked monitoring will be updated once a fixed release of them is available. Update StartWRT when its next release arrives.