BotShelf Vampire BOTSHELF VAMPIRE Register

Library · Team · n8n · data-analysis

Workflow n8n Analytics Untested workflow free

Data Analysis — n8n

Summarize pasted tables or CSV snippets into findings, caveats, and what to check next. Analysis only. (n8n workflow recipe (Manual Trigger → LLM → output).)

Id: n8n/data-analysis · Slug: data-analysis · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

What is this

Workflow for n8n. Summarize pasted tables or CSV snippets into findings, caveats, and what to check next. Analysis only. (n8n workflow recipe (Manual Trigger → LLM → output).)

How this runtime fits

This n8n implementation is primarily an AI workflow / agentic workflow for the parent AI Team. Call it a multi-agent workflow only when the graph actually splits agent-like steps.

Parent AI Team: data-analysis · What is an AI Team?

What it does

Summarize pasted tables or CSV snippets into findings, caveats, and what to check next. Analysis only. (n8n workflow recipe (Manual Trigger → LLM → output).)

Who for

Builders working on Analytics jobs who can run n8n themselves.

Need to run

How to use

  1. In n8n: Import from File → workflow.json (or recreate nodes from the sketch).
  2. Add your local LLM credential/HTTP node in place of the placeholder.
  3. Paste the full system prompt into the LLM node.
  4. Execute once with Example in as input. Inspect output; no schedule yet.

Limitations

Test status

Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

Free. No sign-up. The full text is right here. Copy it, or take the file with you.

Download .md How to run it Fork it Results & questions

# n8n Recipe — Data Analysis

## Full system prompt (put in your LLM node)
You are a data analysis desk. Goal: findings from pasted numbers only.

RULES:
- Always emit ALL four OUTPUT sections.
- Never invent row values, dates, weekdays, or metrics not in the paste.
- Quote the exact cell values you use in each Key finding.
- Note blank/missing cells explicitly; do not fill blanks with guesses.
- Do not invent averages; if you cannot compute carefully write "not computed — needs human calc".
- Do not claim deploy/product events caused gold/market moves unless the paste states that link.
- If paste says SAMPLE/synthetic, say so in Dataset snapshot.
- Prefer max 5 accurate findings over 7 wrong ones.
- Do not invent rows. If math is approximate, say so.
- Call out sample size, missing fields, and selection bias.
- No trading/investment advice. No auto-spend recommendations.
- Charts described in text only unless user provides image.

OUTPUT:
1) Dataset snapshot
2) Key findings (max 7)
3) Caveats
4) Next checks / cuts to request

## workflow.json
```json
{
  "name": "BotShelf Library \u2014 Data Analysis",
  "nodes": [
    {
      "parameters": {},
      "id": "1",
      "name": "Manual Trigger",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ]
    },
    {
      "parameters": {
        "values": {
          "string": [
            {
              "name": "system",
              "value": "You are a data analysis desk. Goal: findings from pasted numbers only.\n\nRULES:\n- Always emit ALL four OUTPUT sections.\n- Never invent row values, dates, weekdays, or metrics not in the paste.\n- Quote the exact cell values you use in each Key finding.\n- Note blank/missing cells explicitly; do not fill blanks with guesses.\n- Do not invent averages; if you cannot compute carefully write \"not computed \u2014 needs human calc\".\n- Do not claim deploy/product events caused gold/market moves unless the paste\u2026"
            },
            {
              "name": "user_input",
              "value": "={{$json.input}}"
            }
          ]
        }
      },
      "id": "2",
      "name": "Prepare Prompt",
      "type": "n8n-nodes-base.set",
      "typeVersion": 3,
      "position": [
        260,
        0
      ]
    },
    {
      "parameters": {
        "notice": "Attach your own local LLM node (Ollama/LM Studio HTTP). Do not enable billing cloud nodes without a human budget check."
      },
      "id": "3",
      "name": "LLM Placeholder",
      "type": "n8n-nodes-base.noOp",
      "typeVersion": 1,
      "position": [
        520,
        0
      ]
    }
  ],
  "connections": {
    "Manual Trigger": {
      "main": [
        [
          {
            "node": "Prepare Prompt",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Prepare Prompt": {
      "main": [
        [
          {
            "node": "LLM Placeholder",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "meta": {
    "botshelf_job": "data-analysis",
    "safety": "manual-trigger-only"
  }
}
```

## README safety
- Trigger is Manual only (no cron spend loops in stage 1).
- Replace LLM Placeholder with a local HTTP node to Ollama/LM Studio when ready.
- Do not store API keys in the workflow JSON committed to git; use n8n credentials store.
- No shell nodes that delete files or push to production.

License as listed in the registry: free-use-at-own-risk. Use is at your own risk. BSV does not run it for you. What is open here

Paste:
day,signups,paid
Mon,40,2
Tue,38,1
Wed,22,1
Thu,21,0
Fri,25,1
Note: Wed deploy.
Snapshot: 5 weekdays; Wed deploy coincides with signup drop.
Findings: Signups fell ~45% Wed–Thu vs Mon–Tue; paid sparse (n small).
Caveats: one week; no traffic denominator.
Next: traffic + error logs around deploy.

Stage-1 recipe is manual-trigger only. Add schedules only after you confirm cost controls.

Parent: data-analysis · implementation_id: n8n/data-analysis

teams/data-analysis/n8n (path in the BSV team registry repository) · commit eb87e8e049fdf9908e438305ff827c7b617505b5 · license: free-use-at-own-risk

Structural check: PASS · env: structural (structural only — does not set Verified)

Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.

The BSV n8n team runner builds an importable workflow for this task: manual trigger, local model over HTTP, section check, then you review the result. It saves and sends nothing. Paste the team prompt from the full-text page into prompts/data-analysis.txt.

python make_workflow.py --task data-analysis

n8n team runner →

Not runtime tested by BSV.