Overview
Pulse workflows run automatically when Rootly receives a pulse. Pulses are code-change events (for example, pushes, merges, and deployments) streamed into Rootly from supported source control and CI/CD integrations such as GitHub and GitLab. Pulse workflows are designed for teams that want to connect delivery signals to operational response. Instead of treating deployments as “background noise,” you can use pulses to proactively notify responders, create artifacts for visibility, and even pre-declare incidents when the change itself represents elevated risk. Pulse workflows are particularly useful for:- Pre-declaring incidents when risky changes ship, so responders have a shared coordination space ready if impact appears
- Broadcasting deployments into shared channels (for example, release, infrastructure, or product channels) with consistent formatting and context
- Creating follow-up work automatically when a pulse matches a high-risk pattern (specific repo, branch, environment, or payload value)
Pulse workflows only run if pulses are successfully flowing into Rootly. Before building automation, confirm your pulse integration is connected and producing pulse events.
Supported Trigger
Pulse workflows support one trigger event:- Pulse Created (
pulse_created)
Fires immediately when a new pulse is received in Rootly.