- Home
- Skills
- Workflow Automation
- n8n Context-Aware Node Fields
Works with the AI Agents you already use
n8n Context-Aware Node Fields
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
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.
| Node | Problem found | Fix applied |
|---|---|---|
| Slack | Config copied from post; kept irrelevant channel, lacked messageTs | Froze resource: message + operation: update, swapped in messageTs from upstream |
| HTTP Request | sendBody left false, so body stayed hidden under a GET-only profile | Set 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.messageTsbefore going live - Re-run the validation loop after any future change to
operationormethod - Apply the same order (
executeQueryvsinsert) 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
sendBodyorauthentication. - 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
- Define Action by setting the core
resourceandoperationfields for the node you are configuring. - Inspect Schema using the
get_nodecommand to see which fields are required or hidden for that specific context. - Iterative Validation using the
validate_nodetool to identify missing dependencies or invalid types. - 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.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Assumes an n8n tool layer with node-inspection and validation commands; it teaches generic display-rule patterns, so highly custom community nodes may still need a full schema dump.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Permissions
File Scopes
Only local workflow JSON is read and rewritten to rebuild node parameter objects; no network egress or credentials are required.