AutomationFlowsWeb Scraping › Flowki · Täglicher Report (zeitplan → Daten → Zusammenfassung) — Grundgerüst

Flowki · Täglicher Report (zeitplan → Daten → Zusammenfassung) — Grundgerüst

FlowKI · Täglicher Report (Zeitplan → Daten → Zusammenfassung) — Grundgerüst. Uses httpRequest. Scheduled trigger; 4 nodes.

Cron / scheduled trigger★★★★☆ complexity4 nodesHTTP Request
Web Scraping Trigger: Cron / scheduled Nodes: 4 Complexity: ★★★★☆ Added:

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": "FlowKI \u00b7 T\u00e4glicher Report (Zeitplan \u2192 Daten \u2192 Zusammenfassung) \u2014 Grundger\u00fcst",
  "nodes": [
    {
      "parameters": {},
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        -440,
        0
      ],
      "id": "ab000000-0000-4000-8000-000000000001",
      "name": "Zeitplan (z.B. 8:00 Uhr)"
    },
    {
      "parameters": {
        "url": "https://api.example.com/kennzahlen",
        "options": {}
      },
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        -200,
        0
      ],
      "id": "ab000000-0000-4000-8000-000000000002",
      "name": "Kennzahlen abrufen"
    },
    {
      "parameters": {
        "jsCode": "// Hier die abgerufenen Daten zu einem kurzen Report zusammenfassen.\n// Beispiel:\nreturn [{ json: { report: 'Tages-Report: ' + $input.all().length + ' Datens\u00e4tze.' } }];"
      },
      "type": "n8n-nodes-base.code",
      "typeVersion": 2,
      "position": [
        40,
        0
      ],
      "id": "ab000000-0000-4000-8000-000000000003",
      "name": "Report zusammenfassen"
    },
    {
      "parameters": {},
      "type": "n8n-nodes-base.noOp",
      "typeVersion": 1,
      "position": [
        280,
        0
      ],
      "id": "ab000000-0000-4000-8000-000000000004",
      "name": "Report senden (Mail/Discord)"
    }
  ],
  "connections": {
    "Zeitplan (z.B. 8:00 Uhr)": {
      "main": [
        [
          {
            "node": "Kennzahlen abrufen",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Kennzahlen abrufen": {
      "main": [
        [
          {
            "node": "Report zusammenfassen",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Report zusammenfassen": {
      "main": [
        [
          {
            "node": "Report senden (Mail/Discord)",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "flowki": "Grundgeruest \u2014 Datenquelle + Report-Logik im Code-Knoten anpassen, Versand-Knoten anbinden."
  }
}
Pro

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

About this workflow

FlowKI · Täglicher Report (Zeitplan → Daten → Zusammenfassung) — Grundgerüst. Uses httpRequest. Scheduled trigger; 4 nodes.

Source: https://github.com/gh0stOo/n8n-workflows-dsgvo-de/blob/main/workflows/11-taeglicher-report.json — original creator credit. Request a take-down →

More Web Scraping workflows → · Browse all categories →

Related workflows

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

Web Scraping

Birthday Automation - Production (Fixed). Uses stopAndError, httpRequest, emailSend, bannerbear. Scheduled trigger; 86 nodes.

Stop And Error, HTTP Request, Email Send +1
Web Scraping

This template runs two scheduled workflows to govern Microsoft Entra ID (Azure AD) guest accounts by detecting stale users via Microsoft Graph, staging deletions in SharePoint with a 72-hour window, n

Microsoft SharePoint, Microsoft Teams, Microsoft Entra +1
Web Scraping

Jira-Allure-Auto-Qa. Uses httpRequest, jira. Scheduled trigger; 68 nodes.

HTTP Request, Jira
Web Scraping

Spotify-Sync-Surrealdb-V1. Uses httpRequest, n8n-nodes-surrealdb, spotify. Scheduled trigger; 62 nodes.

HTTP Request, N8N Nodes Surrealdb, Spotify
Web Scraping

As n8n instances scale, teams often lose track of sub-workflows—who uses them, where they are referenced, and whether they can be safely updated. This leads to inefficiencies like unnecessary copies o

HTTP Request, n8n, N8N Trigger +1