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

> Bolt is Paradime's dbt™ orchestration engine for scheduling production runs, monitoring pipelines, and shipping changes safely with built-in CI/CD workflows.

**Paradime's Bolt** is a comprehensive orchestration solution for deploying dbt™ in production. Instead of manually running commands, take advantage of Paradime's built-in scheduling to configure and automate your entire scheduling workflow.

<Warning>
  Prerequisites

  [Scheduler Environment](/products/settings/connections/scheduler-environment/index) is connected to your data warehouse provider.&#x20;
</Warning>

<Info>
  Coming from dbt Cloud™️? Import all your dbt™️ jobs with one click. See our doc [here](/guides/migrations/dbt-cloud-tm-importer/index).
</Info>

### Key Benefits

* Maintain fresh production data on a consistent schedule
* Execute CI/CD and production pipelines efficiently
* Swiftly identify and resolve deployment issues
* Utilize native integrations and custom webhooks for enhanced deployment

### Documentation Sections

<CardGroup cols={2}>
  <Card title="Schedule Anatomy" href="/products/bolt/creating-schedules/schedule-settings" horizontal>
    🧩 Understand the building blocks of a schedule: settings, commands, triggers, notifications, environment variables, and self-healing.
  </Card>

  <Card title="Deploy Schedules" href="/products/bolt/creating-schedules/deploy" horizontal>
    📅 Build and ship schedules through the UI or as code with YAML, and start from pre-built job templates.
  </Card>

  <Card title="Managing Schedules" href="/products/bolt/managing-schedules/index" horizontal>
    🔄 Discover how to monitor schedule performance, analyze run logs, and troubleshoot issues in your active schedules.
  </Card>

  <Card title="CI/CD" href="/products/bolt/ci-cd/index" horizontal>
    🚀 Find setup instructions and best practices for implementing continuous integration and deployment with various version control platforms.
  </Card>

  <Card title="Bolt API" href="/products/bolt/bolt-api" horizontal>
    🔌 Trigger, monitor, and retry Bolt runs programmatically, including from external orchestrators like Airflow and Dagster, via the API, SDK, CLI, or webhooks.
  </Card>
</CardGroup>

<Info>
  **New to Bolt?** Start with [Schedule Anatomy](/products/bolt/creating-schedules/schedule-settings) to learn the building blocks, then [Deploy Schedules](/products/bolt/creating-schedules/deploy) to set up your first automated workflow.
</Info>

### Bolt Terminology

Understanding these key terms is crucial when configuring your schedules:

| Term                     | Description                                                              | Example                                                | Required |
| ------------------------ | ------------------------------------------------------------------------ | ------------------------------------------------------ | -------- |
| Schedule Type            | Execution type for your scheduled dbt™ run                               | `Standard`, `Deferred`, or `Turbo CI`                  | Yes      |
| Name                     | Identifier for your dbt™ schedule                                        | `hourly_schedule`                                      | Yes      |
| Description              | The purpose of your bolt Schedule                                        | `schedule dbt run on an hourly basis`                  | Yes      |
| Owner Email              | Schedule owner's email                                                   | `me@email.com`                                         | Yes      |
| Git Branch               | Branch used for schedule execution                                       | `main`                                                 | Yes      |
| Commands                 | dbt™ commands to execute (can be multiple)                               | <p><code>dbt run</code><br /><code>dbt test</code></p> | Yes      |
| Trigger Type             | How the schedule is initiated                                            | `Scheduled run`, `On Run Completion`, `On Merge`       | Yes      |
| Cron Schedule            | Frequency of schedule runs (UTC-based) for Schedules Runs                | @hourly                                                | No       |
| SLA Threshold            | Trigger an alert when the schedule has passed a time threshold (minutes) | `30`                                                   | No       |
| Notification Destination | The destination of a notification                                        | `Email`, `Slack`, and/ or `MS Teams`                   | No       |
| Notification Type        | Notifications received after a scheduled run                             | `Success`, `Failure`, `SLA`                            | No       |


## Related topics

- [Bolt Pipeline Agent](/products/dino-ai/bolt-pipeline-agent/index.md)
- [Bolt Pipeline Healer](/guides/programmable-agents/bolt-pipeline-healer.md)
- [Bolt Pipeline Retry Agent](/guides/programmable-agents/bolt-pipeline-retry-agent.md)
- [DinoAI Bolt Pipeline Agent Self-Healing](/products/dino-ai/bolt-pipeline-agent/self-healing.md)
- [Azure Data Factory (ADF)](/integrations/azure-data-factory-adf.md)