Overview
This page provides real-world examples of event payloads that Edge Connectors receive when polling the Rootly API. These examples show the structure and data available for templating in your action configurations.Event Types
Edge Connector events are divided into two categories based on how actions are triggered:Understanding Action Types: Automatic events trigger actions automatically (configured in
on: section), while manual trigger events are user-initiated actions (configured in callable: section). See the Automatic vs Callable Actions guide for detailed comparison.Automatic Event Types
These events are triggered automatically by system events and can be subscribed to by connectors for monitoring and notifications: Alert Events:alert.created- New alert from monitoring systemalert.updated- Alert properties changedalert.acknowledged- Alert acknowledged by a useralert.resolved- Alert marked as resolvedalert.deleted- Alert removed
incident.created- New incident startedincident.updated- Incident properties changedincident.in_triage- Incident moved to triage statusincident.mitigated- Incident mitigatedincident.resolved- Incident marked resolvedincident.cancelled- Incident cancelledincident.deleted- Incident deleted
Manual Trigger Event Types
These events are triggered by user actions and are managed by actions’event_types_trigger field, not connector subscriptions:
action.triggered- Standalone action triggered by a useralert.action_triggered- Action triggered from an alert contextincident.action_triggered- Action triggered from an incident context
Automatic events can be subscribed to when configuring your Edge Connector. Manual trigger events are configured per action and execute when users trigger them from the UI.
Event Payload Examples
Below are detailed examples of event payloads for each event type.alert.created - Production Database Alert
Template Usage
alert.created - PagerDuty Integration
Template Usage
alert.updated - Status Change
incident.created - Full Example
Based onEdgeConnectors::IncidentSerializer:
alert.action_triggered - User-Initiated Restart on Alert
Template Usage in Actions
incident.action_triggered - Escalation on Incident
action.triggered - Standalone Action
Edge Cases
Alert with No Services
Alert with Custom Data (Datadog)
Standalone Action with No Parameters
HTTP Action Examples
alert.created → Slack Notification
incident.created → PagerDuty Integration
alert.action_triggered → Restart Service API
action.triggered → Clear Global Cache
- Exit code = HTTP status code (200, 404, 500, etc.)
- Stdout = Response body + status message
- Stderr = Error message (if request fails)
- Success = 2xx status codes
- Failure = 4xx, 5xx status codes