# Paradime: Products Bolt

## Bolt

- [Bolt Pipelines](https://docs.paradime.io/products/bolt/index.md): Bolt is Paradime's dbt™ orchestration engine for scheduling production runs, monitoring pipelines, and shipping changes safely with built-in CI/CD workflows.

### Schedule Anatomy

- [Triggers](https://docs.paradime.io/products/bolt/creating-schedules/trigger-types.md): Choose how a Bolt schedule runs: on a cron schedule, when another schedule finishes, on merge, on pull request via Turbo CI, or on demand via the Paradime API.
- [Schedule Settings](https://docs.paradime.io/products/bolt/creating-schedules/schedule-settings.md): Name a Bolt schedule, set its owner and Git branch, and optionally defer to a previous run to compare state and build incrementally.
- [Self-Healing settings for a Bolt schedule](https://docs.paradime.io/products/bolt/creating-schedules/self-healing.md): Turn on self-healing in a Bolt schedule's setup panel and pick which DinoAI agent runs when the schedule fails, from the Bolt Pipeline Healer to custom agents.
- [Notifications](https://docs.paradime.io/products/bolt/creating-schedules/notification-settings.md): Alert your team when a Bolt schedule succeeds, fails, or breaches its SLA, via email, Slack, or Microsoft Teams, with per-destination outcome toggles.
- [Alert Templates](https://docs.paradime.io/products/bolt/creating-schedules/alert-templates.md): Customize Slack and Microsoft Teams Bolt notifications with reusable Jinja2 templates for run status, command details, and error context.
- [Environment Variable Overrides](https://docs.paradime.io/products/bolt/creating-schedules/schedules-environment-variables.md): Override environment variables per Bolt schedule. A schedule inherits workspace and environment values, and its own override wins for that specific job.
- [Environment Variables in Commands](https://docs.paradime.io/products/bolt/creating-schedules/environment-variables-in-commands.md): Reference environment variables inside Bolt schedule commands so dbt™ runs pick up secrets, connection settings, and per-environment values at runtime.
- [Audit Variables](https://docs.paradime.io/products/bolt/creating-schedules/audit-variables.md): Bolt injects audit variables like run ID, schedule name, and trigger type into every dbt™ command so you can log, trace, and audit each production run.

#### Commands

- [Commands](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/index.md): Add commands to a Paradime Bolt schedule: run dbt™, trigger data syncs and orchestration, refresh BI dashboards, run data quality checks, and more.
- [Sync Airbyte Connection](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/airbyte-connector-sync.md): Add a Sync Airbyte Connection command to a Paradime Bolt schedule to trigger connector syncs, then run dbt™ transformations on the fresh data.
- [Trigger Airflow DAG](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/airflow-dag.md): Add a Trigger Airflow DAG command to a Paradime Bolt schedule to kick off Apache Airflow DAG runs as part of your dbt™ orchestration pipeline.
- [Run AWS ECS Task](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/aws-ecs-task.md): Add a Run AWS ECS Task command to a Paradime Bolt schedule to launch ECS task definitions from the Paradime CLI as part of your dbt™ pipeline.
- [Run AWS Glue](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/aws-glue.md): Add a Run AWS Glue command to a Paradime Bolt schedule to trigger Glue workflows or jobs from the Paradime CLI alongside your dbt™ transformations.
- [Invoke AWS Lambda](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/aws-lambda.md): Add an Invoke AWS Lambda command to a Paradime Bolt schedule to run serverless functions from the Paradime CLI as part of your dbt™ pipeline.
- [Run AWS SageMaker Pipeline](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/aws-sagemaker-pipeline.md): Add a Run AWS SageMaker Pipeline command to a Paradime Bolt schedule to trigger ML pipelines from the Paradime CLI after your dbt™ models run.
- [Run AWS Step Functions](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/aws-step-functions.md): Add a Run AWS Step Functions command to a Paradime Bolt schedule to start state machines from the Paradime CLI as part of your dbt™ pipeline.
- [Run Azure Data Factory Pipeline](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/azure-data-factory-pipeline.md): Add a Run Azure Data Factory Pipeline command to a Paradime Bolt schedule to trigger ADF pipelines from the Paradime CLI alongside dbt™ runs.
- [Run BigQuery Scheduled Query](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/bigquery-scheduled-query.md): Add a Run BigQuery Scheduled Query command to a Paradime Bolt schedule to trigger BigQuery Data Transfer queries from the Paradime CLI on demand.
- [Toggle Paradime Bolt Schedule](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-bolt-schedule-toggle-commands.md): Add a Toggle Paradime Bolt Schedule command to suspend or activate another Bolt schedule from within a schedule using the Paradime CLI on demand.
- [Refresh Paradime Catalog](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-refresh-catalog.md): Add a Refresh Paradime Catalog command to a Bolt schedule to rebuild the Paradime Data Catalog on demand by running dbt docs generate for your project.
- [Push to DataHub](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/datahub-sync.md): Add a Push to DataHub command to a Paradime Bolt schedule to send dbt™ artifacts to DataHub for metadata ingestion and lineage using the CLI.
- [Run dbt™ Command](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/dbt-tm-commands.md): Add dbt™ commands to a Paradime Bolt schedule to run, test, build, and orchestrate your dbt™ project on a managed cloud runner with Paradime.
- [Run DinoAI Background Agent](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-dinoai-agent-trigger.md): Add a Run DinoAI Background Agent command to a Paradime Bolt schedule to give a DinoAI agent a task to run as part of your dbt™ pipeline.
- [Run Elementary](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/elementary-commands.md): Add an Elementary command to a Paradime Bolt schedule to send data-quality alerts or generate Elementary observability reports after each dbt™ run.
- [Sync Fivetran Connector](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/fivetran-connector-sync.md): Add a Sync Fivetran Connector command to a Paradime Bolt schedule to trigger Fivetran syncs, then run dbt™ transformations on the freshly loaded data.
- [Invoke GCP Cloud Function](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/gcp-cloud-function.md): Add an Invoke GCP Cloud Function command to a Paradime Bolt schedule to run event-driven serverless logic from the Paradime CLI in your pipeline.
- [Run GCP Cloud Run Job](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/gcp-cloud-run-job.md): Add a Run GCP Cloud Run Job command to a Paradime Bolt schedule to execute containerized jobs from the Paradime CLI as part of your dbt™ pipeline.
- [Run GCP Dataflow](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/gcp-dataflow.md): Add a Run GCP Dataflow command to a Paradime Bolt schedule to launch Dataflow jobs from a template using the Paradime CLI in your dbt™ pipeline.
- [Run GCP Dataproc Job](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/gcp-dataproc-job.md): Add a Run GCP Dataproc Job command to a Paradime Bolt schedule to submit Spark and Hadoop jobs from the Paradime CLI alongside your dbt™ runs.
- [Control GCP Datastream](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/gcp-datastream.md): Add a Control GCP Datastream command to a Paradime Bolt schedule to start, pause, or resume Datastream CDC streams from the Paradime CLI on demand.
- [Trigger GitHub Actions](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/github-actions.md): Add a Trigger GitHub Actions command to a Paradime Bolt schedule to run GitHub Actions workflows from the Paradime CLI as part of your dbt™ pipeline.
- [Run Hex Project](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/hex-project.md): Add a Run Hex Project command to a Paradime Bolt schedule to trigger Hex notebook and data-app runs from the Paradime CLI after your dbt™ models run.
- [Sync Hightouch](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/hightouch-sync.md): Add a Sync Hightouch command to a Paradime Bolt schedule to trigger Hightouch reverse-ETL syncs from the Paradime CLI after your dbt™ models refresh.
- [Run Lightdash](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/lightdash-commands.md): Add a Run Lightdash command to a Paradime Bolt schedule to validate, compile, and sync changes to your Lightdash project after each dbt™ run.
- [Run Matillion Pipeline](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/matillion-pipeline.md): Add a Run Matillion Pipeline command to a Paradime Bolt schedule to trigger Matillion ELT pipelines from the Paradime CLI alongside your dbt™ runs.
- [Run MonteCarlo CLI](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/monte-carlo-commands.md): Add a Run MonteCarlo CLI command to a Paradime Bolt schedule to upload dbt™ artifacts to Monte Carlo for data observability after each dbt™ run.
- [Refresh PowerBI Dataset](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/power-bi-dataset-refresh.md): Add a Refresh PowerBI Dataset command to a Paradime Bolt schedule to refresh Power BI semantic models so dashboards stay in sync with each dbt™ run.
- [Run pre-commit](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/pre-commit.md): Add a Run pre-commit command to a Paradime Bolt schedule to run pre-commit hooks against your dbt™ project for linting, formatting, and checks.
- [Run Python Script](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/python-scripts.md): Add a Run Python Script command to a Paradime Bolt schedule with Poetry dependency management and environment variables for secrets and API keys.
- [Refresh Tableau Data Source](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/tableau-data-source-refresh.md): Add a Refresh Tableau Data Source command to a Paradime Bolt schedule to refresh Tableau data source extracts so dashboards stay in sync with dbt™ runs.
- [Refresh Tableau Workbook](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/tableau-workbook-refresh.md): Add a Refresh Tableau Workbook command to a Paradime Bolt schedule to refresh Tableau workbook extracts so dashboards stay in sync with each dbt™ run.
- [Trigger Zapier](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/zapier.md): Add a Trigger Zapier command to a Paradime Bolt schedule to fire Zapier webhooks from the Paradime CLI and kick off automation across thousands of apps.

#### Integrations

- [Bolt Trigger Integrations](https://docs.paradime.io/products/bolt/creating-schedules/trigger-integrations/index.md): Set up Bolt schedule triggers to run pipelines on events from external tools like ingestion jobs, reverse-ETL syncs, and BI dashboard refreshes.
- [Trigger Datadog Incidents](https://docs.paradime.io/products/bolt/creating-schedules/trigger-integrations/trigger-datadog-incidents.md): Configure Datadog triggers in Paradime Bolt to automatically create Datadog incidents when a scheduled dbt™ run fails, so your on-call is paged.
- [Trigger incident.io Incidents](https://docs.paradime.io/products/bolt/creating-schedules/trigger-integrations/trigger-incident.io-incidents.md): Configure incident.io triggers in Paradime Bolt to automatically open incident.io incidents when a scheduled dbt™ run fails or overruns.
- [Trigger PagerDuty Alarms](https://docs.paradime.io/products/bolt/creating-schedules/trigger-integrations/trigger-pagerduty-alarms.md): Configure PagerDuty triggers in Paradime Bolt to automatically create PagerDuty incidents when a scheduled dbt™ run fails, paging your on-call.
- [Trigger New Relic Incidents](https://docs.paradime.io/products/bolt/creating-schedules/trigger-integrations/trigger-new-relic-incidents.md): Configure New Relic triggers in Paradime Bolt to automatically create New Relic incidents when a scheduled dbt™ run fails or overruns its SLA.

### Deploy Schedules

- [Deploy Schedules](https://docs.paradime.io/products/bolt/creating-schedules/deploy.md): Build a Bolt schedule in the UI, then deploy it directly, open a pull request, or download the YAML. Every schedule is also editable as code.
- [Deploy from the UI](https://docs.paradime.io/products/bolt/creating-schedules/deploy-from-ui.md): Deploy a Bolt schedule built in the UI: publish it directly, open a pull request with the GitHub app, or download the YAML to commit yourself.

#### Schedules as Code

- [Schedules as Code](https://docs.paradime.io/products/bolt/creating-schedules/schedules-as-code/index.md): Manage Bolt schedules as code with `paradime_schedules.yml`: version-control schedules in Git, review changes in pull requests, and deploy via GitOps.
- [Configuration Reference](https://docs.paradime.io/products/bolt/creating-schedules/schedules-as-code/configuration-reference.md): Full YAML reference for Bolt Schedules as Code: schedule fields, commands, triggers, notifications, integrations, and self-healing options.
- [The .bolt/ Folder](https://docs.paradime.io/products/bolt/creating-schedules/schedules-as-code/modular-schedules-with-the-.bolt-folder.md): Split Bolt schedules across multiple YAML files inside a .bolt/ folder to keep each schedule modular, easier to review, and simpler to reuse.
- [Editing YAML in the UI](https://docs.paradime.io/products/bolt/creating-schedules/schedules-as-code/editing-yaml-schedules-from-the-paradime-ui.md): Edit Bolt YAML schedules directly from the Paradime UI: change commands, triggers, and settings, then open a pull request to deploy your update.
- [Deploying from a Custom Branch](https://docs.paradime.io/products/bolt/creating-schedules/schedules-as-code/deploying-yaml-schedules-from-a-custom-branch.md): Deploy Bolt YAML schedules from a custom Git branch instead of the default production branch to test schedule changes safely before merging.
- [JSON Schema](https://docs.paradime.io/products/bolt/creating-schedules/schedules-as-code/json-schema-bolt-schedules.md): JSON Schema for validating `paradime_schedules.yml`: schedule fields, triggers, notifications, integrations, and execution options for Bolt schedules.

### Managing Schedules

- [Managing Schedules](https://docs.paradime.io/products/bolt/managing-schedules/index.md): The Schedules page lists every Bolt schedule with its latest run status, owner, trigger, and next run, so you can find, run, and open schedules.
- [Schedule Details](https://docs.paradime.io/products/bolt/managing-schedules/schedule-details.md): Open a Bolt schedule to see its configuration, pipeline graph, run statistics, and full run history, and to run, edit, or clone it.
- [Run Details](https://docs.paradime.io/products/bolt/managing-schedules/run-details.md): Inspect a Bolt run: the pipeline, executed nodes, and model timeline, its succeeded/errors/skipped counts, and retry a failed run from failure or from scratch.
- [Run Logs and Artifacts](https://docs.paradime.io/products/bolt/managing-schedules/run-logs-and-artifacts.md): Inspect each command in a Bolt run: the DinoAI summary, full debuggable logs, generated artifacts like Run SQL, Compiled SQL, and JSON, plus source freshness.
- [Retrying a Run](https://docs.paradime.io/products/bolt/managing-schedules/retrying-a-run.md): Retry a failed Bolt run in one click: resume from the failed command or re-run every command. Each retry creates a new run and leaves the original intact.

#### External Triggers

- [External Triggers](https://docs.paradime.io/products/bolt/external-triggers/index.md): Trigger Paradime Bolt schedules from outside Paradime: call the Bolt API directly, or run them from an external orchestrator like Airflow or Dagster.
- [Bolt API](https://docs.paradime.io/products/bolt/bolt-api.md): Trigger, monitor, and manage Bolt runs programmatically from Airflow, Dagster, or any external system using the Bolt API, Python SDK, CLI, or webhooks.
- [Trigger Bolt schedules from Airflow](https://docs.paradime.io/products/bolt/external-triggers/airflow.md): Trigger Paradime Bolt schedules from Apache Airflow DAGs using the Paradime dbt provider, wait for runs to finish, and download dbt run artifacts.
- [Trigger Bolt schedules from Dagster](https://docs.paradime.io/products/bolt/external-triggers/dagster.md): Run Paradime Bolt schedules as Dagster assets using Paradime's dagster-dbt integration: load a schedule, execute it, and retrieve its artifacts.

### CI/CD

- [Bolt CI/CD for dbt™ pull requests and deploys](https://docs.paradime.io/products/bolt/ci-cd/index.md): Overview of Paradime's CI/CD suite for dbt™: Turbo CI runs models changed in a pull request, and Lineage Diff surfaces column-level impact for reviewers.

#### Turbo CI

- [Turbo CI for dbt™ pull requests](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/index.md): Turbo CI runs and tests only your changed dbt™ models on each pull request in a temporary schema, on GitHub, GitLab, Azure DevOps, or BitBucket.
- [Turbo CI on Azure DevOps pull requests](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/azure-devops.md): Trigger a Paradime Turbo CI Bolt schedule from an Azure Pipeline to build and test only the dbt™ models changed in a pull request before merge.
- [Turbo CI on BitBucket pull requests](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/bitbucket.md): Trigger a Paradime Turbo CI Bolt schedule from a BitBucket pipeline to build and test only the dbt™ models changed in a pull request before merge.
- [Turbo CI on GitHub pull requests](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/github.md): Run Paradime Turbo CI on GitHub pull requests with the native app, including DinoAI failure summaries and a schedule parse check for dbt™ projects.
- [Turbo CI on GitLab merge requests](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/gitlab.md): Trigger a Paradime Turbo CI Bolt schedule from a GitLab pipeline to build and test only the dbt™ models changed in a merge request before it lands.
- [Turbo CI with Snowflake shared databases](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/snowflake-shared-databases.md): Configure dbt™ clone to fall back to views for models in Snowflake shared databases, which cannot be zero-copy cloned during Turbo CI runs.
- [Turbo CI Schema Cleanup macro for dbt™](https://docs.paradime.io/products/bolt/ci-cd/turbo-ci/paradime-turbo-ci-schema-cleanup.md): Use the Paradime Turbo CI schema cleanup dbt™ macro to identify and drop temporary schemas created by Turbo CI runs and keep your warehouse tidy.

#### Continuous Deployment

- [Continuous Deployment](https://docs.paradime.io/products/bolt/ci-cd/continuous-deployment/index.md): Run a Paradime Bolt schedule on merge to deploy dbt™ changes to production, using the native GitHub app or Azure, GitLab, or BitBucket pipelines.
- [Continuous Deployment with GitHub for dbt™](https://docs.paradime.io/products/bolt/ci-cd/continuous-deployment/github.md): Deploy dbt™ changes on merge to main with Paradime's native GitHub app or by triggering a Bolt CD schedule from GitHub Actions using the Bolt API.
- [Continuous Deployment with Azure Pipelines](https://docs.paradime.io/products/bolt/ci-cd/continuous-deployment/azure-devops.md): Trigger a Paradime Bolt CD schedule from an Azure Pipeline on merge to deploy dbt™ changes to production using the Bolt API and Account API keys.
- [Continuous Deployment with BitBucket Pipelines](https://docs.paradime.io/products/bolt/ci-cd/continuous-deployment/bitbucket.md): Trigger a Paradime Bolt CD schedule from a BitBucket pipeline on merge to deploy dbt™ changes to production using the Bolt API and Account API keys.
- [Continuous Deployment with GitLab Pipelines](https://docs.paradime.io/products/bolt/ci-cd/continuous-deployment/gitlab.md): Trigger a Paradime Bolt CD schedule from a GitLab pipeline on merge to deploy dbt™ changes to production using the Bolt API and Account API keys.

#### Column-Level Lineage Diff

- [Column-Level Lineage Diff](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/index.md): Column-Level Lineage Diff shows the exact upstream and downstream columns impacted by a dbt™ pull request, so reviewers can approve changes confidently.
- [Column-Level Lineage Diff on GitHub](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/github.md): Set up Paradime Column-Level Lineage Diff on GitHub pull requests to post upstream and downstream column-impact reports as PR comments for dbt™ changes.
- [Column-Level Lineage Diff on GitLab](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/gitlab.md): Set up Paradime Column-Level Lineage Diff on GitLab merge requests to post upstream and downstream column-impact reports as MR comments for dbt™ changes.
- [Column-Level Lineage Diff on Azure DevOps](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/azure-devops.md): Set up Paradime Column-Level Lineage Diff on Azure DevOps pull requests to post upstream and downstream column-impact reports as PR comments for dbt™ changes.
- [Column-Level Lineage Diff on BitBucket](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/bitbucket.md): Set up Paradime Column-Level Lineage Diff on BitBucket pull requests to post upstream and downstream column-impact reports as PR comments for dbt™ changes.
- [dbt™ mesh](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/dbt-mesh.md): Configure Paradime Bolt Turbo CI for dbt™ Mesh: run PR checks that surface mesh-aware lineage and column diffs across your linked dbt™ projects.
- [Column-Level Lineage Diff for Looker](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/looker.md): See which Looker views, explores, looks, and dashboards are impacted by a dbt™ pull request so you can review changes before they reach production.
- [Tableau](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/tableau.md): Configure Paradime Bolt Turbo CI to show Tableau lineage on pull requests, so reviewers see which dashboards depend on the dbt™ models you're changing.
- [Column-Level Lineage Diff for ThoughtSpot](https://docs.paradime.io/products/bolt/ci-cd/lineage-diff/thoughtspot.md): See which ThoughtSpot worksheets, answers, and liveboards are impacted by a dbt™ pull request so you can review changes before they reach production.