Triggers

A trigger is the event that starts a workflow. Batida supports several event-based triggers that cover the most common automation scenarios.

Available triggers

Trigger	Description
Incident opened	Fires when a new incident is created
Status changed	Fires when an incident transitions to a new status
Severity changed	Fires when an incident's severity level is updated
Incident resolved	Fires when an incident is marked as resolved
Alert triggered	Fires when an external alert is received
Maintenance scheduled	Fires when a maintenance window is created
Comment added	Fires when a comment is posted on an incident
Commander assigned	Fires when a Commander is assigned to an incident

Configuring trigger conditions

Most triggers support additional conditions to narrow down when the workflow runs. For example, you can configure a workflow to run only when:

• An incident is opened with severity P1.
• An incident's status changes to "Monitoring".
• An alert is triggered for a specific monitor.

{
  "trigger": "incident_opened",
  "conditions": {
    "severity": "P1",
    "type": "technical"
  }
}

Multiple triggers

A single workflow can have multiple triggers. This is useful when you want the same automation to run in different scenarios. For example, a Slack notification workflow might trigger on both "incident opened" and "severity changed."

Incident opened (P1)  ----\
                           --> Notify #incidents-critical channel
Severity changed (to P1) --/

Trigger evaluation order

When multiple workflows share the same trigger, they all run in parallel. There is no guaranteed execution order between workflows. If you need steps to run in a specific order, combine them into a single workflow.

Webhook triggers

In addition to built-in triggers, you can configure a workflow to start when an inbound webhook receives a specific payload. This lets you integrate with external systems that Batida does not natively support.

1. Navigate to Settings > Webhooks and create an inbound webhook endpoint.
2. In your workflow, select Webhook received as the trigger.
3. Select the webhook endpoint and optionally define a payload filter.

See Webhook management for full setup instructions.

WARNING

Avoid creating workflows that trigger each other in a loop. Batida has a built-in safeguard that stops a workflow if it has already run 10 times within one hour for the same incident.