airflow-provider-paradime-dbt
This is the provider for Paradime to run and manage dbt™ jobs in production. The provider enables interaction with Paradime’s Bolt scheduler and management APIs.
Usage
Create a connection
Account API key (recommended)
An account API key (prdm_cmp_...) can access one or more workspaces. One Airflow connection is enough to trigger schedules in all of them.
- In Paradime, create an account API key and select the workspaces it can access. Copy the key, the API endpoint, and the workspace UID listed next to each workspace.
- In Airflow, create a connection of type Paradime with these fields:
| Field | Value |
|---|---|
| API Endpoint | The API endpoint shown with the key |
| API Secret | Your prdm_cmp_... key |
| Default Workspace UID | Optional. The workspace to use when a task does not set workspace_uid |
Leave API Key blank. The provider detects an account API key from its prdm_cmp_ prefix, same as paradime-python-sdk.
You can also create the connection from an environment variable:
export AIRFLOW_CONN_PARADIME_DEFAULT='{
"conn_type": "paradime",
"extra": {
"api_endpoint": "https://api.paradime.io/api/v1/<company_token>/graphql",
"api_secret": "prdm_cmp_...",
"workspace_uid": "<default_workspace_uid>"
}
}'
Every request with an account API key needs a workspace UID. Set it on the task with workspace_uid=, or set a default on the connection. The task value wins. If neither is set, the task fails with an error that says so.
Workspace API key (legacy)
Workspace API keys still work with no changes. A workspace key and secret are bound to one workspace, so you need one connection per workspace.
- Generate your API key, secret and endpoint from Paradime Workspace settings.
- Create a connection in Airflow and fill in API Endpoint, API Key and API Secret.
workspace_uid has no effect on a connection that uses a workspace API key.
Create a DAG
This DAG uses one account API key connection to trigger schedules in two workspaces, wait for them, and download their manifest.json:
from airflow.decorators import dag
from paradime_dbt_provider.operators.paradime import ParadimeBoltDbtScheduleRunArtifactOperator, ParadimeBoltDbtScheduleRunOperator
from paradime_dbt_provider.sensors.paradime import ParadimeBoltDbtScheduleRunSensor
PARADIME_CONN_ID = "your_paradime_conn_id" # Update this to your connection id
# Map each Bolt schedule to the workspace that owns it
SCHEDULES = {
"marketing": {"workspace_uid": "your_marketing_workspace_uid", "slug": "your-marketing-schedule-slug"},
"finance": {"workspace_uid": "your_finance_workspace_uid", "slug": "your-finance-schedule-slug"},
}
@dag(
default_args={"conn_id": PARADIME_CONN_ID},
)
def run_schedules_in_two_workspaces():
for name, schedule in SCHEDULES.items():
workspace_uid = schedule["workspace_uid"]
# Run the schedule in its workspace and return the run id as the xcom return value
task_run_schedule = ParadimeBoltDbtScheduleRunOperator(task_id=f"run_{name}", slug=schedule["slug"], workspace_uid=workspace_uid)
# Get the run id from the xcom return value
run_id = f"{{{{ task_instance.xcom_pull(task_ids='run_{name}') }}}}"
# Wait for the run to complete. Use the same workspace UID as the task that triggered it.
task_wait_for_schedule = ParadimeBoltDbtScheduleRunSensor(task_id=f"wait_for_{name}", run_id=run_id, workspace_uid=workspace_uid)
# Download the manifest.json file from the run and return the path as the xcom return value
task_download_manifest = ParadimeBoltDbtScheduleRunArtifactOperator(
task_id=f"download_{name}_manifest",
run_id=run_id,
artifact_path="target/manifest.json",
workspace_uid=workspace_uid,
)
task_run_schedule >> task_wait_for_schedule >> task_download_manifest
run_schedules_in_two_workspaces()
workspace_uid is a templated field on ParadimeBoltDbtScheduleRunOperator, ParadimeBoltDbtScheduleRunSensor and ParadimeBoltDbtScheduleRunArtifactOperator. ParadimeHook also takes a workspace_uid argument. The sensor and the artifact operator must use the same workspace as the task that triggered the run.
With a workspace API key, or an account API key with a default workspace UID on the connection, leave out workspace_uid. See bolt_dbt_schedule_run.py.
Refer to the example DAGs in this repository for more examples.
Advanced Configuration
HTTP / HTTPS Proxy
If you need to use a proxy to connect to Paradime's API, you can configure it in the connection on the Airflow UI. You can set the following parameters in the connection:
- Proxy: The URL for your proxy server (e.g.,
http://proxy.example.com:8080).
This setting is optional. If not provided, connections will be made directly without a proxy.
Metadata
Release files for airflow-provider-paradime-dbt 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| airflow_provider_paradime_dbt-1.4.0.tar.gz | 19.4 kB | With provenance | Details for airflow_provider_paradime_dbt-1.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| airflow_provider_paradime_dbt-1.4.0-py3-none-any.whl | Python 3 | none | any | Details for airflow_provider_paradime_dbt-1.4.0-py3-none-any.whl |
Total release size: 43.1 kB
Release files / airflow_provider_paradime_dbt-1.4.0.tar.gz
| Download URL | airflow_provider_paradime_dbt-1.4.0.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4798ee3c28e9ccb3719b889ee7f5f29a534dbe8129049f89f2e9c50469955e43
|
|
BLAKE2b-256 checksum How to use checksums |
5baa31589ef898b9dff2b5da46af8fd66ac986c1c45c396c47b8817ec6789051
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / airflow_provider_paradime_dbt-1.4.0-py3-none-any.whl
| Download URL | airflow_provider_paradime_dbt-1.4.0-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79941577cfbdf9985f5db5e99d64c13e56e7474e8d2488e0587b66b64ff3bba9
|
|
BLAKE2b-256 checksum How to use checksums |
d46d6cbe1852e574b7c1f0956994ef39d65096a3a8f9b42db423473bc874fef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for airflow-provider-paradime-dbt 1.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for airflow_provider_paradime_dbt-1.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.