What you can do
Catalog & Lineage
Lightdash assets appear in Paradime’s catalog and lineage, so you can trace dbt™ models through to the metrics built on them.
Orchestration
Develop metrics with the Lightdash CLI in the Code IDE and deploy dbt™ project changes to Lightdash from a Bolt schedule.
Prerequisites
Development setup
Authenticate the Lightdash CLI in the terminal
The Paradime terminal runs in the cloud, so the Lightdash CLI’s default browser-based login does not work there: the CLI cannot open a browser tab, and the OAuth callback cannot reach the terminal. Paradime does not support OAuth login for the Lightdash CLI. Use a personal access token instead.1
Create a personal access token in Lightdash
In Lightdash, go to Settings > Personal Access Tokens and click Generate new token. Copy the token; Lightdash shows it only once.

2
3
Pick the active project
After login the CLI asks which project to work in. Change it later with:
Alternative: authenticate with environment variables
Alternative: authenticate with environment variables
Instead of logging in, set these as Code IDE environment variables. They apply to every Lightdash command in your terminal and take precedence over a saved login.
LIGHTDASH_API_KEY: your personal access tokenLIGHTDASH_URL: your instance URL, for examplehttps://eu1.lightdash.cloudLIGHTDASH_PROJECT: the project UUID (optional, otherwise uselightdash config set-project)
lightdash login succeeds but later commands fail to authenticate, check for a stale key with env | grep LIGHTDASH.Use the Lightdash CLI
The Lightdash CLI in Paradime enables you to:- Autogenerate Lightdash-ready YAML files
- Preview metrics before deployment
- Deploy changes to your Lightdash instance
Orchestration
Enable automatic deployment of your dbt™ project changes to Lightdash using Paradime Bolt schedules. For the full set of Bolt commands, see Lightdash commands.Step 1: Configure Lightdash credentials
- From any page in Paradime, click Settings
- Navigate to Workspaces > Environment Variables
- In the Bolt Schedules section, click Add New
- Configure each required variable:
LIGHTDASH_API_KEY: Personal access tokenLIGHTDASH_PROJECT: Project UUIDLIGHTDASH_URL: Instance URL
Finding your Lightdash credentials
Finding your Lightdash credentials
LIGHTDASH_API_KEY
Settings > Personal Access Tokens. This is the token you’ll put in for LIGHTDASH_API_KEY.
LIGHTDASH_PROJECT
https://eu1.lightdash.cloud/projects/3538ab33-dc90-45f0-aabb-e50bba3a5f69/tables, then 3538ab33-dc90-45f0-aabb-e50bba3a5f69 is your LIGHTDASH_PROJECT.LIGHTDASH_URL
https://eu1.lightdash.cloud or https://app.lightdash.cloud (check the URL to your Lightdash project)Step 2: Configure deployment schedule
- Create or edit a Bolt schedule
- Add the
lightdash deploycommand - This will:
- Execute after your dbt™ commands complete
- Deploy changes to your Lightdash project
- Keep metrics in sync with your dbt™ project
You can configure this as part of a CD schedule to deploy changes automatically after PR merges.