Zeebe JobWorker binding spec

    To setup Zeebe JobWorker binding create a component of type . See on how to create and apply a binding configuration.

    See this for Zeebe JobWorker documentation.

    Variables

    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 the 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 productId, productName and productKey then the worker will be called with the following JSON body:

    1. {
    2. "productId": "some-product-id",
    3. "productName": "some-product-name",
    4. "productKey": "some-product-key"

    Headers

    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.

    MetadataData typeDescription
    X-Zeebe-Job-Keyint64The key, a unique identifier for the job
    X-Zeebe-Job-TypestringThe type of the job (should match what was requested)
    X-Zeebe-Process-Instance-Keyint64The job’s process instance key
    X-Zeebe-Bpmn-Process-IdstringThe bpmn process ID of the job process definition
    X-Zeebe-Process-Definition-Versionint32The version of the job process definition
    X-Zeebe-Process-Definition-Keyint64The key of the job process definition
    X-Zeebe-Element-IdstringThe associated task element ID
    X-Zeebe-Element-Instance-Keyint64The unique key identifying the associated task, unique within the scope of the process instance
    X-Zeebe-WorkerstringThe name of the worker which activated this job
    X-Zeebe-Retriesint32The amount of retries left to this job (should always be positive)
    X-Zeebe-Deadlineint64When the job can be activated again, sent as a UNIX epoch timestamp