[➕ Feature]: Trigger workflows when alert is assigned via UI

[alexmorbo]

Problem

When a user clicks "Self-Assign" or changes the assignee in Keep's web UI, workflows with only_on_change: [assignee] are NOT triggered.

This prevents external integrations (like Mattermost/Slack bridges) from receiving notifications when alerts are assigned through the UI.

Current Behavior

The /alerts/{fingerprint}/assign/{last_received} endpoint in keep/api/routes/alerts.py:

1. ✅ Updates assignee in enrichments table
2. ✅ Changes alert status to "acknowledged"
3. ✅ Sends email notification
4. ❌ Does NOT call workflow_manager.insert_events()

@router.post("/{fingerprint}/assign/{last_received}")
def assign_alert(...):
    enrichment_bl.enrich_entity(...)
    send_email(...)
    return {"status": "ok"}
    # Missing: workflow_manager.insert_events()

Expected Behavior

When an alert is assigned via UI, workflows with matching triggers should be executed, similar to how /enrich and /batch_enrich endpoints work.

Proposed Solution

Add workflow_manager.insert_events() call to the assign endpoint:

@router.post("/{fingerprint}/assign/{last_received}")
def assign_alert(...):
    enrichment_bl.enrich_entity(...)
    send_email(...)
    
    # Trigger workflows for assignee change
    alert_dto = get_alert_by_fingerprint(tenant_id, fingerprint)
    workflow_manager.insert_events(tenant_id=tenant_id, events=[alert_dto])
    
    return {"status": "ok"}

This would allow workflows like:

workflow:
  id: notify-on-assign
  triggers:
    - type: alert
      only_on_change:
        - assignee
  actions:
    - name: send-webhook
      provider:
        type: webhook
      with:
        url: "https://my-bridge/webhook"
        body:
          fingerprint: "{{ alert.fingerprint }}"
          assignee: "{{ alert.assignee }}"

Use Case

I'm building a Mattermost bridge that syncs Keep alerts bidirectionally. When someone acknowledges an alert in Mattermost, it updates Keep. However, when someone assigns an alert in Keep's UI, Mattermost doesn't get notified because no workflow is triggered.

Environment

• Keep version: latest (main branch)
• Affected endpoints: /alerts/{fingerprint}/assign/{last_received}

Related Code

• keep/api/routes/alerts.py - assign endpoint
• keep/workflowmanager/workflowmanager.py - insert_events() method
• Similar pattern already exists in /enrich endpoint

[dosubot]

Hi @alexmorbo! I'm Dosu and I’m helping the keep team.

Your proposed solution—adding a call to workflow_manager.insert_events() in the assign endpoint—will trigger workflows with only_on_change: [assignee] as expected. This matches the pattern used in the /enrich and /batch_enrich endpoints, which already call insert_events() after enrichment to trigger workflows on relevant changes. The workflow manager's logic supports only_on_change triggers by comparing the current and previous alert states, so workflows will only run when the assignee actually changes, avoiding duplicate notifications or unnecessary executions source.

There are no architectural or business logic reasons in the code or comments for skipping workflow triggers on assignment; this appears to be an oversight rather than an intentional design. Recent fixes for similar issues (like missing workflow triggers after incident status changes) have been low risk and backward compatible, suggesting this change should be safe and consistent with existing patterns source.

For best results, follow the enrichment endpoints' approach: after updating the assignee and sending the email, fetch the updated alert DTO and call insert_events() with it. This will ensure external integrations like your Mattermost bridge receive notifications when alerts are assigned via the UI.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[jyoti369]

I've opened #6243 to fix this. The assign_alert endpoint was missing a workflow_manager.insert_events() call after enriching the alert, so workflows with only_on_change: [assignee] never fired on UI assignment. The fix follows the same pattern used by the /enrich and /batch_enrich endpoints.

[jyoti369]

@alexmorbo opened #6243 with the fix -- the assign endpoint now calls workflow_manager.insert_events() so workflows with only_on_change: [assignee] should fire on UI assignment.