3. Trigger Types
Last updated
Last updated
After configuring the Command Settings of a Bolt Schedule, you’ll define trigger conditions to specify when the schedule should initiate runs. Bolt Schedules support four distinct trigger types, each designed for specific use cases and workflows.
Runs the job at specific times and frequencies using cron syntax.
Daily data warehouse updates
Hourly incremental loads
Weekly report generation, monthly reconciliation.
Triggers when a specified run finishes its execution, in the same dbt project or from another Paradime workspace
Sequential data processing
Dependency-based execution to other projects
Chained transformations
Executes when code is merged into designated branches in your Git repository.
Continuous Deployment (CD) workflows to deploy changes right after merged in your Git Branch
External tool integration
Custom workflows (e.g. Data Orchestration)
Event-driven processing
Purpose: To automate jobs on a fixed schedule using cron syntax.
How it Works: Specify the timing and frequency with cron expressions, such as hourly, daily, weekly, or custom intervals.
From the Bolt UI, select Scheduled Run as the Trigger Type
Add your cron expression, you can use some of the preset option from the dropdown or build your own
For Manual (Ad-hoc) runs, simply set the cron schedule to OFF.
For assistance in setting up cron expressions use the cron preset dropdown, or visit crontab.guru.
Purpose: Initiates a Bolt Schedule once another specified Bolt Schedule completes, ensuring dependency-based execution for sequential workflows.
How it works: This trigger starts a Bolt Schedule only after a designated “parent” job finishes, creating a dependency chain.
From the Bolt UI, select On Run Completion as the Trigger Type
In the Workspace Name dropdown, select the Paradime Workspace containing the triggering Bolt Schedule.
In the Bolt Schedule Name dropdown, select the specific Bolt Schedule that will act as the trigger.
Select in which event the "parent" Schedule will trigger this new run, you can choose between:
Passed: the schedule will be trigger only if the "parent" complete successfully
Failed: the schedule will be trigger only if the "parent" complete and contains errors
Both Passed & Failed: the schedule will be trigger only irrespective of the "parent" status after completion
Purpose: Automatically runs Bolt pipelines when code is merged into designated branches in your Git repository.
Ensure that Paradime is connected to your GitHub repository and the GitHub App is installed This integration enables Paradime to detect merge events in specified branches.
Using another Git provider? Check our code templates to execute on Merge Runs.
From the Bolt UI, select On Merge as the Trigger Type
Click Deploy to publish your schedule.
Purpose: Allows external systems or custom scripts to programmatically trigger jobs via REST API.
How it Works: Uses Paradime’s REST API endpoints to initiate jobs based on events or actions outside of Paradime.
Configuration: When configuring a Bolt schedule and wants to trigger this via the Paradime API, select the Scheduled run trigger type click on the OFF button to let the Schedule being trigger only via the API.
For detailed configuration steps, refer to the Bolt API and Webhooks documentation.
Now, let's learn how to configure the Notification Settings of a Bolt Schedule.
Programmatically triggers jobs through endpoints.
