Skip to main content

​
Overview

Connect FireHydrant to enable TierZero to receive incident events and participate in your incident response workflow. TierZero can automatically investigate incidents reported through FireHydrant.

​
Prerequisites

  • Administrative access to your FireHydrant account
  • Permission to configure webhook integrations

​
Setup Instructions

​
Step 1: Navigate to Integration Settings

  1. Log into your TierZero dashboard
  2. Go to Settings → Integrations
  3. Click Connect next to FireHydrant

​
Step 2: Configure Webhook

  1. TierZero will display a webhook URL. Copy it
  2. In FireHydrant, go to Settings → Integrations
  3. Add a webhook integration pointing to the TierZero URL
  4. Enter the webhook secret provided by TierZero
  5. Select the incident events to forward (incident creation, updates, milestones)

​
Step 3: Create a Webhook Subscription

  1. Back in TierZero, enter the webhook details:
    • Name: A descriptive name (e.g., “FireHydrant Production”)
    • Remote ID: The integration identifier from FireHydrant
    • Secret: The webhook authentication secret
See Webhook Subscriptions for more details.

​
What TierZero Accesses

  • Incident lifecycle events: Creation, updates, status changes, milestones
  • Incident metadata: Severity, affected services, responders

​
Using with Alert Agents

After creating a webhook subscription, connect it to an Alert Agent:
  1. Create or edit an Alert Agent
  2. Select Webhook as the alert source
  3. Choose your FireHydrant webhook subscription
  4. TierZero will automatically investigate incidents reported through FireHydrant

​
Using with Incident Agent

FireHydrant incidents can trigger the Incident Agent, which will auto-join the corresponding Slack channel and begin real-time investigation.

​
Security

  • Webhook signatures are validated on every incoming event
  • Secrets are encrypted at rest and never exposed in API responses
  • Revoke by removing the webhook in FireHydrant

​
Troubleshooting

​
Incidents Not Triggering Investigations

  • Verify the webhook URL is correct in FireHydrant
  • Check that the webhook secret matches
  • Ensure an Alert Agent is connected to the webhook subscription
  • Review FireHydrant’s webhook delivery logs for errors