For local development, authenticate your machine against the Ennote Cloud using an OAuth 2.0 PKCE flow.

ennote auth login

Once authenticated, you can specify your organization and workspace via the config command:

ennote config set organization-id my-org-id
ennote config set workspace-id my-workspace-id

You can now inject secrets directly into your local development servers without writing a .env file:

ennote secret get stripe-keys -- npm run dev

For automated pipelines (GitHub Actions, GitLab CI), avoid the auth login command. Instead, provision a Machine Identity Token and inject it via the environment.

# Example: GitHub Actions
steps:
  - name: Run Database Migrations
    env:
      ENNOTE_TOKEN: ${{ secrets.ENNOTE_MACHINE_TOKEN }}
      ENNOTE_ORGANIZATION_ID: org_123
      ENNOTE_WORKSPACE_ID: wrk_prod
      ENNOTE_DO_NOT_TRACK: 1
    run: |
      ennote secret get db-credentials -- npm run migrate

To learn more about token limits, expiration, and management, please see our detailed Personal Access Tokens guide.

Need to securely transfer credentials across untrusted channels like Slack, Jira, or email? The CLI allows you to create and consume self-destructing, end-to-end encrypted links effortlessly.

1. Create a Share Link

# Quickly share a secret string
ennote share create "my-super-secret"

# Or pipe a file directly and set a 7-day expiration
cat config.json | ennote share create --ttl 7d

2. Read & Inject a Share Link

Once the recipient has the link, they can read it or inject it directly into their own processes. Decryption happens entirely in their local memory.

# Read the shared payload
ennote share get "https://app.ennote.io/onetime/1234#key_salt"

# Extract a specific key and inject it into a deployment script
ennote share get "https://app.ennote.io/onetime/1234#key_salt" -k "api_key" -- ./deploy.sh

Because the decryption key is embedded in the URL fragment (which browsers and clients never transmit to the server), Ennote acts purely as a blind storage provider. Dive into the details in our Share Command guide.