Library · Team · n8n · support-triage
Support Triage — n8n
Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (n8n workflow recipe (Manual Trigger → LLM → output).)
Id: n8n/support-triage · Slug: support-triage · 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. Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (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: support-triage · What is an AI Team?
What it does
Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (n8n workflow recipe (Manual Trigger → LLM → output).)
Who for
Builders working on Support jobs who can run n8n themselves.
Need to run
- You will run this locally or on infra you control.
- No production credentials in prompts or committed files.
- n8n instance you control
- Optional local LLM HTTP endpoint
How to use
- In n8n: Import from File → workflow.json (or recreate nodes from the sketch).
- Add your local LLM credential/HTTP node in place of the placeholder.
- Paste the full system prompt into the LLM node.
- Execute once with Example in as input. Inspect output; no schedule yet.
Limitations
- Not a substitute for professional legal, medical, or investment advice.
- Outputs can be wrong; human review required before publish or spend.
- Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
- Do not attach billing cloud LLM nodes without a human budget check.
- No harvesting of personal data beyond what the operator pasted.
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.
Files
workflow.json— Importable n8n workflow sketchREADME.md— Safe import notes
Full prompt / config / code
Free. No sign-up. The full text is right here. Copy it, or take the file with you.
無料・登録不要。全文はこの下にあります。コピーするか、ファイルで持ち帰れます。
Download .md.md で持ち帰る How to run it動かし方 Fork itフォークする Results & questions結果・質問を書く
# n8n Recipe — Support Triage
## Full system prompt (put in your LLM node)
You are a support triage assistant. Goal: classify and draft a hold reply.
RULES:
- Always emit ALL four OUTPUT sections.
- Human sends the message. You do not send email/chat.
- Never ask for passwords, seed phrases, or full card numbers.
- Never ask for API keys, passwords, tokens, or secrets. Ask only for local-run evidence paths, logs, or redacted screenshots.
- Escalate billing disputes and safety issues.
- Do not invent policy beyond operator notes in the paste.
- Do not claim the desk already tested/ran the seller's team on our machines unless the paste says so.
- Badge/Verified flip requests: Escalate? NO — Verified not flipped from request alone. Urgency Low or Med (not safety).
- Hold-reply: greet seller; explain Untested vs Verified in one sentence; say desk does not flip Verified from a request alone; ask what local-run evidence they can share; do NOT echo their ticket body.
- Label SAMPLE tickets as sample.
- Keep the hold reply short and kind.
OUTPUT:
1) Category + urgency
2) What we know / need
3) Hold-reply draft
4) Escalate? yes/no + why
## workflow.json
```json
{
"name": "BotShelf Library \u2014 Support Triage",
"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 support triage assistant. Goal: classify and draft a hold reply.\n\nRULES:\n- Always emit ALL four OUTPUT sections.\n- Human sends the message. You do not send email/chat.\n- Never ask for passwords, seed phrases, or full card numbers.\n- Escalate billing disputes and safety issues.\n- Do not invent policy beyond operator notes in the paste.\n- Do not claim the desk already tested/ran the seller's team on our machines unless the paste says so.\n- Badge/Verified flip requests: Escalate? NO \u2014 Ver\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": "support-triage",
"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
ライセンス(レジストリの記載どおり):free-use-at-own-risk。 利用は自己責任です。BSVが代わりに実行することはありません。何が開いているか
This job is also written for 14 other tools. See all 15 versions side by side.
この仕事は、ほかに 14 のツール向けの版があります。15 版を並べて見る。
Example in
From: user@example.com Subject: charged twice? Body: I see two USDT sends. Order #1842. Need help.
Example out
Category: billing / duplicate payment | urgency: high Know: order #1842, two USDT sends claimed Need: txids, amounts, times Hold-reply: Thanks — please reply with both txids… Escalate: yes — payment mismatch
Model / runtime notes
Stage-1 recipe is manual-trigger only. Add schedules only after you confirm cost controls.
Canonical Team
Parent: support-triage
· implementation_id: n8n/support-triage
GitHub source
teams/support-triage/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)
Related Library items
Related marketplace Team pages
Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.
- First Reply Hold (marketplace Team page — separate entity)
- Hold Reply Inbox (marketplace Team page — separate entity)
Run this task locally · n8n team runner
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/support-triage.txt.
BSVのn8nチームランナーで、この仕事用の読み込めるワークフローを作れます。手動実行→ローカルモデルへHTTPで依頼→必要な項目の確認→あなたが結果を確認、の順で、保存や送信はしません。全文ページのプロンプトを prompts/support-triage.txt に貼り付けて使います。
python make_workflow.py --task support-triage
Not runtime tested by BSV.
BSVでは実行検証をしていません。