Templates and authorization header

Hi! What is the best strategy if I want to share new template with Authorization header? Shall I go with simple Edit Field that will instruct user to enter his api-key, or shall I instruct user to enter his api-key into new credential storage? He will have to enter name: Authorization and Value: “Bearer dfg-api-key”. Which one do you propose. For me there is no difference (safety of course, but usually it’s your own instance of n8n), so please help me choose.

btw. this will be telegram → groq[llama3] chat with simple memory management.

Regards,
Artur

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hello @Artur_Witek

The credentials must be defined only within the n8n credentials. No edit field nodes or other plain-text formats should be used

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.