Camunda Connectors Development

Build a custom Camunda 8 connector when the OOTB catalog doesn't cover the integration. Two distinct paths share the same element-template surface but differ in whether you write Java.

Prerequisites

• Camunda 8.8+ cluster reachable for testing (local c8run, SaaS, or Self-Managed — see camunda-c8ctl)
• Path A: none beyond the cluster — the JSON template is hand-authored, using c8ctl element-template get <id> to fetch the base OOTB template as a starting point
• Path B: Java 17+, Maven 3.8+ (or Gradle equivalent), and a JVM hosting option for the resulting connector JAR — see camunda-development for installing the JDK / Maven toolchain locally

Cross-References

• camunda-development: Use first to decide whether building a connector is the right shape at all (vs. an OOTB connector or a job worker)
• camunda-connectors: Use for discovering and applying OOTB connectors — the catalog you're extending here
• camunda-job-workers: Use when the integration logic belongs in application code rather than a reusable connector (Path C in the decision matrix; workers are outbound-only)
• camunda-bpmn: Use for authoring the BPMN element the connector attaches to (service task for outbound, start/intermediate/boundary event or receive task for inbound)
• camunda-feel: Use for the FEEL expressions that pre-fill template properties and bind input/output mappings
• camunda-process-test: Use for end-to-end tests that drive a process through a custom connector