sc-n8n

# sc-n8n — n8n control via @n8n/cli Use the official `@n8n/cli` binary (`n8n-cli`) against the **user-selected n8n instance**. Do not assume a fixed hostname, backup location, deployment platform, shell profile, project, or workflow set. ## Required connection state | Setting | Purpose | |---|---| | `N8N_URL` | Base URL of the selected n8n instance, for example `https://n8n.example.com` | | `N8N_API_KEY` | Public API key for that instance; keep it in the selected SI-Coder credential store or another secure local source | | `~/.n8n-cli/config.json` | Optional CLI-local configuration; never treat it as the only possible source of truth | Install the binary only when needed: ```bash npm i -g @n8n/cli # or use: npx @n8n/cli ... ``` ## Auth resolution When diagnosing which account/instance is active, inspect explicit CLI flags first, then environment variables, then CLI config. Environment variables can override a value saved in the CLI config, so a newly written config value may appear ignored when an older environment variable is still present. If the API returns `401` or an invalid-signature error, do not guess that the header format is wrong. Verify the selected instance/account, then create or rotate an API key from the official n8n UI and store it through the safe SI-Coder credential handoff. Never print the key during verification. ## Connect / verify ```bash n8n-cli config show n8n-cli workflow list --format=id-only ``` A successful read-only workflow listing is...