# Feedback on passing Coda API key as a command line argument when running \`coda upload\` command

**URL:** <https://connect.superhuman.com/t/feedback-on-passing-coda-api-key-as-a-command-line-argument-when-running-coda-upload-command/32748>\
**Category:** Making Packs\
**Created:** [August 3, 2022, 5:38am UTC](https://connect.superhuman.com/t/feedback-on-passing-coda-api-key-as-a-command-line-argument-when-running-coda-upload-command/32748 "2022-08-03T05:38:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [August 3, 2022, 2:01pm UTC](https://connect.superhuman.com/t/feedback-on-passing-coda-api-key-as-a-command-line-argument-when-running-coda-upload-command/32748/2 "2022-08-03T14:01:07Z")

</div>

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:

```nohighlight
name: Pack Actions
on:
  push:
    branches:
      - main
jobs:
  upload-pack:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16'
      - run: npm install
      - run: 'echo "{\"apiKey\": \"${{ secrets.CODA_API_KEY }}\"}" > .coda.json'
      - run: npx coda upload pack.ts

```

I hope that helps you get started!

---

_[View the full topic](https://connect.superhuman.com/t/feedback-on-passing-coda-api-key-as-a-command-line-argument-when-running-coda-upload-command/32748)._