Pulse Variables

Reference for pulse variables available in Liquid templates for processing health check, deploy, and monitoring data in Rootly workflows and integrations.

You can use pulse variables in pulse workflows and any Liquid template evaluated in a pulse context.

Use the Liquid Markup explorer to navigate through all pulse variables against real pulse data.

Rootly uses the Liquid template language. The variables below are available wherever a pulse is in scope.

Variables

Ruby

{{ pulse.id }} # returns string (uuid)
{{ pulse.short_id }} # returns string
{{ pulse.source }} # returns string — name of the pulse source (e.g., "github", "k8s", "generic")
{{ pulse.summary }} # returns string
{{ pulse.data }} # returns the raw pulse payload as a JSON object

Examples

Reaching into the raw pulse payload:

Ruby

{{ pulse.data | get: 'commit_sha' }}

Building a deploy-style summary line:

Ruby

{{ pulse.source | titleize }} pulse {{ pulse.short_id }}: {{ pulse.summary }}

---

Related Pages

Pulse Workflows

The workflow type that consumes pulses — where these variables are used.

Incident Variables

Reference incident attributes when a pulse converts into or updates an incident.

Alert Variables

Reference alert attributes from adjacent alert workflows.