Common Use Cases

Real-world examples of incident fields in runbook actions.

Common use cases

Dynamic notification routing

Scenario: Route notifications to service-specific channels

Slack action configuration:

• Channel (form field): #{{incident.service}}-incidents

• Message:

  🚨 New incident in {{incident.service}}
  Severity: {{incident.severity}}

If incident.service = payment-service, message goes to #payment-service-incidents

Service-specific runbooks

Scenario: Trigger different remediation based on affected service

Implementation: Use trigger conditions

• Trigger 1: incident.service equals payment-service, then run the "Restart Payment Pods" runbook

• Trigger 2: incident.service equals database, then run the "Database Health Check" runbook

Custom field integration

Scenario: Your incident type has a custom field affected_users (Number type)

Jira ticket description:

Impact: {{incident.affected_users}} users affected
Service: {{incident.service}}
Severity: {{incident.severity}}

Environment-specific actions

Scenario: Different escalation for production vs. staging

Trigger conditions:

• Trigger 1: incident.environment equals production AND incident.severity in [SEV0, SEV1], then page VP Engineering

• Trigger 2: incident.environment in [staging, development], then post to #dev-incidents

---

Next steps

• Go to Use Mustache templates in runbook actions to learn how to implement these patterns.

• Go to Use CEL in runbook actions to add advanced dynamic content.

• Go to Best practices to review usage guidelines.

Need Help? Contact our support team by email at [e-mail] or visit the Harness Documentation for additional resources and troubleshooting guides.