Diag n8n
Turning official n8n tutorials into a Hood2 dependency map
Official n8n tutorials are a useful starting point because they are small, recognizable, and already teach the right concepts: create a workflow, call an API, branch, configure credentials, and test an AI agent.
Diag n8n uses those tutorials as a clean demo for Hood2.
Instead of treating each tutorial as a flat link, the wrapper turns it into a node in a learning and operations graph:
Tutorials
Foundation
Quickstart
First Workflow
AI
Chat Agent
Operations
n8n
Local Instance
Tutorial Resources
NASA API
AI Model Credential
Three tutorials are enough to show the pattern
The first map uses three official n8n tutorials:
- Quickstart proves the local editor and runtime loop.
- First Workflow introduces an external HTTP API and branching.
- AI Chat Agent introduces model credentials and AI workflow readiness.
Each tutorial has a different dependency shape.
Quickstart only needs local n8n:
Quickstart -> Local Instance:local_n8n_ready
First Workflow depends on both learning order and an external service:
First Workflow -> Quickstart:runnable
First Workflow -> Local Instance:local_n8n_ready
First Workflow -> NASA API:api_reachable
Chat Agent is blocked by credential setup:
Chat Agent -> Local Instance:local_n8n_ready
Chat Agent -> AI Model Credential:credential_configured
Why this matters
Tutorial pages explain what to do. Hood2 can remember what each step depends on.
That means the same structure can later become executable:
- start local n8n
- seed tutorial workflows
- check external APIs
- verify credentials
- import or export workflow fixtures
- explain why a tutorial cannot run yet
The current Diag n8n version is intentionally read-only, but the model is already useful. It shows the separation of responsibilities:
- n8n owns workflow editing and execution.
- Hood2 owns hierarchy, prerequisites, dependency links, and operational checks.
- Diag n8n presents that map in a product-specific UI.
That is the core product story: learn with n8n, then operate the growing workflow estate with structure.