# Bolt

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

{% hint style="warning" %}
Prerequisites

[Scheduler Environment](https://docs.paradime.io/app-help/documentation/settings/connections/scheduler-environment) is connected to your data warehouse provider. 
{% endhint %}

{% hint style="info" %}
Coming from dbt Cloud™️? Import all your dbt™️ jobs with one click. See our doc [here](https://docs.paradime.io/app-help/guides/dbt-cloud-tm-importer).
{% endhint %}

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

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>📅 <strong>Creating Schedules</strong></td><td><p></p><p>Learn how to set up new schedules, configure settings, triggers, commands, and notifications for your dbt™ workflows.</p></td><td></td><td><a href="bolt/creating-schedules">creating-schedules</a></td></tr><tr><td>🔄 <strong>Managing Schedules</strong></td><td><p></p><p>Discover how to monitor schedule performance, analyze run logs, and troubleshoot issues in your active schedules.</p></td><td></td><td><a href="bolt/managing-schedules">managing-schedules</a></td></tr><tr><td>🔌 <strong>Bolt API and Webhooks</strong></td><td><p></p><p>Find documentation for Bolt's API endpoints and learn how to set up webhook integrations with your existing systems.</p></td><td></td><td><a href="bolt/bolt-api">bolt-api</a></td></tr><tr><td>⚙️ <strong>Special Environment Variables</strong></td><td><p></p><p>Reference guide for configuring specialized environment variables, including audit processing and runtime settings.</p></td><td></td><td><a href="bolt/special-environment-variables">special-environment-variables</a></td></tr><tr><td>🔗 <strong>Integrations</strong></td><td><p></p><p>Explore guides for connecting Bolt with various platforms, including Reverse ETL tools, BI solutions, and orchestration systems.</p></td><td></td><td><a href="broken-reference">Broken link</a></td></tr><tr><td>🚀 <strong>CI/CD</strong></td><td><p></p><p>Find setup instructions and best practices for implementing continuous integration and deployment with various version control platforms.</p></td><td></td><td><a href="bolt/ci-cd">ci-cd</a></td></tr></tbody></table>

{% hint style="info" %}
**New to Bolt?** Start with our [Creating Schedules](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules) guide to set up your first automated workflow.
{% endhint %}

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