> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Orchestrate your whole stack

> Run ingestion syncs, Python scripts, and dbt™ commands from a single Paradime Bolt schedule so your end-to-end data pipeline runs in the right order.

A Bolt schedule runs more than dbt™. In this guide you'll add a non-dbt command to a schedule so ingestion, custom scripts, and transformations all run in the right order from one place.

<Note>
  **Prerequisites**

  * A [Bolt schedule](/guides/paradime-101/running-dbt-in-production-with-bolt/creating-bolt-schedules) you can edit.
  * For an ingestion sync: your source connected to Paradime (for example, [Airbyte](/products/bolt/creating-schedules/command-settings/airbyte-connector-sync) or [Fivetran](/products/bolt/creating-schedules/command-settings/fivetran-connector-sync)) with its credentials set as [Bolt schedule environment variables](/products/settings/environment-variables/bolt-schedule-env-variables).
  * For a Python script: the script committed to your dbt™ project.

  Estimated time: 10 minutes.
</Note>

## Steps

<Steps>
  <Step title="Understand what a command is">
    A schedule is an ordered list of commands. Each command runs a step of your pipeline, and Bolt runs them top to bottom. Beyond dbt™ commands, you can add ingestion syncs (Airbyte, Fivetran, and more) and custom Python scripts to the same schedule.

    Order the commands to match your pipeline: sync source data first, then transform it with dbt™, then run any downstream checks or scripts.
  </Step>

  <Step title="Add a non-dbt command">
    Open the schedule and add a command. Pick the command type for the task you want to run, for example **Sync Airbyte Connection**, **Sync Fivetran Connector**, or **Run Python Script**.
  </Step>

  <Step title="Configure an ingestion sync (example)">
    For a **Sync Fivetran Connector** command, enter one or more **Connector IDs** (for example, `unsold_decoration`). Use **Add connector** to sync several in parallel; the schedule continues to the next command only once all syncs finish. Then click **Add command**.

    For a **Sync Airbyte Connection** command, enter one or more **Connection IDs** (for example, `conn_123`), choose the **Job type** (**Sync** to run the connection, or **Reset** to clear its data and re-sync), then click **Add command**.

    <Info>
      Set the connector or connection to **Manual** scheduling in Fivetran or Airbyte, so syncs run only when Paradime triggers them.
    </Info>
  </Step>

  <Step title="Or run a Python script (example)">
    For a **Run Python Script** command, enter one or more commands, one per line. If you manage dependencies with Poetry, keep `pyproject.toml` and `poetry.lock` at the root of your dbt™ project and make `poetry install` the first command:

    ```bash theme={"system"}
    poetry install
    poetry run python path/to/my/script.py
    ```

    Without Poetry, run the script directly:

    ```bash theme={"system"}
    python path/to/my/script.py
    ```

    <Info>
      Store secrets (API keys, credentials) as [Bolt schedule environment variables](/products/settings/environment-variables/bolt-schedule-env-variables) and read them with `os.environ` rather than hardcoding them.
    </Info>
  </Step>

  <Step title="Order commands and add your dbt™ run">
    Arrange the commands so each step has what it needs: run the ingestion sync first, then your dbt™ commands to transform the fresh data, then any downstream Python checks. Save the schedule.
  </Step>
</Steps>

<Check>
  Trigger the schedule and open its run. You'll know it worked when every command shows as completed in order, with the ingestion sync finishing before the dbt™ run starts. If a sync hangs, confirm the source is set to **Manual** scheduling and that its credentials are set as Bolt environment variables.
</Check>

## Next steps

<CardGroup cols={2}>
  <Card title="Trigger runs the right way" href="/guides/paradime-101/running-dbt-in-production-with-bolt/understanding-schedule-types-and-triggers" icon="workflow">
    Choose schedule types and triggers, including running a pipeline on another schedule's completion.
  </Card>

  <Card title="Set up Turbo CI" href="/guides/orchestrate-data-pipelines/set-up-turbo-ci" icon="git-branch">
    Run and test only changed models on every pull request.
  </Card>

  <Card title="Fivetran command reference" href="/products/bolt/creating-schedules/command-settings/fivetran-connector-sync" icon="refresh-cw">
    Every field for the Sync Fivetran Connector command.
  </Card>

  <Card title="Python script reference" href="/products/bolt/creating-schedules/command-settings/python-scripts" icon="code">
    Poetry setup, environment variables, and usage for Run Python Script.
  </Card>
</CardGroup>


## Related topics

- [Orchestrate data pipelines](/guides/ship-to-production/index.md)
- [Send failures to your incident tools](/guides/orchestrate-data-pipelines/send-failures-to-incident-tools.md)
- [New Bolt command integrations](/changelog/2026-07-22/bolt-command-integrations.md)
- [Connecting integrations](/integrations/connecting-integrations.md)
- [Search & Replace](/products/code-ide/explore/search-and-replace.md)