Camunda Job Workers

Implement job workers for Camunda 8.8+ in Java, Camunda Spring Boot, or TypeScript. A job worker is the handler that the Zeebe engine hands an activated job to — it runs business logic, then signals success, failure, or a BPMN error back to the engine.

Prerequisites

• Camunda 8.8+ cluster reachable from the worker process (local c8run, SaaS, or Self-Managed — see camunda-c8ctl)
• A BPMN process with at least one element that has <zeebe:taskDefinition type="..."/> matching the worker's job type (see camunda-bpmn)
• Toolchain for the chosen SDK — OpenJDK 17+ and Maven/Gradle for Java and Spring; Node.js 18+ for TypeScript. SDK-specific version constraints (e.g. Spring Boot 4 vs 3, browser support) are in each SDK's reference. See camunda-development for installing these locally.

Cross-References

• camunda-development: Use first to decide whether a worker is the right shape at all (vs. an OOTB connector, a JSON-only protocol-connector template, or a custom Java connector via the SDK)
• camunda-connectors-development: Use when the integration is closer to a reusable Java connector than to application-bound worker code, or when the integration needs inbound triggers (workers are outbound-only)
• camunda-bpmn: Use for the service-task / receive-task element and its zeebe:taskDefinition, plus the boundary events that catch the worker's BPMN errors
• camunda-feel: Use for FEEL in zeebe:taskHeaders and for the gateway conditions that consume the worker's output variables
• camunda-process-mgmt: Use for deploying the process, starting instances against the running worker, and inspecting jobs / incidents from the cluster side
• camunda-process-test: Use for end-to-end tests that drive worker handlers through an embedded Zeebe engine