> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Send failures to your incident tools

> Add an incident trigger to a Bolt schedule so a failed run automatically creates an incident in PagerDuty, Datadog, incident.io, or New Relic.

Route Bolt run failures into the on-call stack your team already watches. When a schedule fails, an incident trigger creates an incident in PagerDuty, Datadog, incident.io, or New Relic, with a link back to the run. This guide adds one to a schedule.

<Note>
  **Prerequisites**

  * A [Bolt schedule](/guides/paradime-101/running-dbt-in-production-with-bolt/creating-bolt-schedules) you can edit.
  * Your incident tool connected to Paradime: [PagerDuty](/integrations/pagerduty), [Datadog](/integrations/datadog), [incident.io](/integrations/incident.io), or [New Relic](/integrations/new-relic).

  Estimated time: 10 minutes.
</Note>

## Steps

<Steps>
  <Step title="Add an incident trigger to the schedule">
    On the schedule, open the **Triggers integration** section, select **Add integration**, and choose your tool (for example, PagerDuty).
  </Step>

  <Step title="Configure the incident">
    Set the fields that shape the incident created on failure. For PagerDuty, for example: the from email, incident type, impacted service, urgency, priority, escalation policy, and any extra users to notify. Select **Confirm** to activate the trigger for this schedule.

    <Info>
      Incident triggers only fire on **failed** runs. Successful runs never create an incident.
    </Info>
  </Step>

  <Step title="Or define it as code">
    If you [manage schedules as code](/guides/orchestrate-data-pipelines/manage-schedules-as-code), configure the incident trigger in the schedule's [`integrations` block](/products/bolt/creating-schedules/schedules-as-code/configuration-reference) instead of the UI.
  </Step>
</Steps>

<Check>
  Trigger a failing run. Paradime creates an incident in your tool with the schedule name, workspace, run ID, and a link to the Paradime run logs. Each trigger runs independently, so if one tool errors, the others still fire.
</Check>

## Next steps

<CardGroup cols={2}>
  <Card title="Set up alerts" href="/guides/orchestrate-data-pipelines/set-up-alerts" icon="bell">
    Customize the Slack and Teams messages for the same failures.
  </Card>

  <Card title="Set up self-healing" href="/guides/orchestrate-data-pipelines/set-up-self-healing" icon="shield">
    Attempt an automatic fix before paging a human.
  </Card>

  <Card title="Trigger integrations reference" href="/products/bolt/creating-schedules/trigger-integrations/index" icon="plug">
    Every incident tool and its fields.
  </Card>

  <Card title="Incident templates" href="/guides/orchestrate-data-pipelines/templates/incident-templates/index" icon="workflow">
    Template-based incident creation, including Rootly.
  </Card>
</CardGroup>


## Related topics

- [Bolt Trigger Integrations](/products/bolt/creating-schedules/trigger-integrations/index.md)
- [Send Elementary dbt alerts to Datadog](/integrations/elementary-data/sending-alerts/datadog-alerts.md)
- [Send Elementary alerts to Slack](/guides/orchestrate-data-pipelines/templates/observability-templates/send-elementary-alerts-to-slack.md)
- [Incident.io](/integrations/incident.io.md)
- [Send Elementary alerts to MS Teams](/guides/orchestrate-data-pipelines/templates/observability-templates/send-elementary-alerts-to-ms-teams.md)