mirror of
https://github.com/n8n-io/n8n.git
synced 2026-10-21 20:20:03 +02:00
70b3f2fcaf
The dependency index already records a row per node type per workflow, kept current on every save, and the workflow repository already resolves a `nodeTypes` filter against it. No caller ever supplied one, so "which workflows use Postgres" meant fetching every workflow and parsing its nodes, and "what is this folder built out of" was not answerable at all. - `workflows(list)` gains `nodeTypes`. It matches the node a workflow actually contains, so a workflow merely NAMED for a service is correctly excluded and one that uses it under an unrelated name is correctly found. - `workflows(node-usage)` returns the node-type histogram for a scope, most-used first, and composes with the folder arguments. Offered only where the adapter can answer it, so the agent is never shown a summary it would get an error from. - Counts DISTINCT workflows rather than node instances: three HTTP Request nodes in one workflow are one user of the type, which is the question being asked. - The scan is capped, and a capped scan says its counts are a lower bound — silently truncating would read as a total, and these are numbers a caller quotes back to the user. - Gated separately from folder context. The two answer different questions (where something lives vs what it is made of), and one switch could not tell which of them moved a result. Shared field descriptions are hoisted to constants because the schema sanitizer requires a single description per field name across the action union. |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| AGENTS.md | ||
| eslint.config.mjs | ||
| package.json | ||
| tsconfig.build.json | ||
| tsconfig.json | ||
| vite.config.ts | ||