[Go to site: main page, start]
Skip to main content
The secrets variable lets you reference stored secrets — API keys, tokens, and passwords — inside Liquid templates. Instead of hardcoding sensitive values into your workflow configurations, you reference a secret by name and Rootly resolves the actual value at runtime, so the value itself never appears in your workflow definition.

​
Variables

Rootly uses the Liquid template language. The available variables are:
Ruby

​
Usage

Secrets are most commonly used in workflow tasks that call external systems, such as HTTP request actions that need an authorization header. Because the expression is just Liquid, you can combine secrets with filters like any other variable. For example, to build a Basic authentication header:
Ruby
If your secrets are backed by the HashiCorp Vault integration, values are read from Vault at runtime and JSON secret values are traversed using dot notation:
Ruby
The key path in your template must match the JSON structure of the stored secret exactly, including case.
Managing secret definitions is restricted to Rootly owners and admins by default. If you need a new secret reference, ask an admin to create it for you.