Skip to main content
Workflows often need external credentials (API keys, database passwords) and configuration values (endpoints, feature flags). V-Run provides two mechanisms to inject these at runtime, both scoped to a single workflow.

Secrets

Secrets are encrypted values that are never exposed in the UI after creation. Use them for:
  • API keys and tokens
  • Database passwords
  • Private keys
  • Any value you would never commit to source control

Setting secrets

Secrets live inside the workflow that uses them. Open the workflow in the editor and set them from the Config tab alongside your environment variables.

Using secrets in code

Secrets are injected as environment variables at runtime. Access them with os.environ:

Declaring required secrets

List secrets your workflow needs in the config.yaml so that missing secrets are flagged before execution:

Environment variables

Environment variables store non-sensitive configuration values. Unlike secrets, their values are visible in the UI. Use them for:
  • API endpoint URLs
  • Feature flags
  • Configuration modes (e.g. LOG_LEVEL=debug)

Setting environment variables

Environment variables are also defined per-workflow, from the Config tab of the editor.

Using environment variables in code

Access them the same way as secrets:

Declaring required environment variables

Scope

Both secrets and environment variables are scoped to a single workflow — there is no shared, account-level, or project-level scope. If two workflows need the same value, set it on each one independently.