Integrations and components

FireHydrant

Learn how to use FireHydrant with SuperPlane.

Manage and react to incidents in FireHydrant

Triggers

On Incident Runs when an incident is created or reaches a specific milestone in FireHydrant

Actions

Create Incident Create a new incident in FireHydrant

Instructions

To connect FireHydrant, create an API key:

Go to Settings → API Keys → Create API Key in your FireHydrant account. This requires Owner permissions.
The API key should have Write Access in order to create incidents and webhooks.
Copy the API key and paste it into the configuration for this integration.

On Incident

Trigger key: firehydrant.onIncident

The On Incident trigger starts a workflow execution when a FireHydrant incident is created or reaches a specific milestone.

Use Cases

Incident response: Automatically notify Slack, update a status page, or create a Jira ticket when an incident is opened
Alert escalation: Trigger escalation workflows when critical incidents are created
Milestone tracking: React to incidents reaching specific milestones such as mitigated or resolved
Cross-tool sync: Sync new FireHydrant incidents to other incident management tools

Configuration

Current Milestone: Select which incident milestones to trigger on (started, acknowledged, mitigated, resolved, etc.). The workflow will trigger when an incident is created or updated to match any of the selected milestones.
Severities (optional): Filter by severity levels. Only incidents matching the selected severities will trigger the workflow. If empty, all severities are accepted.

Event Data

Each incident event includes:

name: Incident name/title
number: Incident number
severity: Severity level
priority: Priority level
current_milestone: Current milestone (e.g., started, acknowledged)
summary: Incident summary

Webhook Setup

This trigger automatically sets up a FireHydrant 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": {
      "conference_bridges": [
        {
          "id": "cb-9f1a2c3d",
          "name": "Zoom War Room",
          "provider": "zoom",
          "url": "https://zoom.us/j/9876543210"
        }
      ],
      "counts": {
        "starred_events": 3,
        "starred_messages": 12
      },
      "created_at": "2026-03-02 14:43:05 UTC",
      "current_milestone": "started",
      "custom_fields": [
        {
          "display_name": "Detected by",
          "id": "b370d5b8-9ef1-49d5-be4a-96ee6e536c8b",
          "value": "Datadog Monitor: DB Health Check"
        }
      ],
      "customer_impact_summary": "All production API requests are failing due to database deletion. Users cannot log in or access core features.",
      "description": "Primary production database was accidentally deleted during maintenance.",
      "follow_ups": [
        {
          "id": "fu-123",
          "status": "pending",
          "title": "Implement database deletion safeguards"
        }
      ],
      "id": "21fe20b5-8012-4a51-a34c-623b1389af66",
      "impacts": [
        {
          "description": "Production users unable to access platform",
          "id": "impact-1",
          "type": "customer"
        }
      ],
      "incident_channels": [
        {
          "id": "ic-789",
          "name": "#incident-001",
          "type": "slack",
          "visibility": "private"
        }
      ],
      "labels": [
        "database",
        "production",
        "outage"
      ],
      "last_note": "Engineering team restoring latest backup from 14:30 UTC.",
      "milestones": [
        {
          "created_at": "2026-03-02 14:43:05 UTC",
          "duration": "",
          "id": "d0eaad5c-6922-4f35-adfb-9cf481d39f46",
          "name": "Started",
          "occurred_at": "2026-03-02 14:43:05 UTC",
          "original_milestone_id": "99e55a31-894a-4e76-b680-89b3acab0d7b",
          "type": "started",
          "updated_at": "2026-03-02 14:43:06 UTC",
          "updated_by_id": "bd23faac-dcda-4fd7-a968-4e0b6a04bf35",
          "updated_by_type": "Bot"
        }
      ],
      "name": "Production Database Accidentally Deleted",
      "number": 42,
      "priority": "P1",
      "private_status_page_url": "https://app.firehydrant.io/incidents/internal/status_page/mock-url",
      "role_assignments": [
        {
          "role": "Incident Commander",
          "user_id": "user-111",
          "user_name": "Alice Johnson"
        },
        {
          "role": "Communications Lead",
          "user_id": "user-222",
          "user_name": "Bob Smith"
        }
      ],
      "severity": "SEV1",
      "started_at": "2026-03-02 14:43:05 UTC",
      "summary": "Production outage caused by accidental database deletion.",
      "tags": [
        "critical",
        "customer-impacting"
      ],
      "tasks": [
        {
          "description": "Restore database from latest backup",
          "id": "task-1",
          "status": "in_progress"
        },
        {
          "description": "Validate data integrity after restore",
          "id": "task-2",
          "status": "pending"
        }
      ],
      "team_assignments": [
        {
          "team_id": "team-ops",
          "team_name": "Operations"
        },
        {
          "team_id": "team-eng",
          "team_name": "Engineering"
        }
      ],
      "updated_at": "2026-03-02 14:45:10 +0000"
    },
    "operation": "CREATED",
    "resource_type": "incident"
  },
  "timestamp": "2026-03-02T14:43:07.292043553Z",
  "type": "firehydrant.incident.created"
}

Create Incident

Component key: firehydrant.createIncident

The Create Incident component creates a new incident in FireHydrant.

Use Cases

Alert escalation: Create incidents from monitoring alerts or error tracking
Cross-tool sync: Open a FireHydrant incident from other SuperPlane triggers (e.g., PagerDuty, Rootly, GitHub)
Manual incident creation: Create incidents from workflow events
Automated response: Automatically declare incidents when thresholds are breached

Configuration

Name: Incident name/title (required, supports expressions)
Summary: Short summary of the incident (optional, supports expressions)
Description: Detailed description of the incident (optional, supports expressions)
Severity: Severity level, e.g., SEV1, SEV2 (optional, populated from FireHydrant)
Priority: Priority level, e.g., P1, P2 (optional, populated from FireHydrant)

Output

Returns the created incident object including:

id: Incident ID
name: Incident name
description: Incident description
summary: Incident summary
customer_impact_summary: Summary of customer impact
current_milestone: Current milestone (e.g., started, acknowledged)
number: Incident number
incident_url: URL to the incident in FireHydrant
severity: Severity level
priority: Priority level
tag_list: List of tags associated with the incident
impacts: List of impacts associated with the incident
milestones: List of milestones associated with the incident

Example Output

{
  "data": {
    "current_milestone": "started",
    "customer_impact_summary": "Some customers are experiencing slow performance and intermittent errors when accessing the application.",
    "description": "Users are experiencing slow database queries and connection timeouts.",
    "id": "04d9fd1a-ba9c-417d-b396-58a6e2c374de",
    "impacts": [],
    "incident_url": "https://app.firehydrant.com/incidents/04d9fd1a-ba9c-417d-b396-58a6e2c374de",
    "milestones": [
      {
        "occurred_at": "2026-01-19T12:00:00Z",
        "type": "started"
      }
    ],
    "name": "Database connection issues",
    "number": 603,
    "priority": "P1",
    "severity": "SEV1",
    "summary": "Database connection pool exhausted causing cascading failures.",
    "tag_list": []
  },
  "timestamp": "2026-01-19T12:00:00Z",
  "type": "firehydrant.incident"
}