Allow NODES_INCLUDE/NODES_EXCLUDE to filter credential-only nodes (HTTP Request integrations)

The idea is:

Extend NODES_INCLUDE and NODES_EXCLUDE environment variables to also filter credential-only nodes that appear in the “Action in an app” section of the node picker.

Currently, these environment variables only work on actual node types (e.g., n8n-nodes-base.slack), but they do not affect the HTTP Request-based integrations that are auto-generated from credential definitions (e.g., Datadog, VirusTotal, Zabbix, ZscalerZIA, etc.).

Alternatively, introduce new environment variables like CREDENTIALS_INCLUDE or CREDENTIALS_EXCLUDE to control which predefined credential types appear in the HTTP Request node.

My use case:

We run a self-hosted n8n instance for our team and want to curate a clean, focused node picker showing only the integrations we actually use. We’ve set up NODES_INCLUDE with ~50 nodes and disabled community packages with N8N_COMMUNITY_PACKAGES_ENABLED=false.

However, the node picker still shows 100+ HTTP Request-based integrations in the “Action in an app” section that we don’t need. This creates noise and confusion for our users who have to scroll through irrelevant integrations.

I think it would be beneficial to add this because:

  1. Consistency - If NODES_INCLUDE whitelists nodes, it should whitelist all nodes including credential-only ones
  2. Security/Compliance - Some organizations need to restrict which external services users can connect to
  3. User experience - A curated node picker is easier to navigate and reduces onboarding friction
  4. Existing demand - GitHub Issue Can not hide HTTP request based Nodes using NODES_EXCLUDE · Issue #19281 · n8n-io/n8n · GitHub was closed as a feature request, showing this is a known limitation

Any resources to support this?

Are you willing to work on this?

Yes, I’m willing to contribute code to implement this feature if it can speed up the implementation. Happy to submit a PR once the approach is validated by the maintainers.