Automating workflow using Runbook conditions

The option to automate steps during an incident is one of the most powerful features of FireHydrant's incident response platform. By using Runbook conditions, you can leverage that automation to run when your incident is at a specific state. You can set up conditions to enable automation at any point in your incident lifecycle.

To access available conditions, click Runbooks in the left nav. Click the link for the Runbook where you want to add the condition. choose_runbook_from_list.png

On the edit page, find the specific step where you would like to add a condition. In the panel for that step, click Conditions & scheduling.


This opens your options for applying rules that dictate when you want this specific step to run.

Note: Runbook conditions evaluate up to 30-days from attachment to the incident. An example might be an incident runs for a month, is resolved, we won’t execute a greater than 15 daycondition post resolution because it has been past 30 days since declared OR runbook is attached (if manually done).

Example: Applying a condition based on milestone

For example, assume that you want the Create PagerDuty Incident step (shown above) to run only after an incident has been acknowledged. You can create a rule to ensure this condition.

  1. Click Select , then Current milestone.
    A list opens, showing all available milestones in FireHydrant.
  2. Select Is , then choose Acknowledged. Click Done.
    This rule is added to the Runbook step.

Creating complex rule sets 

After you learn to create rules for Runbooks, you can add complexity to Runbook conditions by linking multiple sets of rules together with an AND statement. This gives you the flexibility to tailor Runbook steps to be triggered only for unique conditions or at specific times during an incident.

Last updated on 3/28/2023