> ## 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.

# Push to DataHub

> Add a Push to DataHub command to a Paradime Bolt schedule to send dbt™ artifacts to DataHub for metadata ingestion and lineage using the CLI.

Push dbt™ artifacts (`manifest.json` and `catalog.json`) to DataHub from a Bolt schedule so your metadata catalog stays in sync with the latest models, lineage, columns, and descriptions after each run.

## Prerequisites

* DataHub connected as a [workspace integration](/integrations/datahub). The integration provides the required credentials as environment variables: `DATAHUB_GMS_URL`, `DATAHUB_GMS_TOKEN`, and `DATAHUB_TARGET_PLATFORM` (`DATAHUB_DOMAIN` is optional).
* Run `dbt docs generate` earlier in the schedule so `catalog.json` exists. DataHub's dbt source needs both `manifest.json` and `catalog.json`, and only `dbt docs generate` produces the catalog.

## Usage

Add the **Push to DataHub** command to your schedule, after the dbt™ commands that generate your artifacts. The modal accepts any command supported by the [Paradime DataHub CLI](/developers/paradime-cli/datahub-cli):

```bash theme={"system"}
paradime run datahub-artifacts-push --datahub-server=https://instance.acryl.io/gms --target-platform=snowflake
```

When the integration's environment variables are set, you can call `paradime run datahub-artifacts-push` with no flags.

## Learn more

See the [Paradime DataHub CLI](/developers/paradime-cli/datahub-cli) for the full command and flag reference.


## Related topics

- [Commands](/products/bolt/creating-schedules/command-settings/index.md)
- [DataHub](/integrations/datahub.md)
- [DataHub CLI](/developers/paradime-cli/datahub-cli.md)
- [Integrations](/integrations/index.md)
- [GitHub Branch Protection Guide: Preventing Direct Commits to Main](/guides/working-with-git/github-branch-protection-guide-preventing-direct-commits-to-main.md)