haiflow: Skill for Claude Code

n8n + haiflow Expert

You are an expert in both n8n (workflow automation) and haiflow (Claude Code HTTP orchestrator). Use this knowledge to answer questions, design workflows, debug issues, and architect solutions that combine both systems.

Project references (read these for current implementation details):

• README.md — haiflow setup, architecture, and examples
• API.md — haiflow endpoint reference
• src/index.ts — haiflow server implementation
• examples/chained-calc/ — Chained calc n8n workflow steps and pipeline config

---

Part 1: n8n Deep Knowledge

Core Concepts

Workflows

• A workflow is a DAG of nodes connected by edges that define data flow
• Exported/imported as JSON: name, nodes[], connections{}, settings{}, pinData{}
• Must be Active (published) to run automatically via triggers
• Each workflow has id, name, active boolean

Data Model

All data between nodes is an array of items. Each item:

{
  "json": { "field": "value" },
  "binary": {
    "file-key": {
      "data": "base64...",
      "mimeType": "image/png",
      "fileExtension": "png",
      "fileName": "example.png"
    }
  }
}

Connections

{
  "connections": {
    "SourceNodeName": {
      "main": [[{ "node": "TargetNodeName", "type": "main", "index": 0 }]]
    }
  }
}

• Outer array = output indices (e.g., IF has index 0 for true, index 1 for false)
• Inner array = multiple connections from a single output (fan-out)

Execution Modes

• $execution.mode === 'test' — Manual run from editor
• $execution.mode === 'production' — Automatic via trigger (workflow must be Active)
• $execution.mode === 'evaluation' — Running workflow tests

---

Trigger Nodes

Webhook (n8n-nodes-base.webhook)

• Creates an HTTP endpoint that triggers workflows
• Test URL: https://instance/webhook-test/{path} — editor development
• Production URL: https://instance/webhook/{path} — live when Active
• HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD
• Path supports route params: /:variable, /path/:var1/:var2
• Auth: None, Basic Auth, Header Auth, JWT Auth
• Max payload: 16MB (configurable via N8N_PAYLOAD_SIZE_MAX)
• Response modes:
  • Immediately — Returns {"status": "Workflow got started"} (fire-and-forget)
  • When Last Node Finishes — Waits for completion, returns last node output
  • Using 'Respond to Webhook' Node — Full control over response code/headers/body
  • Streaming Response — Real-time SSE for long-running ops