Workflow Run in Ticket Events

You can now see exactly which workflow and which specific run triggered each automated ticket event in Ravenna. This update adds more transparency to automation-driven activity, making it easier to understand how workflows are interacting with your tickets.

Why we built it

As teams expanded their use of automation, tracking the source of ticket updates became more challenging. Customers told us they needed a clearer way to identify which workflow caused a given change, especially when troubleshooting unexpected behavior or reviewing audit trails. We built this feature to make workflow attribution straightforward, helping teams debug, verify, and fine-tune automations with confidence.

What you can do with it

Every event in a ticket’s activity log now includes details about the workflow and run that triggered it. You can quickly trace an update back to its origin, whether it’s an automated status change, field update, or comment. This provides a full picture of how automations are influencing your tickets, supports better auditing, and ensures workflows perform as intended.

Check out the docs to learn more about workflow run visibility in ticket events.