Skip to main content
The trigger defines when a Bolt schedule runs. It is the first thing you configure when creating a schedule: pick a trigger type, then add commands, schedule settings, and notifications.

​
Trigger types

​
Scheduled

Runs the schedule automatically on a cron schedule.
  1. Select Scheduled as the trigger type.
  2. Enter a cron schedule (for example, 0 0 * * *). Use Choose a preset for common intervals, or Cron help to build your own.
  3. Select a timezone. The default is UTC.
For help writing cron expressions, use the Choose a preset dropdown, or visit crontab.guru.

​
On run completion

Runs the schedule after another Bolt schedule finishes, so you can chain dependent workflows, including across Paradime workspaces.
  1. Select On run completion as the trigger type.
  2. In the Workspace Name dropdown, select the Paradime workspace that contains the triggering schedule.
  3. In the Bolt Schedule Name dropdown, select the schedule that acts as the trigger.
  4. Choose which parent outcome starts this run:
    • Passed — only when the parent schedule completes successfully.
    • Failed — only when the parent schedule completes with errors.
    • Passed & Failed — whenever the parent schedule completes, regardless of outcome.

​
On merge

Runs the schedule when a pull request is merged into the branch, for continuous deployment workflows.
Prerequisite: GitHub integrationParadime must be connected to your GitHub repository with the GitHub App installed so it can detect merge events on the branch.Using another Git provider? Use the CI/CD code templates to run on merge.
  1. Select On merge as the trigger type.
  2. Click Deploy to publish the schedule.

​
Turbo CI

Runs the schedule when a pull request is opened, building only the changed models so you can validate changes before they merge. See Turbo CI for the full setup, including per-provider configuration and schema cleanup.

​
Incoming webhook

Coming soon. Trigger runs from external tools via a webhook URL.
Until this is available, use the Off trigger type to run a schedule from an external system through the Bolt API.

​
Off

No automatic trigger. The schedule only runs when you start it manually or call it through the Paradime API. Use this for on-demand schedules and for triggering Bolt from external systems such as Airflow, Dagster, or Prefect.
  1. Select Off as the trigger type.
  2. Run the schedule manually from the Bolt UI, or trigger it with the Bolt API.
Next, configure the commands your schedule runs.

Define this as code

Set the trigger in YAML with schedule, schedule_trigger, trigger_on_merge, or turbo_ci.

Related topics

External TriggersTrigger ZapierBolt Trigger IntegrationsTrigger Bolt externallySchedule types and triggers