Databricks Jobs
Develop and deploy Lakeflow Jobs on Databricks via DABs, Python SDK, or the CLI. Use when creating data engineering jobs with notebooks, Python wheels, SQL, dbt, or pipelines. Invoke BEFORE starting implementation.
- Skill ID
- databricks/databricks-agent-skills/databricks-jobs
- Publisher
- databricks
- Repository
- databricks-agent-skills
- Installs
- 0
- Files
- 8
- Requires
- Requires databricks CLI (>= v1.0.0)
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
databricks/databricks-agent-skills/databricks-jobsInstalls these files- SKILL.md
- agents/openai.yaml
- assets/databricks.png
- assets/databricks.svg
- references/examples.md
- references/notifications-monitoring.md
- references/task-types.md
- references/triggers-schedules.md
What this skill tells the agent
Lakeflow Jobs Development
FIRST: Use the parent databricks-core skill for CLI basics, authentication, profile selection, and data exploration commands.
Lakeflow Jobs orchestrate data workflows with multi-task DAGs, flexible triggers, and comprehensive monitoring. Jobs support diverse task types and can be managed via Asset Bundles (DABs), Python SDK, or CLI.
Reference Files
| Use Case | Reference File |
|---|---|
| Configure task types (notebook, Python, SQL, dbt, pipeline, JAR, run_job, for_each) | references/task-types.md |
| Set up triggers and schedules (cron, periodic, file arrival, table update, continuous) | references/triggers-schedules.md |
| Configure notifications, health rules, retries, timeouts, queues | references/notifications-monitoring.md |
| Complete worked examples (ETL, warehouse refresh, event-driven, ML training, multi-env, streaming, cross-job) | references/examples.md |
Scaffolding a New Job Project
Use databricks bundle init with a config file to scaffold non-interactively. This creates a project in the <project_name>/ directory:
databricks bundle init default-python --config-file <(echo '{"project_name": "my_job", "include_job": "yes", "include_pipeline": "no", "include_python": "yes", "serverless": "yes"}') --profile <PROFILE> < /dev/nullproject_name: letters, numbers, underscores only
After scaffolding, create CLAUDE.md and AGENTS.md in the project directory. These files are essential to provide agents with guidance on how to work with the project. Use this content:
# Declarative Automation Bundles Project
This project uses Declarative Automation Bundles (formerly Databricks Asset Bundles) for deployment.
## Prerequisites
Install the Databricks CLI (>= v0.288.0) if not already installed:
- macOS: `brew tap databricks/tap && brew install databricks`
- Linux: `curl -fsSL https://raw.githubusercontent.com/databricks/setup-cli/main/install.sh | sh`
- Windows: `winget install Databricks.DatabricksCLI`
Verify: `databricks -v`
## For AI Agents
Read the `databricks-core` skill for CLI basics, authentication, and deployment workflow.
Read the `databricks-jobs` skill for job-specific guidance.
If skills are not available, install them: `databricks aitools install`Project Structure
my-job-project/
├── databricks.yml # Bundle configuration
├── resources/
│ └── my_job.job.yml # Job definition
├── src/
│ ├── my_notebook.ipynb # Notebook tasks
│ └── my_module/ # Python wheel package
│ ├── __init__.py
│ └── main.py
├── tests/
│ └── test_main.py
└── pyproject.toml # Python project config (if using wheels)Quick Start
Asset Bundles (DABs) — recommended
# resources/jobs.yml
resources:
jobs:
my_etl_job:
name: "[${bundle.target}] My ETL Job"
tasks:
- task_key: extract
notebook_task:
notebook_path: ../src/notebooks/extract.pyPython SDK
from databricks.sdk import WorkspaceClient
from databricks.sdk.service.jobs import Task, NotebookTask, Source
w = WorkspaceClient()
job = w.jobs.create(
name="my-etl-job",
tasks=[
Task(
task_key="extract",
notebook_task=NotebookTask(
notebook_path="/Workspace/Shared/etl/extract",
source=Source.WORKSPACE,
),
),
],
)
print(f"Created job: {job.job_id}")CLI
databricks jobs create --json '{
"name": "my-etl-job",
"tasks": [{
"task_key": "extract",
"notebook_task": {
"notebook_path": "/Workspace/Shared/etl/extract",
"source": "WORKSPACE"
}
}]
}'Core Concepts
Multi-Task Workflows
Jobs support DAG-based task dependencies:
tasks:
- task_key: extract
notebook_task:
notebook_path: ../src/extract.py
- task_key: transform
depends_on:
- task_key: extract
notebook_task:
notebook_path: ../src/transform.py
- task_key: load
depends_on:
- task_key: transform
run_if: ALL_SUCCESS # Only run if all dependencies succeed
notebook_task:
notebook_path: ../src/load.pyrun_if conditions:
ALL_SUCCESS(default) — run when all dependencies succeedALL_DONE— run when all dependencies complete (success or failure)AT_LEAST_ONE_SUCCESS— run when at least one dependency succeedsNONE_FAILED— run when no dependencies failedALL_FAILED— run when all dependencies failedAT_LEAST_ONE_FAILED— run when at least one dependency failed
Task Types Summary
| Task Type | Use Case | Reference |
|---|---|---|
notebook_task | Run notebooks | references/task-types.md#notebook-task |
spark_python_task | Run Python scripts | references/task-types.md#spark-python-task |
python_wheel_task | Run Python wheels | references/task-types.md#python-wheel-task |
sql_task | Run SQL queries/files/dashboards/alerts | references/task-types.md#sql-task |
dbt_task | Run dbt projects | references/task-types.md#dbt-task |
pipeline_task | Trigger SDP (formerly DLT) pipelines | references/task-types.md#pipeline-task |
spark_jar_task | Run Spark JARs | references/task-types.md#spark-jar-task |
run_job_task | Trigger other jobs | references/task-types.md#run-job-task |
for_each_task | Loop over inputs | references/task-types.md#for-each-task |
Trigger Types Summary
| Trigger Type | Use Case | Reference |
|---|---|---|
schedule | Cron-based scheduling | references/triggers-schedules.md#cron-schedule |
trigger.periodic | Interval-based | references/triggers-schedules.md#periodic-trigger |
trigger.file_arrival | File arrival events | references/triggers-schedules.md#file-arrival-trigger |
trigger.table_update | Unity Catalog table change events | references/triggers-schedules.md#table-update-trigger |
continuous | Always-running jobs | references/triggers-schedules.md#continuous-jobs |
Compute Configuration
Job Clusters (recommended)
Define reusable cluster configurations shared across tasks:
job_clusters:
- job_cluster_key: shared_cluster
new_cluster:
spark_version: "15.4.x-scala2.12"
node_type_id: "i3.xlarge"
num_workers: 2
spark_conf:
spark.speculation: "true"
tasks:
- task_key: my_task
job_cluster_key: shared_cluster
notebook_task:
notebook_path: ../src/notebook.pyAutoscaling Clusters
new_cluster:
spark_version: "15.4.x-scala2.12"
node_type_id: "i3.xlarge"
autoscale:
min_workers: 2
max_workers: 8Existing Cluster
tasks:
- task_key: my_task
existing_cluster_id: "0123-456789-abcdef12"
notebook_task:
notebook_path: ../src/notebook.pyServerless Compute
For notebook and Python tasks, omit cluster configuration to use serverless:
tasks:
- task_key: serverless_task
notebook_task:
notebook_path: ../src/notebook.py
# No cluster config = serverlessJob Parameters
More from databricks
Use this skill in a project
Open any RiverX project, search the Skills panel for databricks/databricks-agent-skills/databricks-jobs, and install it in one click.
