Summary
Add a toggle or checkbox in the HTTP Request node UI to skip sending query parameters if the value is null, undefined, or an empty string.
Why this matters
Currently, when a query parameter is defined in the HTTP Request node, n8n always includes it—even if the value is blank or dynamically resolves to nothing. This leads to:
?param=being sent unnecessarily,- Potential filtering issues in APIs,
- And a need for extra logic in Function or Set nodes, which is not beginner-friendly.
Proposed Solution
In the Query Parameters section of the HTTP Request node:
- Add a checkbox labeled “Skip if empty/null” next to each parameter.
- When enabled, the parameter will be omitted entirely from the request if the value is
null,undefined, or an empty string ("").
Benefits
- Improves accessibility for non-technical users who build flows using only the GUI.
- Keeps workflows clean by avoiding extra Set or Function nodes.
- Mirrors behavior in tools like Postman, Retool, and Xano.
Example Use Case
In a real estate automation, the StandardStatus.in parameter should only be sent if a checkbox is checked. Currently, we must use a Function node to conditionally include it, which breaks the low-code flow.