Rootly

Manage and react to incidents in Rootly

Triggers

On Incident Listen to incident events

Actions

Create Event Add a timeline event to a Rootly incident

Create Incident Create a new incident in Rootly

Update Incident Update an existing incident in Rootly

On Incident

The On Incident trigger starts a workflow execution when Rootly incident events occur.

Use Cases

• Incident automation: Automate responses to incident events
• Notification workflows: Send notifications when incidents are created or resolved
• Integration workflows: Sync incidents with external systems
• Post-incident actions: Trigger follow-up workflows when incidents are mitigated or resolved

Configuration

• Events: Select which incident events to listen for (created, updated, mitigated, resolved, cancelled, deleted)

Event Data

Each incident event includes:

• event: Event type (incident.created, incident.updated, etc.)
• incident: Complete incident information including title, summary, severity, status

Webhook Setup

This trigger automatically sets up a Rootly webhook endpoint when configured. The endpoint is managed by SuperPlane and will be cleaned up when the trigger is removed.

Example Data

{
  "data": {
    "event": "incident.created",
    "incident": {
      "id": "abc123-def456",
      "mitigated_at": null,
      "resolved_at": null,
      "severity": "sev2",
      "started_at": "2026-01-19T12:00:00Z",
      "status": "started",
      "summary": "The API response times have increased significantly across all endpoints.",
      "title": "API latency spike detected",
      "url": "https://app.rootly.com/incidents/abc123-def456"
    }
  },
  "timestamp": "2026-01-19T12:00:00Z",
  "type": "rootly.onIncident"
}

Create Event

The Create Event component adds a timeline event (note/annotation) to a Rootly incident.

Use Cases

• Investigation notes: Add detailed investigation notes to the incident timeline
• Status updates: Post automated status updates as workflows progress
• Cross-system sync: Sync comments from external tools into the incident timeline

Configuration

• Incident ID: The Rootly incident UUID to add the event to (required, supports expressions)
• Event: The note/annotation text (required, supports expressions)
• Visibility: Internal or external visibility (optional, default per Rootly)

Output

Returns the created incident event with:

• id: Event ID
• event: Event content
• visibility: Event visibility
• occurred_at: Event timestamp
• created_at: Creation timestamp

Example Output

{
  "data": {
    "created_at": "2026-02-10T07:34:35.902-8:00",
    "event": "Investigation update: database connections stabilized.",
    "id": "a2d32bb7-0417-4d0d-8483-a583c3-7853",
    "occurred_at": "2026-02-10T07:34:35.902-8:00",
    "visibility": "internal"
  },
  "timestamp": "2026-02-10T15:34:36.09877478Z",
  "type": "rootly.incident.event"
}

Create Incident

The Create Incident component creates a new incident in Rootly.

Use Cases

• Alert escalation: Create incidents from monitoring alerts
• Error tracking: Automatically create incidents when errors are detected
• Manual incident creation: Create incidents from workflow events
• Integration workflows: Create incidents from external system events

Configuration

• Title: A succinct description of the incident (required, supports expressions)
• Summary: Additional details about the incident (optional, supports expressions)
• Severity: Incident severity level (optional, supports expressions)

Output

Returns the created incident object including:

• id: Incident ID
• title: Incident title
• status: Current incident status
• severity: Incident severity
• started_at: Incident creation timestamp
• url: Link to the incident in Rootly

Example Output

{
  "data": {
    "id": "abc123-def456",
    "severity": "sev1",
    "started_at": "2026-01-19T12:00:00Z",
    "status": "started",
    "summary": "Users are experiencing slow database queries and connection timeouts.",
    "title": "Database connection issues",
    "url": "https://app.rootly.com/incidents/abc123-def456"
  },
  "timestamp": "2026-01-19T12:00:00Z",
  "type": "rootly.incident"
}

Update Incident

The Update Incident component updates an existing incident in Rootly.

Use Cases

• Status updates: Update incident status when new information arrives
• Severity changes: Adjust severity based on impact assessment
• Service association: Attach affected services to an incident
• Team assignment: Assign teams to respond to an incident
• Metadata updates: Add labels to categorize incidents

Configuration

• Incident ID: The UUID of the incident to update (required, supports expressions)
• Title: Update the incident title (optional, supports expressions)
• Summary: Update the incident summary (optional, supports expressions)
• Status: Update the incident status (optional)
• Sub-Status: Update the incident sub-status (optional, required by some Rootly accounts when changing status)
• Severity: Update the incident severity level (optional)
• Services: Services to attach to the incident (optional)
• Teams: Teams to attach to the incident (optional)
• Labels: Key-value labels for the incident (optional)

Output

Returns the updated incident object including:

• id: Incident UUID
• sequential_id: Sequential incident number
• title: Incident title
• slug: URL-friendly slug
• status: Current incident status
• updated_at: Last update timestamp

Example Output

{
  "data": {
    "id": "abc123-def456",
    "mitigated_at": "2026-01-19T13:30:00Z",
    "sequential_id": 42,
    "severity": "sev1",
    "slug": "database-connection-issues",
    "started_at": "2026-01-19T12:00:00Z",
    "status": "mitigated",
    "summary": "Root cause identified. Connection pool exhausted.",
    "title": "Database connection issues - Updated",
    "updated_at": "2026-01-19T13:30:00Z",
    "url": "https://app.rootly.com/incidents/abc123-def456"
  },
  "timestamp": "2026-01-19T13:30:00Z",
  "type": "rootly.incident"
}