Creating Automation

after resolving signals, you can create automation to handle similar signals in the future create a triage rule when to create when you see a signal pattern that should be automatically routed or processed what gets created clicking create a triage rule creates a record in the signal routing rules application (for example, rule 29) a link to the new rule record is shown—click it to open the record you can also open it from application records → signal routing rules or the routing rule management dashboard to edit, enable, or run it against pending signals steps in the ai alert analysis panel, go to the automation section and click create a triage rule on the rule record, configure rule name pre populated from the signal name; edit for clarity rule application set to signal triage (or as needed) description (optional) add a short explanation of when and why the rule runs enabled off by default; turn on when the rule is ready to run if conditions define when the rule fires (for example, signal name contains a value, signal source equals x, severity is high) use the condition builder choose field , operator (for example, contains, equals), and value use and or group to add multiple conditions; all must be met for the rule to trigger associated playbook select a playbook that uses the emit trigger and contains only one flow when the rule's conditions are met, this playbook runs rule order is assigned automatically (next available) save the record enable the rule when ready once enabled, the rule evaluates incoming signals; when a signal meets all conditions, the associated playbook runs to test without waiting for new signals open the rule record, go to the support tab, and use run rule against pending signals expand records matched to see which signals were matched by the rule best practices start with simple conditions and refine based on volume test rules before enabling in production (use run this rule against pending signals ) use the routing rule management dashboard to reorder rules (drag and drop), open the rule or associated playbook, enable or disable rules, and edit or delete rules see docid\ uosuzrpsl6hfe9d6br5az for the full dashboard walkthrough document rule logic and purpose in the description field create a playbook when to create when you have investigation steps that should be automated for similar signals steps in the automation section, click create a playbook important ensure browser pop ups are allowed for your swimlane domain the playbook builder opens with suggested components from your plan review and customize the playbook add or remove steps configure step parameters add error handling save and enable the playbook after saving, the associated routing rule is updated with this playbook, and links to the rule record and the playbook are shown—click either link to open it test the playbook with sample data pop up requirement create a playbook opens a new browser window if pop ups are blocked, the playbook may be created without suggested components allow pop ups for the swimlane domain and retry if components are missing best practices test playbooks with sample data before enabling add error handling for external integrations keep playbook flows focused on a single use case document what triggers the playbook and what it does for detailed playbook creation guidance, see the playbooks documentation