Alert-triggered workflows have always been able to act on what happened — but not on who handled it or when. There was no way to reference the responder who acknowledged or resolved an alert inside a workflow action, which meant follow-up automation had to leave that context out or look it up separately.
Acknowledged by, resolved by, and alert timeline are now exposed as Liquid variables in alert-triggered workflows. You can reference them directly in any workflow action that accepts template input — Slack messages, Jira tickets, status updates, or any custom action.
What's included
{{ alert.acknowledged_by }}— the responder who first acknowledged the alert{{ alert.resolved_by }}— the responder who closed it out{{ alert.timeline }}— structured timeline data of status changes and key events
This unlocks workflows that can automatically attribute resolution to the right responder in follow-up tickets, include handler context in Slack status updates, or trigger downstream actions based on who handled an alert — without any manual lookup.
