# apiKey environment variable instead of .coda.json file **URL:** \ **Category:** Making Packs\ **Created:** [February 13, 2023, 5:43pm UTC](https://connect.superhuman.com/t/apikey-environment-variable-instead-of-coda-json-file/37612 "2023-02-13T17:43:33Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Eric\_Koleda](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eric_koleda/32/50286_2.png) [@Eric\_Koleda](https://connect.superhuman.com/u/Eric_Koleda)\ **Post date:** [February 14, 2023, 2:37pm UTC](https://connect.superhuman.com/t/apikey-environment-variable-instead-of-coda-json-file/37612/2 "2023-02-14T14:37:43Z")
Hi @orth - Thanks for the feedback, that is something we’ve heard before as well. You can work around the limitation by generating your `.coda.json` in the action, as shown here: > [@Feedback on passing Coda API key as a command line argument when running \`coda upload\` command](https://connect.superhuman.com/t/feedback-on-passing-coda-api-key-as-a-command-line-argument-when-running-coda-upload-command/32748/2): > > Hi @Mohammad_Mohammad2 - Thanks for kicking off this discussion. I’ve had people mention to me that they wanted to set up a GitHub action before, but I hadn’t had time to look into it to date. I agree that it would be nice to have a parameter for the token for cases like this, and I can see if the engineers would be open to accepting that PR. I did some testing and found that I could create a .coda.json file without too much trouble. Here’s what my workflow file looks like: name: Pack Actions … In the long run though it would be nice to just make it a command line argument. --- _[View the full topic](https://connect.superhuman.com/t/apikey-environment-variable-instead-of-coda-json-file/37612)._