Advanced

Environment Variables

Environment variables let you store configuration values that are accessible across all workflows in a tenant — without hardcoding them in individual nodes.

Setting Environment Variables

Settings → Environment Variables → + Add
Enter a key (e.g., STRIPE_WEBHOOK_SECRET) and value
Save — the value is encrypted at rest

Using in Expressions

{{ $env.STRIPE_WEBHOOK_SECRET }}
{{ $env.API_BASE_URL }}
{{ $env.TENANT_REGION }}

Common Use Cases

Variable	Use Case
`API_BASE_URL`	Base URL for internal services (different per environment)
`WEBHOOK_SECRET`	Shared signing secret for HMAC verification
`DEFAULT_TIMEZONE`	Timezone for date/time operations
`SLACK_ALERTS_CHANNEL`	Default Slack channel for error notifications

Environment Promotion

If you have separate riogentix tenants for staging and production, export variables from one and import to the other:

Settings → Environment Variables → Export — downloads an encrypted JSON file
In the target tenant: Settings → Environment Variables → Import

⚠️ Security note: Never store secret values in workflow node parameters or expressions directly. Always use credentials or environment variables.

Variable Precedence

Node-level override (highest priority)
Workflow-level variable (set in workflow settings)
Tenant environment variable
System default (lowest priority)