excalidash-n8n-workflow-diagrammer

Provide the exported JSON and the Skill maps nodes[] entries to shapes and connections{} outputs to labeled edges, then reshapes it with convert_diagram_type into a left-to-right flowchart. Branch index 0 becomes the true output and index 1 becomes false, while retryOnFail and continueOnFail settings become retry loops and error lanes.

Describe the trigger, ordered processing nodes, and failure behavior; the Skill draws the happy path straight across the center and places retry loops, error branches, dead-letter sinks, observability taps, and fallback routes each in their own separated lane. Every retry edge is labeled with its bound, such as retry 3x with backoff.

Yes, any trigger-to-action automation described in prose can be rendered as an n8n-style node graph with labeled IF, Switch, or Filter branches. It is not intended for deployed service topologies, event-bus diagrams, or time-ordered sequence diagrams, which need different diagram types.

No. The Skill redacts webhook signing secrets, HTTP Authorization bearer headers, node API keys, Postgres connection passwords, and OAuth tokens before any tool call, replacing them with placeholders like [REDACTED_BEARER]. The final export is re-scanned to confirm no raw credentials remain.

Common failures are a second trigger node, an orphan node unreachable from the trigger, an unlabeled branch output, or a Switch case that goes nowhere. The validate_architecture and suggest_architecture_improvements tools flag these, and the lint-score-repair loop runs until the score reaches 95 with zero hard blockers.