Create Incident in incident.io

Learn how to automatically create incident.io incidents when dbt™ runs fail in Bolt. This integration helps data teams track and respond to pipeline failures efficiently by connecting Bolt's pipeline monitoring with incident.io's modern incident management platform.


What You'll Get

When a run fails, Bolt automatically creates an incident.io incident containing:

  • Incident name with schedule and workspace details

  • Incident summary including:

    • Direct link to Paradime run logs

    • Run ID and execution details

    • Start and end timestamps

    • Commands executed

    • Branch information

  • Severity level based on your configuration


Setup Guide

Set up incident.io incident creation for failed runs. Follow the steps below, and watch our interactive tutorial.

Step 1: Gather Your incident.io Information

  1. Generate API Key:

  2. Find Your Severity ID:

    Method 1: Using the API

    • Make a GET request to https://api.incident.io/v1/severities with your API key

    • This returns all severities with their corresponding IDs

    Method 2: Through the Web Interface

    Both methods will give you the unique severity ID (e.g., 01FCNDV6P870EA6S7TK1DSYDG0)

Step 2: Configure the Template in Paradime

  1. From the Bolt home screen, go to Templates

  2. Click Incidents and select "Create incident in incident.io"

  3. Fill in the following fields:

    • Select Schedules: Choose the schedules for which you want to trigger this webhook. Leave blank or select all for all schedules without filtering

    • API Key: Enter the API key you generated in incident.io

    • Visibility: Choose incident visibility:

      • public - Open to anyone in your Slack workspace

      • private - Invite-only access

    • Severity Id: Enter the severity ID you found in Step 1

  4. Click "Connect"

Step 3: Test the Integration

  1. Run a Bolt schedule manually that will fail (the webhook only triggers on failed runs)

  2. After the run fails:

    • Check your incident.io dashboard for the new incident

    • Verify a Slack channel was created (if configured)

    • Confirm the incident contains all run failure details

Last updated

Was this helpful?