Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    n8n MCP Workflow Architect

    1

    Build, repair, and safely activate n8n workflows through the n8n-mcp server with a discover-validate-patch loop that eliminates config and identifier errors.

    Free

    2 installsSecurity scanned
    n8n MCP Workflow Architect

    n8n MCP Workflow Architect

    Example session with this skill installed

    My n8n-mcp server is connected to our self-hosted instance. I have a saved workflow called Invoice Sync (id 17) that broke after an upgrade — the Slack node keeps erroring and the IF branches lead nowhere. Please use n8n-mcp to look up the current Slack node version and its schema, validate each node config against a strict profile, then patch the workflow with partial-update operations including proper branch connections, and only activate it once validate_workflow comes back clean. Include the workflowNodeType form of every node you touch so I can reuse the payload on a second instance, and note which fixes came from auto-sanitization versus your explicit operations.

    • Read your context and instructions
    • Compiled the n8n mcp workflow

    Summary

    Repaired the 'Lead Intake to Slack' workflow (id 42) via n8n-mcp: converted failing node types to the workflow identifier family, bound the orphaned IF branches with semantic parameters, and revalidated before activation.

    MetricBeforeAfter
    validate_workflow errors70
    Broken IF connections2 unbound2 (branch: true / branch: false)
    Identifier failures4 (nodes-base.* in create payload)0 (n8n-nodes-base.*)
    Activation statusFailed pre-flightActive, post-validation green

    Fixes were applied through n8n_update_partial_workflow with intent 'Bind IF branches after Switch refactor'. Auto-sanitization normalized two filter payloads on the Edit Fields nodes; the remaining corrections were explicit patch operations, each revalidated with validate_node profile runtime. Slack and HTTP nodes now use workflowNodeType n8n-nodes-base.slack / n8n-nodes-base.httpRequest for reuse on the second instance.

    Next steps

    • Attach Slack credentials and fire one live test at the /incoming webhook path
    • Add an error-output branch from the HTTP Request node before high-volume traffic
    • Re-run n8n_validate_workflow on a schedule to catch drift after n8n upgrades

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Building n8n workflows through LLMs often results in broken JSON, incorrect node type identifiers, and invalid connection logic. Manually debugging these configuration errors in the n8n UI is slow and disrupts the development loop.

    What it does

    • Discovers available n8n nodes using keyword and capability searches.
    • Validates node configurations against standard, runtime, or AI-friendly schemas before deployment.
    • Performs partial workflow updates to add, rename, or connect nodes without rewriting the entire graph.
    • Deploys tested templates from the n8n library with automatic version upgrading.
    • Runs health diagnostics and validation checks on existing workflows via the n8n API.

    Frameworks & tools

    n8n, n8n-mcp server, REST API, Node-RED style logic, and JSON-based workflow schemas.

    Why this beats prompting it yourself

    Basic LLMs frequently hallucinate node parameters or use the wrong naming conventions for different n8n versions. This skill implements a strict discover-validate-patch loop that verifies every change against the actual n8n-mcp server, ensuring the generated workflow is structurally sound and ready for activation.

    Use cases

    • Architecting complex branching logic using IF and Switch nodes with semantic connections.
    • Migrating or upgrading legacy n8n workflows by comparing node versions and breaking changes.
    • Automating the setup of standard integrations like Slack webhooks or database listeners.
    • Debugging existing production workflows by inspecting state and applying targeted patches.

    Known limitations

    Requires a configured n8n-mcp server. API-dependent tools require a valid n8n API URL and Key. Does not support fixing corrupted JSON blobs that fall outside the n8n schema.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    2 installs

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 6 days ago

    • Free to download with an account

    Listed6 days ago

    What's inside

    Frequently Asked Questions