N8N Workflow Api Patcher

Patch n8n workflows via API in seconds - no manual JSON editing required.

Install
cmdop skills install agensi-n8n-workflow-api-patcher

N8N Workflow API Patcher is a skill that applies bulk updates to n8n workflow nodes through the n8n REST API, eliminating the need to open and manually edit workflow JSON files one by one. It targets developers and automation engineers who maintain large numbers of n8n workflows and periodically need to apply the same change across many of them at once.

The skill addresses several recurring maintenance tasks: migrating API endpoints from one LLM provider to another (for example, moving from Ollama to a different LLM API), correcting code node typeVersion values across workflows, updating authentication headers in bulk, and changing typeValidation mode settings. These are changes that would otherwise require opening each workflow individually in the n8n editor or writing one-off scripts against the API.

The skill connects to a locally running n8n instance at http://localhost:5678 and requires an API key to be configured before use. Because it depends on a local n8n instance at that specific address, it is not suited for remote or cloud-hosted n8n deployments unless network routing is arranged externally. There are no additional environment variables documented in the registry record. The skill is described as built for n8n power users who maintain ten or more workflows, so it is less relevant for single-workflow or small-scale setups.

Use cases

  • Migrate all Ollama API endpoint references to a different LLM API across 50 workflows in one operation
  • Fix code node typeVersion values from 2 to 1 across multiple workflows without opening each one
  • Bulk-update authentication headers when rotating API keys or changing auth schemes
  • Change typeValidation mode settings uniformly across a set of workflows
  • Automate repetitive node-level edits that would otherwise require manual JSON surgery

When to use it

  • Maintaining 10 or more n8n workflows that share common node configurations
  • Performing a migration from one LLM API provider to another across many workflows
  • Rotating or updating authentication headers in bulk
  • Correcting a misconfigured field (such as typeVersion) that appears in many workflows

When not to use it

  • n8n is hosted remotely or in the cloud and not accessible at http://localhost:5678
  • No n8n API key is available or can be configured
  • Only a single workflow needs to be edited — the n8n UI is sufficient
  • Changes need to target workflow triggers or structural elements beyond node-level properties