> ## 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.

# Bolt Trigger Integrations

> Set up Bolt schedule triggers to run pipelines on events from external tools like ingestion jobs, reverse-ETL syncs, and BI dashboard refreshes.

Trigger integrations route run outcomes to your incident and monitoring tools after a schedule finishes. Add one to send Bolt run results to incident.io, PagerDuty, Datadog, or New Relic, so failures reach the systems your team already watches.

### Overview

With Bolt Triggers, you can:

* Automatically execute actions when runs complete
* Connect Bolt to external tools and services
* Configure which schedules activate specific triggers
* Customize trigger behavior and parameters
* Integrate pipeline execution with your broader data and DevOps workflows

### How Triggers Work

Triggers are evaluated **after a Bolt run completes**. Here's the execution flow:

1. **Bolt Schedule Execution**: Your configured commands run in sequence according to Command Settings
2. **Run Completion**: The schedule completes with either a success or failure status
3. **Trigger Evaluation**: Paradime evaluates configured triggers based on the run outcome
4. **Action Execution**: Triggers automatically execute their configured actions with run details

### Trigger Execution Logic

Paradime follows a specific trigger execution logic to ensure actions are executed appropriately:

1. **Run Status Detection**: When a Bolt schedule completes, Paradime determines the run status (success or failure)
2. **Trigger Filtering**: Only triggers configured for the specific run outcome are evaluated
3. **Automatic Action Execution**: Each connected service receives relevant information such as:
   * Schedule name and workspace details
   * Direct link to Paradime run logs
   * Run ID and execution timestamps
   * Commands that were executed
   * Branch information
   * Run status and details
4. **Independent Trigger Execution**: Each trigger operates independently - if one integration fails, others will still execute

### Available Trigger Types

#### Incident Management Triggers

Automatically create incidents in your incident management platform when runs **fail**.

<CardGroup cols={2}>
  <Card title="Datadog" href="/products/bolt/creating-schedules/trigger-integrations/trigger-datadog-incidents" horizontal>
    Create incidents in Datadog alongside infrastructure monitoring
  </Card>

  <Card title="incident.io" href="/products/bolt/creating-schedules/trigger-integrations/trigger-incident.io-incidents" horizontal>
    Create Slack-native incidents with automatic channel creation
  </Card>

  <Card title="PagerDuty" href="/products/bolt/creating-schedules/trigger-integrations/trigger-pagerduty-alarms" horizontal>
    Create incidents in PagerDuty with on-call escalation
  </Card>

  <Card title="New Relic" href="/products/bolt/creating-schedules/trigger-integrations/trigger-new-relic-incidents" horizontal>
    Create incidents in New Relic tied to your alerting and observability
  </Card>
</CardGroup>

<Info>
  **Note:** Incident management triggers only activate on **failed runs**. Successful runs do not trigger incident creation.
</Info>

<Card title="Define this as code" icon="code" href="/products/bolt/creating-schedules/schedules-as-code/configuration-reference#trigger-integration" horizontal>
  Configure the `integrations` block for incident.io, PagerDuty, Datadog, or New Relic.
</Card>


## Related topics

- [Trigger Bolt schedules from Dagster](/products/bolt/external-triggers/dagster.md)
- [Bolt API](/developers/graphql-api/api-reference/bolt-api.md)
- [Trigger Bolt schedules from Airflow](/products/bolt/external-triggers/airflow.md)
- [Bolt API and schedule trigger errors](/get-help/error-list/bolt-api-and-schedule-trigger-errors.md)
- [Configuration Reference](/products/bolt/creating-schedules/schedules-as-code/configuration-reference.md)