How do you all handle storing sensitive information like API keys?
In my case, I have flows that interact with Stripe, external APIs, etc., and they all rely on API keys. I used to hardcode them directly into the flows, but that quickly became inefficient especially when the same key is used across multiple flows. Updating them is a hassle.
To solve this, I created a config table in a separate protected workspace with a single record where I store all my keys and references. It works, but I’m wondering if there’s a better or more secure way others are using.
Ideally, Tape should allow us to store credentials securely and reference them by name within flows. That’s be a great feature.
I think most of us are doing the same as you are currently.
I also store links to our logo and address, it’s been a while since I’ve had to build any new landing pages, but I think I have some CSS style sheets that we call as well…
Having a global place to update assets is amazing and saves so much time.
Hey @Thaha,
yes we do it exactly the same way. Not the best way, but the only way currently.
Problem is: when other developers with less access rights, especially not for the config table, want to adjust an automation, that depends on it - it will break the automation.
I also hope, there will be a better handling of secrets in the (near) future.