> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/ai-sre/ai-sre-for-administrators/set-up-runbook-management/workflows/common-use-cases.md).

# Common Use Cases

### Common use cases <a href="#common-use-cases" id="common-use-cases"></a>

#### Dynamic notification routing <a href="#dynamic-notification-routing" id="dynamic-notification-routing"></a>

**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 <a href="#service-specific-runbooks" id="service-specific-runbooks"></a>

**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 <a href="#custom-field-integration" id="custom-field-integration"></a>

**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 <a href="#environment-specific-actions" id="environment-specific-actions"></a>

**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 <a href="#next-steps" id="next-steps"></a>

* Go to [Use Mustache templates in runbook actions](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/workflows/use-mustache-runbook-actions.md) to learn how to implement these patterns.
* Go to [Use CEL in runbook actions](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/workflows/use-cel-runbook-actions.md) to add advanced dynamic content.
* Go to [Best practices](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/workflows/best-practices.md) to review usage guidelines.

{% hint style="info" %}
**Need Help?** Contact our support team by email at **<support@harness.io>** or visit the [Harness Documentation](https://docs.harness.io) for additional resources and troubleshooting guides.
{% endhint %}