In n8n, credentials are not stored directly inside nodes but in the encrypted credentials store, so the human way to handle this is to manage them through the n8n REST API rather than trying to inject them directly into workflows. From your admin dashboard (in Aeros PHP), you can collect the API keys or secrets via forms and then call the /credentials endpoint of n8n to create or update credentials dynamically. This ensures the credentials are stored securely in n8n and can be reused by any node that requires them. For simpler setups, you can also use environment variables to provide static keys (e.g., a shared OpenAI key), but for a multi-user system, the best practice is to securely store user-specific credentials in your dashboard, push them to n8n via its API when needed, and link them to the relevant nodes. This approach keeps workflows clean, credentials secure, and makes integrations seamless from your dashboard layer.

Hi Georgio, I specialize in building automation solutions using n8n and AI agents, including voice/chat systems and data integrations. I’d be happy to connect and discuss how my expertise could add value to your projects.

I am facing this issue on self-hosted but not on n8n Cloud. Can you suggest any solution for this?

@Usman Mohammed