Skip to main content

Trigger on Key Events

Last updated on

Integration with Key Events​

Key Event Trigger Configuration​

When using Key Events as trigger sources:

  1. Set Trigger Condition: In the Triggers section, set the condition to "Key Event Created"
  2. Map Event to Input: Configure how event data maps to runbook input variables
  3. Dynamic Execution: Enable automatic execution when specified Key Events occur
  4. Data Validation: Ensure event data meets runbook input requirements

This approach allows for seamless integration between event detection and automated response, without requiring manual configuration of input variables for each execution.

Benefits​

  • Automated Response: Immediate response to incidents and alerts without manual intervention
  • Consistent Execution: Standardized response procedures triggered by specific conditions
  • Scalable Operations: Handle increasing incident volumes without additional manual effort
  • Reduced MTTR: Faster incident resolution through automated trigger-based responses
  • Operational Efficiency: Free up team members to focus on complex issues requiring human intervention
  • Audit Trail: Complete tracking of automated actions and their triggers
  • Flexible Configuration: Adapt trigger behavior to changing operational requirements

Next steps​

info

Need Help? Contact our support team by email at support@harness.io or visit the Harness Documentation for additional resources and troubleshooting guides.