Allow Using Expressions for Header Auth Credential Selection in HTTP Request Node

Feature Requests
1

The idea is:

Currently, the HTTP Request node in n8n only allows selecting the Header Auth credential type in a fixed manner. It would be beneficial to allow using an expression to dynamically reference credentials by name instead of selecting them manually.

My use case:

I have an automation that needs to operate with multiple API tokens, such as different ManyChat accounts (e.g., “ManyChat Account 1”, “ManyChat Account 2”). Since ManyChat authentication is based solely on the API token, I need a way to dynamically select the correct credential without exposing the API keys in execution logs.

Right now, a workaround is storing API keys in Redis, but this exposes them in the logs, which is a security risk. If the Header Auth field could accept expressions, I could simply pass a credential name dynamically.

I think it would be beneficial to add this because:

  • Improves security by preventing API keys from being exposed in execution logs.
  • Enhances flexibility for automations that require switching between multiple API credentials.
  • Reduces the need for workarounds like storing API keys in Redis or hardcoding multiple requests for different credentials.

Any resources to support this?

Screenshot highlighting the current limitation:
:paperclip:

n8n feature
n8n feature503×883 23 KB

Are you willing to work on this?

I would love to see this feature added! Let me know if I can provide more details to help with the implementation.

Thanks in advance!
Anderson

2

I agree that it is an interesting feature to implement. It would really increase security and make it easier to use multiple credentials, without exposing sensitive data. :wink::handshake: