Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    n8n Context-Aware Node Fields

    1

    Configure any n8n node correctly by letting the chosen action define its fields — find hidden, required, and stale settings before they break your workflow.

    Free

    Security scanned
    n8n Context-Aware Node Fields

    n8n Context-Aware Node Fields

    Example session with this skill installed

    My n8n workflow (exported in workflow.json) has two broken nodes. The Slack node was fine for posting messages, but after switching the operation to update, validation complains about a missing channel field even though I can't see it in the UI, and I'm not sure which field replaces it. The HTTP Request node is set to GET and silently drops my JSON body even though sendBody looks configured. Walk me through the right order: confirm the selection fields, find the toggle or dependency hiding each missing field, rebuild a minimal valid parameter object for both nodes, and revalidate before I redeploy.

    • Read your context and instructions
    • Compiled the n8n context-aware node

    Summary

    Both nodes fixed: the Slack "missing channel" error and the silently dropped HTTP body were prerequisite-toggle dependencies, not typos — reconfigured action-first and revalidated.

    NodeProblem foundFix applied
    SlackConfig copied from post; kept irrelevant channel, lacked messageTsFroze resource: message + operation: update, swapped in messageTs from upstream
    HTTP RequestsendBody left false, so body stayed hidden under a GET-only profileSet method: POST, sendBody: true, JSON content mapped from $json.order

    Valid Slack parameters

    {
  resource: "message",
  operation: "update",
  messageTs: "={{ $json.slack.messageTs }}",
  text: "Order status changed to {{ $json.order.status }}"
}

    validate_node now passes for both; removed stale channel and noisy false sendHeaders/sendQuery toggles.

    Next steps

    • Confirm the upstream item actually carries $json.slack.messageTs before going live
    • Re-run the validation loop after any future change to operation or method
    • Apply the same order (executeQuery vs insert) to the Postgres node later in the workflow

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

    About this skill

    Workflow nodes in n8n are not static objects. Selecting a resource or operation often hides, reveals, or changes the validation requirements of multiple fields, leading to broken nodes and cryptic "missing property" errors. This skill manages these dynamic contracts by analyzing node schemas against your specific configuration.

    What it does

    • Action-Aware Validation checks if your parameter object matches the specific requirements of the chosen resource and operation.
    • Dependency Mapping identifies why fields are hidden or shown based on parent toggles like sendBody or authentication.
    • Property Discovery finds the correct field names and data structures for unfamiliar or deep-nested node settings.
    • Config Sanitization removes stale parameters left over from previous actions that no longer apply to the current mode.

    How it works

    1. Define Action by setting the core resource and operation fields for the node you are configuring.
    2. Inspect Schema using the get_node command to see which fields are required or hidden for that specific context.
    3. Iterative Validation using the validate_node tool to identify missing dependencies or invalid types.
    4. Finalize Params by building a minimal, valid configuration object that follows n8n's internal visibility rules.

    Frameworks & tools

    Specifically designed for n8n workflow automation. Works with core nodes, SaaS integrations, and the HTTP Request node.

    Why this beats prompting it yourself

    Generic AI often suggests parameters that are valid for one version of a node but hidden or renamed in the current one. This skill uses direct node schema inspection to ensure your JSON configuration actually matches the platform's internal dependency graph.

    Use cases

    • Configuring complex HTTP Request nodes with conditional headers, body types, and auth flows.
    • Switching a Slack or Discord node from "send" to "update" without leaving stale fields.
    • Mapping dynamic database operations where fields change between "insert", "update", and "upsert".
    • Troubleshooting "property not found" errors in the n8n UI by checking hidden visibility rules.

    Known limitations

    Does not support community nodes that are not part of the standard n8n distribution. Requires valid node types as input.

    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

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 5 days ago

    • Free to download with an account

    Listed5 days ago

    What's inside

    Frequently Asked Questions