diff --git a/airflow/providers/databricks/example_dags/example_run_now.py b/airflow/providers/databricks/example_dags/example_run_now.py
new file mode 100644
index 0000000000000..e5f9e3bef606a
--- /dev/null
+++ b/airflow/providers/databricks/example_dags/example_run_now.py
@@ -0,0 +1,74 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+"""
+This is an example DAG which uses the DatabricksRunNowOperator.
+
+Use this operator if you have already created a job in Databricks
+and wish to trigger a run of that job.
+
+See https://docs.databricks.com/dev-tools/api/2.0/jobs.html#create or
+https://docs.databricks.com/jobs.html#create-a-job for details on how to
+create a job.
+
+In this example, we create two tasks which execute sequentially.
+The first task is to run a notebook with additional notebook parameters,
+and the second task is to run a JAR with additional parameters.
+
+Because we have set a downstream dependency on the notebook task,
+the spark jar task will NOT run until the notebook task completes
+successfully.
+
+The definition of a successful run is if the run has a result_state of "SUCCESS".
+For more information about the state of a run refer to
+https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobsrunstate
+"""
+
+from datetime import datetime
+
+from airflow import DAG
+from airflow.providers.databricks.operators.databricks import DatabricksRunNowOperator
+
+with DAG(
+    dag_id='example_databricks_run_now_operator',
+    schedule_interval='@daily',
+    start_date=datetime(2021, 1, 1),
+    tags=['example'],
+    catchup=False,
+) as dag:
+    # [START howto_operator_databricks_json]
+    notebook_task_json = {
+        'job_id': 1,
+        'notebook_params': {
+            'name': 'john doe',
+            'age': '35',
+        },
+    }
+    # Example of using the JSON parameter to initialize the operator.
+    notebook_task = DatabricksRunNowOperator(task_id='notebook_task', json=notebook_task_json)
+    # [END howto_operator_databricks_json]
+
+    # [START howto_operator_databricks_named]
+    # Example of using the named parameters of DatabricksRunNowOperator
+    # to initialize the operator.
+    jar_task = DatabricksRunNowOperator(
+        task_id='spark_jar_task',
+        job_id=2,
+        jar_params=["john doe", "35"],
+    )
+    # [END howto_operator_databricks_named]
+    notebook_task >> jar_task
diff --git a/airflow/providers/databricks/example_dags/example_databricks.py b/airflow/providers/databricks/example_dags/example_submit_run.py
similarity index 93%
rename from airflow/providers/databricks/example_dags/example_databricks.py
rename to airflow/providers/databricks/example_dags/example_submit_run.py
index 2f1310c786c6f..b6fb30b800903 100644
--- a/airflow/providers/databricks/example_dags/example_databricks.py
+++ b/airflow/providers/databricks/example_dags/example_submit_run.py
@@ -17,6 +17,9 @@
 # under the License.
 """
 This is an example DAG which uses the DatabricksSubmitRunOperator.
+
+Submit a one-time runs without having to create a Databricks job first.
+
 In this example, we create two tasks which execute sequentially.
 The first task is to run a notebook at the workspace path "/test"
 and the second task is to run a JAR uploaded to DBFS. Both,
@@ -28,7 +31,7 @@
 
 The definition of a successful run is if the run has a result_state of "SUCCESS".
 For more information about the state of a run refer to
-https://docs.databricks.com/api/latest/jobs.html#runstate
+https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobsrunstate
 """
 
 from datetime import datetime
@@ -37,7 +40,7 @@
 from airflow.providers.databricks.operators.databricks import DatabricksSubmitRunOperator
 
 with DAG(
-    dag_id='example_databricks_operator',
+    dag_id='example_databricks_submit_run_operator',
     schedule_interval='@daily',
     start_date=datetime(2021, 1, 1),
     tags=['example'],
@@ -50,13 +53,13 @@
         'num_workers': 8,
     }
 
+    # [START howto_operator_databricks_json]
     notebook_task_params = {
         'new_cluster': new_cluster,
         'notebook_task': {
             'notebook_path': '/Users/airflow@example.com/PrepareData',
         },
     }
-    # [START howto_operator_databricks_json]
     # Example of using the JSON parameter to initialize the operator.
     notebook_task = DatabricksSubmitRunOperator(task_id='notebook_task', json=notebook_task_params)
     # [END howto_operator_databricks_json]
diff --git a/airflow/providers/databricks/operators/databricks.py b/airflow/providers/databricks/operators/databricks.py
index 8956b43be1de7..a6196a844484f 100644
--- a/airflow/providers/databricks/operators/databricks.py
+++ b/airflow/providers/databricks/operators/databricks.py
@@ -96,9 +96,13 @@ class DatabricksSubmitRunOperator(BaseOperator):
     """
     Submits a Spark job run to Databricks using the
     `api/2.0/jobs/runs/submit
-    <https://docs.databricks.com/api/latest/jobs.html#runs-submit>`_
+    <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runs-submit>`_
     API endpoint.
 
+    .. seealso::
+        For more information on how to use this operator, take a look at the guide:
+        :ref:`howto/operator:DatabricksSubmitRunOperator`
+
     There are two ways to instantiate this operator.
 
     In the first way, you can take the JSON payload that you typically use
@@ -143,6 +147,7 @@ class DatabricksSubmitRunOperator(BaseOperator):
         - ``notebook_task``
         - ``spark_python_task``
         - ``spark_submit_task``
+        - ``pipeline_task``
         - ``new_cluster``
         - ``existing_cluster_id``
         - ``libraries``
@@ -162,47 +167,62 @@ class DatabricksSubmitRunOperator(BaseOperator):
 
         .. seealso::
             For more information about templating see :ref:`concepts:jinja-templating`.
-            https://docs.databricks.com/api/latest/jobs.html#runs-submit
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runs-submit
+
     :type json: dict
     :param spark_jar_task: The main class and parameters for the JAR task. Note that
         the actual JAR is specified in the ``libraries``.
         *EITHER* ``spark_jar_task`` *OR* ``notebook_task`` *OR* ``spark_python_task``
-        *OR* ``spark_submit_task`` should be specified.
+        *OR* ``spark_submit_task`` *OR* ``pipeline_task`` should be specified.
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#jobssparkjartask
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobssparkjartask
+
     :type spark_jar_task: dict
     :param notebook_task: The notebook path and parameters for the notebook task.
         *EITHER* ``spark_jar_task`` *OR* ``notebook_task`` *OR* ``spark_python_task``
-        *OR* ``spark_submit_task`` should be specified.
+        *OR* ``spark_submit_task`` *OR* ``pipeline_task`` should be specified.
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#jobsnotebooktask
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobsnotebooktask
+
     :type notebook_task: dict
     :param spark_python_task: The python file path and parameters to run the python file with.
         *EITHER* ``spark_jar_task`` *OR* ``notebook_task`` *OR* ``spark_python_task``
-        *OR* ``spark_submit_task`` should be specified.
+        *OR* ``spark_submit_task`` *OR* ``pipeline_task`` should be specified.
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#jobssparkpythontask
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobssparkpythontask
+
     :type spark_python_task: dict
     :param spark_submit_task: Parameters needed to run a spark-submit command.
         *EITHER* ``spark_jar_task`` *OR* ``notebook_task`` *OR* ``spark_python_task``
-        *OR* ``spark_submit_task`` should be specified.
+        *OR* ``spark_submit_task`` *OR* ``pipeline_task`` should be specified.
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#jobssparksubmittask
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobssparksubmittask
+
     :type spark_submit_task: dict
+    :param pipeline_task: Pipeline_id (full name of the Delta Live Tables pipeline) of the pipeline to run.
+        *EITHER* ``spark_jar_task`` *OR* ``notebook_task`` *OR* ``spark_python_task``
+        *OR* ``spark_submit_task`` *OR* ``pipeline_task`` should be specified.
+        This field will be templated.
+
+        .. seealso::
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobspipelinetask
+
+    :type pipeline_task: dict
     :param new_cluster: Specs for a new cluster on which this task will be run.
         *EITHER* ``new_cluster`` *OR* ``existing_cluster_id`` should be specified.
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#jobsclusterspecnewcluster
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#jobsclusterspecnewcluster
+
     :type new_cluster: dict
     :param existing_cluster_id: ID for existing cluster on which to run this task.
         *EITHER* ``new_cluster`` *OR* ``existing_cluster_id`` should be specified.
@@ -213,6 +233,7 @@ class DatabricksSubmitRunOperator(BaseOperator):
 
         .. seealso::
             https://docs.databricks.com/api/latest/libraries.html#managedlibrarieslibrary
+
     :type libraries: list of dicts
     :param run_name: The run name used for this task.
         By default this will be set to the Airflow ``task_id``. This ``task_id`` is a
@@ -255,6 +276,7 @@ def __init__(
         notebook_task: Optional[Dict[str, str]] = None,
         spark_python_task: Optional[Dict[str, Union[str, List[str]]]] = None,
         spark_submit_task: Optional[Dict[str, List[str]]] = None,
+        pipeline_task: Optional[Dict[str, str]] = None,
         new_cluster: Optional[Dict[str, object]] = None,
         existing_cluster_id: Optional[str] = None,
         libraries: Optional[List[Dict[str, str]]] = None,
@@ -282,6 +304,8 @@ def __init__(
             self.json['spark_python_task'] = spark_python_task
         if spark_submit_task is not None:
             self.json['spark_submit_task'] = spark_submit_task
+        if pipeline_task is not None:
+            self.json['pipeline_task'] = pipeline_task
         if new_cluster is not None:
             self.json['new_cluster'] = new_cluster
         if existing_cluster_id is not None:
@@ -322,9 +346,13 @@ class DatabricksRunNowOperator(BaseOperator):
     """
     Runs an existing Spark job run to Databricks using the
     `api/2.0/jobs/run-now
-    <https://docs.databricks.com/api/latest/jobs.html#run-now>`_
+    <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#run-now>`_
     API endpoint.
 
+    .. seealso::
+        For more information on how to use this operator, take a look at the guide:
+        :ref:`howto/operator:DatabricksRunNowOperator`
+
     There are two ways to instantiate this operator.
 
     In the first way, you can take the JSON payload that you typically use
@@ -372,6 +400,7 @@ class DatabricksRunNowOperator(BaseOperator):
     Currently the named parameters that ``DatabricksRunNowOperator`` supports are
         - ``job_id``
         - ``json``
+        - ``jar_params``
         - ``notebook_params``
         - ``python_params``
         - ``spark_submit_params``
@@ -381,7 +410,8 @@ class DatabricksRunNowOperator(BaseOperator):
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#run-now
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#run-now
+
     :type job_id: str
     :param json: A JSON object containing API parameters which will be passed
         directly to the ``api/2.0/jobs/run-now`` endpoint. The other named parameters
@@ -392,8 +422,22 @@ class DatabricksRunNowOperator(BaseOperator):
 
         .. seealso::
             For more information about templating see :ref:`concepts:jinja-templating`.
-            https://docs.databricks.com/api/latest/jobs.html#run-now
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#run-now
+
     :type json: dict
+    :param jar_params: A list of parameters for jobs with JAR tasks,
+        e.g. "jar_params": ["john doe", "35"].
+        The parameters will be used to invoke the main function of the main class specified
+        in the Spark JAR task. If not specified upon run-now, it will default to an empty
+        list. jar_params cannot be specified in conjunction with notebook_params.
+        The JSON representation of this field (i.e. {"jar_params":["john doe","35"]})
+        cannot exceed 10,000 bytes.
+        This field will be templated.
+
+        .. seealso::
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runparameters
+
+    :type jar_params: list[str]
     :param notebook_params: A dict from keys to values for jobs with notebook task,
         e.g. "notebook_params": {"name": "john doe", "age":  "35"}.
         The map is passed to the notebook and will be accessible through the
@@ -407,6 +451,7 @@ class DatabricksRunNowOperator(BaseOperator):
 
         .. seealso::
             https://docs.databricks.com/user-guide/notebooks/widgets.html
+
     :type notebook_params: dict
     :param python_params: A list of parameters for jobs with python tasks,
         e.g. "python_params": ["john doe", "35"].
@@ -418,7 +463,8 @@ class DatabricksRunNowOperator(BaseOperator):
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#run-now
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runparameters
+
     :type python_params: list[str]
     :param spark_submit_params: A list of parameters for jobs with spark submit task,
         e.g. "spark_submit_params": ["--class", "org.apache.spark.examples.SparkPi"].
@@ -429,7 +475,8 @@ class DatabricksRunNowOperator(BaseOperator):
         This field will be templated.
 
         .. seealso::
-            https://docs.databricks.com/api/latest/jobs.html#run-now
+            https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runparameters
+
     :type spark_submit_params: list[str]
     :param timeout_seconds: The timeout for this run. By default a value of 0 is used
         which means to have no timeout.
@@ -461,6 +508,7 @@ def __init__(
         *,
         job_id: Optional[str] = None,
         json: Optional[Any] = None,
+        jar_params: Optional[List[str]] = None,
         notebook_params: Optional[Dict[str, str]] = None,
         python_params: Optional[List[str]] = None,
         spark_submit_params: Optional[List[str]] = None,
@@ -481,6 +529,8 @@ def __init__(
 
         if job_id is not None:
             self.json['job_id'] = job_id
+        if jar_params is not None:
+            self.json['jar_params'] = jar_params
         if notebook_params is not None:
             self.json['notebook_params'] = notebook_params
         if python_params is not None:
diff --git a/docs/apache-airflow-providers-databricks/operators.rst b/docs/apache-airflow-providers-databricks/operators.rst
index eb5170f839d84..b98839a1baf5e 100644
--- a/docs/apache-airflow-providers-databricks/operators.rst
+++ b/docs/apache-airflow-providers-databricks/operators.rst
@@ -16,26 +16,25 @@
     under the License.
 
 
+Databricks Operators
+====================
 
 .. _howto/operator:DatabricksSubmitRunOperator:
 
 DatabricksSubmitRunOperator
-===========================
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Use the :class:`~airflow.providers.databricks.operators.DatabricksSubmitRunOperator` to submit
-an existing Spark job run to Databricks api/2.0/jobs/runs/submit <https://docs.databricks.com/api/latest/jobs.html#runs-submit> API endpoint.
-
-
-Using the Operator
-^^^^^^^^^^^^^^^^^^
+Use the :class:`~airflow.providers.databricks.operators.databricks.DatabricksSubmitRunOperator` to submit
+an existing Spark job run to Databricks `runs/submit <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runs-submit>`__ endpoint.
 
 There are two ways to instantiate this operator. In the first way, you can take the JSON payload that you typically use
-to call the ``api/2.0/jobs/runs/submit`` endpoint and pass it directly to our ``DatabricksSubmitRunOperator`` through the ``json`` parameter.
+to call the `runs/submit <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runs-submit>`__ endpoint and pass it directly
+to the :class:`~airflow.providers.databricks.operators.databricks.DatabricksSubmitRunOperator` through the ``json`` parameter.
 
-Another way to accomplish the same thing is to use the named parameters of the ``DatabricksSubmitRunOperator`` directly. Note that there is exactly
-one named parameter for each top level parameter in the ``runs/submit`` endpoint.
+Another way to accomplish the same thing is to use the named parameters of the :class:`~airflow.providers.databricks.operators.databricks.DatabricksSubmitRunOperator`
+directly. Note that there is exactly one named parameter for each top level parameter in the `runs/submit <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#runs-submit>`__ endpoint.
 
-.. list-table:: Databricks Airflow Connection Metadata
+.. list-table::  DatabricksSubmitRunOperator named parameters
    :widths: 25 25
    :header-rows: 1
 
@@ -49,6 +48,8 @@ one named parameter for each top level parameter in the ``runs/submit`` endpoint
      - python file path and parameters to run the python file with
    * - spark_submit_task: dict
      - parameters needed to run a spark-submit command
+   * - pipeline_task: dict
+     - pipeline_id (full name of the Delta Live Tables pipeline) to run the pipeline
    * - new_cluster: dict
      - specs for a new cluster on which this task will be run
    * - existing_cluster_id: string
@@ -70,16 +71,68 @@ one named parameter for each top level parameter in the ``runs/submit`` endpoint
    * - do_xcom_push: boolean
      - whether we should push run_id and run_page_url to xcom
 
-An example usage of the DatabricksSubmitRunOperator is as follows:
+Example Usage
+"""""""""""""
+
+An example usage of the :class:`~airflow.providers.databricks.operators.databricks.DatabricksSubmitRunOperator` is as follows:
+
+.. exampleinclude:: /../../airflow/providers/databricks/example_dags/example_submit_run.py
+    :language: python
+    :start-after: [START howto_operator_databricks_json]
+    :end-before: [END howto_operator_databricks_json]
+
+You can also use named parameters to initialize the :class:`~airflow.providers.databricks.operators.databricks.DatabricksSubmitRunOperator` and run the job.
+
+.. exampleinclude:: /../../airflow/providers/databricks/example_dags/example_submit_run.py
+    :language: python
+    :start-after: [START howto_operator_databricks_named]
+    :end-before: [END howto_operator_databricks_named]
 
-.. exampleinclude:: /../../airflow/providers/databricks/example_dags/example_databricks.py
+.. _howto/operator:DatabricksRunNowOperator:
+
+DatabricksRunNowOperator
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+Use the :class:`~airflow.providers.databricks.operators.databricks.DatabricksRunNowOperator` to submit
+an existing Spark job run to Databricks `jobs/run-now <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#run-now>`__  endpoint.
+
+There are two ways to instantiate this operator. In the first way, you can take the JSON payload that you typically use
+to call the `jobs/run-now <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#run-now>`__ endpoint and pass it directly
+to the :class:`~airflow.providers.databricks.operators.databricks.DatabricksRunNowOperator` through the ``json`` parameter.
+
+Another way to accomplish the same thing is to use the named parameters of the :class:`~airflow.providers.databricks.operators.databricks.DatabricksRunNowOperator`
+directly. Note that there is exactly one named parameter for each top level parameter in the `jobs/run-now <https://docs.databricks.com/dev-tools/api/2.0/jobs.html#run-now>`__ endpoint.
+
+.. list-table:: DatabricksRunNowOperator named parameters
+   :widths: 25 25
+   :header-rows: 1
+
+   * - Parameter
+     - Input
+   * - job_id: str
+     - the job_id of the existing Databricks job
+   * - jar_params: list[str]
+     - additional list of parameters for jobs with JAR tasks
+   * - notebook_params: dict
+     - a dict from keys to values for jobs with notebook task
+   * - python_params: list[str]
+     - additional list of parameters for jobs with python tasks
+   * - spark_submit_params: list[str]
+     - a list of parameters for jobs with spark submit task
+
+Example Usage
+"""""""""""""
+
+An example usage of the :class:`~airflow.providers.databricks.operators.databricks.DatabricksRunNowOperator` is as follows:
+
+.. exampleinclude:: /../../airflow/providers/databricks/example_dags/example_run_now.py
     :language: python
     :start-after: [START howto_operator_databricks_json]
     :end-before: [END howto_operator_databricks_json]
 
-You can also use named parameters to initialize the operator and run the job.
+You can also use named parameters to initialize the :class:`~airflow.providers.databricks.operators.databricks.DatabricksRunNowOperator` and run the job.
 
-.. exampleinclude:: /../../airflow/providers/databricks/example_dags/example_databricks.py
+.. exampleinclude:: /../../airflow/providers/databricks/example_dags/example_run_now.py
     :language: python
     :start-after: [START howto_operator_databricks_named]
     :end-before: [END howto_operator_databricks_named]
