The documentation you are viewing is for Dapr v1.9 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Zeebe JobWorker binding spec
To setup Zeebe JobWorker binding create a component of type
bindings.zeebe.jobworker. See this guide on how to create and apply a binding configuration.
See this for Zeebe JobWorker documentation.
- name: gatewayAddr
- name: gatewayKeepAlive
- name: usePlainTextConnection
- name: caCertificatePath
- name: workerName
- name: workerTimeout
- name: requestTimeout
- name: jobType
- name: maxJobsActive
- name: concurrency
- name: pollInterval
- name: pollThreshold
- name: fetchVariables
value: productId, productName, productKey
- name: autocomplete
Spec metadata fields
|Zeebe gateway address
|Sets how often keep alive messages should be sent to the gateway. Defaults to 45 seconds
|Whether to use a plain text connection or not
|The path to the CA cert
|The name of the worker activating the jobs, mostly used for logging purposes
|A job returned after this call will not be activated by another call until the timeout has been reached; defaults to 5 minutes
|The request will be completed when at least one job is activated or after the requestTimeout. If the requestTimeout = 0, a default timeout is used. If the requestTimeout < 0, long polling is disabled and the request is completed immediately, even when no job is activated. Defaults to 10 seconds
|the job type, as defined in the BPMN process (e.g.
<zeebe:taskDefinition type="fetch-products" />)
|Set the maximum number of jobs which will be activated for this worker at the same time. Defaults to 32
|The maximum number of concurrent spawned goroutines to complete jobs. Defaults to 4
|Set the maximal interval between polling for new jobs. Defaults to 100 milliseconds
|Set the threshold of buffered activated jobs before polling for new jobs, i.e. threshold * maxJobsActive. Defaults to 0.3
|A list of variables to fetch as the job variables; if empty, all visible variables at the time of activation for the scope of the job will be returned
productId, productName, productKey
|Indicates if a job should be autocompleted or not. If not set, all jobs will be auto-completed by default. Disable it if the worker should manually complete or fail the job with either a business error or an incident
This component supports input binding interfaces.
The Zeebe process engine handles the process state as also process variables which can be passed
on process instantiation or which can be updated or created during process execution. These variables
can be passed to a registered job worker by defining the variable names as comma-separated list in
fetchVariables metadata field. The process engine will then pass these variables with its current
values to the job worker implementation.
If the binding will register three variables
productKey then the worker will
be called with the following JSON body:
Note: if the
fetchVariables metadata field will not be passed, all process variables will be passed to the worker.
The Zeebe process engine has the ability to pass custom task headers to a job worker. These headers can be defined for every service task. Task headers will be passed by the binding as metadata (HTTP headers) to the job worker.
The binding will also pass the following job related variables as metadata. The values will be passed as string. The table contains also the original data type so that it can be converted back to the equivalent data type in the used programming language for the worker.
|The key, a unique identifier for the job
|The type of the job (should match what was requested)
|The job’s process instance key
|The bpmn process ID of the job process definition
|The version of the job process definition
|The key of the job process definition
|The associated task element ID
|The unique key identifying the associated task, unique within the scope of the process instance
|The name of the worker which activated this job
|The amount of retries left to this job (should always be positive)
|When the job can be activated again, sent as a UNIX epoch timestamp
- Basic schema for a Dapr component
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.