# 6. Trigger Integrations

After configuring [Schedule Settings](/app-help/documentation/bolt/creating-schedules/trigger-types.md) and [Command Settings](/app-help/documentation/bolt/creating-schedules/command-settings.md) of a Bolt Schedule, you can set up triggers to automate actions when runs complete. Trigger Settings allow you to connect Bolt to external tools and services, enabling automated workflows based on your pipeline execution results.

<figure><img src="/files/y9UNpPn3A4vShSg82og6" alt=""><figcaption></figcaption></figure>

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

<table data-view="cards" data-full-width="true"><thead><tr><th align="center"></th><th align="center"></th></tr></thead><tbody><tr><td align="center"><strong>Datadog</strong></td><td align="center">Create incidents in Datadog alongside infrastructure monitoring</td></tr><tr><td align="center"><strong>incident.io</strong></td><td align="center">Create Slack-native incidents with automatic channel creation</td></tr><tr><td align="center"><strong>PagerDuty</strong></td><td align="center">Create incidents in PagerDuty with on-call escalation</td></tr><tr><td align="center"><strong>New Relic</strong></td><td align="center"></td></tr></tbody></table>

{% hint style="info" %}
**Note:** Incident management triggers only activate on **failed runs**. Successful runs do not trigger incident creation.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/trigger-integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.