▸case-14 I have constructed a parameter JSON payload for an n8n node and am ready to write it into my workflow file using n8n_update_partial_workflow. Can I immediately execute the update tool call, or should an interim verification tool call be executed first? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 When setting up an n8n HTTP Request node for a simple GET request to https://api.example.com/status, I want to ensure every possible setting is explicitly listed in the JSON. Should I include explicit false flags for sendHeaders, sendQuery, and sendBody, or keep the JSON minimal? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 My n8n Slack node configuration worked fine for sending new messages, but after switching the operation to update existing messages, the workflow validation fails due to parameter mismatch. Please provide a diagnostic guide that explains how parameter requirements shift across operations, detail the optimal sequence for querying node property schema, and supply a valid sample payload for the update action. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 I am building an n8n IF node parameter JSON to check if {{$json.status}} equals the string 'active'. I am tempted to set singleValue: true on this condition like I did for an empty check. Is that parameter structure correct for binary equality? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 I am architecting an automated incident alert pipeline in n8n. I need advice on how to structure overall workflow routing between a Webhook Trigger, an Error Trigger node, and multi-node failure retry strategies across the entire canvas. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 I am trying to set up an HTTP Request node in an n8n workflow to send a JSON payload via POST, but I keep hitting validation errors stating that required body fields are missing or hidden. Can you give me a step-by-step setup walkthrough showing which tool calls to run first to inspect the properties without pulling excessive schema bloat, followed by the complete node configuration JSON? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 I am configuring an n8n Switch or IF node with an operator that checks if a string is empty (operation: 'isEmpty'). Should I include value2 in the condition item, or how should single-value operations be formatted? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 I want to pass URL query parameters in an n8n HTTP Request node without hardcoding them into the base URL string. Should I place the query parameter key-value pairs directly inside the body object? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 I am configuring an n8n Postgres node with operation: 'executeQuery' to run a custom SQL query. Should I provide table and values properties in the parameter object? | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 I am updating an existing n8n workflow node from resource: 'message' / operation: 'post' to resource: 'message' / operation: 'update'. Can I keep the exact same payload keys and just change the operation string? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 I am updating records in a PostgreSQL database using an n8n Postgres node (nodes-base.postgres). My team lead says I can use the exact same configuration object as an insert action, just changing operation to 'update'. Is this true, or what extra field is mandatory? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 During workflow editing, an n8n HTTP Request node fails runtime validation with an error indicating that a dependent property is missing, but I cannot see where it is defined in standard output. What specific query mode should I run to inspect that property's rules? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 In n8n node definitions, why do certain parameters appear or vanish dynamically depending on the values chosen for other parameters? What underlying metadata construct governs this conditional behavior? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 I have incoming webhook JSON with an array of user items and I want to filter and transform this data using custom JavaScript inside an n8n Code node using standard $input / $json methods. How do I map and filter nested items programmatically? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 I am building a brand-new custom community node for n8n in TypeScript using n8n-workflow packages to connect to a custom REST API. How do I define the INodeType class definition and standard node properties file structure? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 What is the recommended sequence of discovery steps when configuring an unfamiliar n8n node from scratch, from initial inspection through validation and troubleshooting? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 I am starting to configure a complex n8n node for Google Sheets. I want to inspect its schema using automated tool calls without blowing past my context window token limits. Should I request full detail schema right away, or is there a lighter default option? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 I need to configure an IF node in n8n to evaluate whether an incoming string attribute is empty, but I am uncertain which conditional parameters are needed and how to look up specific fields efficiently. Please supply a structured guide outlining the recommended node schema discovery workflow, an explanation of how conditional field visibility works, and the resulting parameter JSON. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 I am configuring an n8n HTTP Request node and want to know under what exact property condition the body field becomes required during validation. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 I am configuring an n8n HTTP Request node and only need to know how to set up OAuth authentication headers. Rather than fetching all 50+ node properties, what specific tool query parameter should I use to inspect just the authentication properties? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 I want to create a new Slack channel using an n8n Slack node (nodes-base.slack) with resource: 'channel' and operation: 'create'. Should I supply a text property in the parameters payload just like when sending a message? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Why is get_node with standard detail recommended as the primary discovery mechanism in n8n node configuration rather than requesting detail: 'full' every time? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |