AutomationFlowsSlack & Telegram › Premium / Error Watch (app_logs → Telegram Alerts)

Premium / Error Watch (app_logs → Telegram Alerts)

Premium / Error watch (app_logs → Telegram alerts). Uses postgres, telegram. Scheduled trigger; 4 nodes.

Cron / scheduled trigger★★☆☆☆ complexity4 nodesPostgresTelegram
Slack & Telegram Trigger: Cron / scheduled Nodes: 4 Complexity: ★★☆☆☆ Added:

This workflow follows the Postgres → Telegram recipe pattern — see all workflows that pair these two integrations.

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json
{
  "name": "Premium / Error watch (app_logs \u2192 Telegram alerts)",
  "nodes": [
    {
      "parameters": {
        "rule": {
          "interval": [
            {
              "field": "minutes",
              "minutesInterval": 5
            }
          ]
        }
      },
      "name": "Cron (every 5m)",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        240,
        300
      ]
    },
    {
      "parameters": {
        "operation": "executeQuery",
        "query": "select id, level, source, message, context, created_at\n  from public.app_logs\n where level = 'error' and created_at > now() - interval '6 minutes'\n order by created_at desc\n limit 20;"
      },
      "name": "Postgres (recent errors)",
      "type": "n8n-nodes-base.postgres",
      "typeVersion": 2.4,
      "position": [
        460,
        300
      ],
      "credentials": {
        "postgres": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "batchSize": 1,
        "options": {}
      },
      "name": "SplitInBatches (1)",
      "type": "n8n-nodes-base.splitInBatches",
      "typeVersion": 3,
      "position": [
        680,
        300
      ]
    },
    {
      "parameters": {
        "chatId": "={{$env.TELEGRAM_OWNER_CHAT_ID}}",
        "text": "\ud83d\uded1 [{{$json.source}}] {{$json.message}}\n<code>{{JSON.stringify($json.context)}}</code>",
        "additionalFields": {
          "parse_mode": "HTML",
          "disable_web_page_preview": true
        }
      },
      "name": "Telegram (alert)",
      "type": "n8n-nodes-base.telegram",
      "typeVersion": 1.1,
      "position": [
        900,
        300
      ],
      "credentials": {
        "telegramApi": {
          "name": "<your credential>"
        }
      }
    }
  ],
  "connections": {
    "Cron (every 5m)": {
      "main": [
        [
          {
            "node": "Postgres (recent errors)",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Postgres (recent errors)": {
      "main": [
        [
          {
            "node": "SplitInBatches (1)",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "SplitInBatches (1)": {
      "main": [
        [
          {
            "node": "Telegram (alert)",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {
    "executionOrder": "v1"
  },
  "active": false,
  "tags": [
    "premium",
    "ops"
  ]
}

Credentials you'll need

Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

Premium / Error watch (app_logs → Telegram alerts). Uses postgres, telegram. Scheduled trigger; 4 nodes.

Source: https://github.com/alexdmitrievi/Podryad_PRO/blob/main/n8n/workflows/04-error-watch.json — original creator credit. Request a take-down →

More Slack & Telegram workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

Memorize Ghost Alerts. Uses postgres, telegram. Scheduled trigger; 4 nodes.

Postgres, Telegram
Slack & Telegram

This workflow performs scheduled health checks on a list of URLs stored in a Google Sheet. Every X minutes, it retrieves the URLs, sends HTTP requests to check their availability, and notifies a Teleg

Telegram, Google Sheets, HTTP Request
Slack & Telegram

Solana Wallet Monitor — Telegram Alerts. Uses httpRequest, telegram. Scheduled trigger; 4 nodes.

HTTP Request, Telegram
Slack & Telegram

⚠️ Heads up: this is satire. The "Hell Yeah!" workflow is a parody of "automate your whole life with AI agents" grindset content. The API endpoints are fictional and the function nodes are illustrativ

HTTP Request, Salesforce, Telegram +4
Slack & Telegram

This workflow tracks a configurable crypto watchlist using the CoinGecko API, sends Telegram alerts when price, % change, or volume-spike conditions are met (with optional RSI filtering), optionally l

HTTP Request, Telegram, Google Sheets +1