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.conditions_and_scheduling_runbook_step.png

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

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.
    milestone_condition.png
  2. Select Is, then choose Acknowledged. Click Done.
    is_acknowledged.png
    This rule is added to the Runbook step.
    milestone_acknowledged.png

Creating complex rule sets 

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

Was this article helpful?
0 out of 0 found this helpful
Register your product
You can get support that’s tailored to you, owner exclusives and more
Our helpline hours:
8:00am - 8:00pm CST Monday to Friday; 9:00am - 6:00pm CST Saturday
Follow us on Twitter
Get the latest news and updates first