Hey @Benjamin_Behrens
, thanks for reading and for calling that out! You hit the nail on the head.
For this ‘Beginner’ phase, I kept things simple by assuming a personal setup running n8n locally. Hardcoding the key is an okay shortcut just to learn the plumbing, but as you rightly pointed out, it’s a major liability for a production or public extension.
Since this is an ongoing series of tutorials, I’m actually going to solve exactly this in the upcoming parts!
-
In the next mid-level tutorial, I’ll be walking through how to build an
options.htmlsettings page to move away from hardcoded credentials. -
Then, in the 3rd tutorial, I will fully implement the
chrome.storage.localapproach to securely save, load, and rotate those keys.
This will give users a true BYOK “Bring Your Own Key” experience without ever needing to rebuild the extension. Really appreciate the great feedback—it perfectly tees up the next chapters!