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.
Prerequisites
Scheduler Environment is connected to your data warehouse provider.
Coming from dbt Cloud™️? Import all your dbt™️ jobs with one click. See our doc here.
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
📅 Creating Schedules
Learn how to set up new schedules, configure settings, triggers, commands, and notifications for your dbt™ workflows.
🔄 Managing Schedules
Discover how to monitor schedule performance, analyze run logs, and troubleshoot issues in your active schedules.
🔌 Bolt API and Webhooks
Find documentation for Bolt's API endpoints and learn how to set up webhook integrations with your existing systems.
⚙️ Special Environment Variables
Reference guide for configuring specialized environment variables, including audit processing and runtime settings.
🔗 Integrations
Explore guides for connecting Bolt with various platforms, including Reverse ETL tools, BI solutions, and orchestration systems.
🚀 CI/CD
Find setup instructions and best practices for implementing continuous integration and deployment with various version control platforms.
New to Bolt? Start with our Creating Schedules guide to set up your first automated workflow.
Bolt Terminology
Understanding these key terms is crucial when configuring your schedules:
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)
dbt run
dbt test
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
Last updated