Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

camunda-development

Use this skill FIRST for any Camunda 8 integration or BPMN step that talks to another system — Slack, REST/HTTPS, webhooks, Kafka, S3, internal microservices, AI/LLM agents. The right implementation can't be read off the request's keywords (a "webhook" might be an OOTB connector or a custom inbound one; "LLM" a custom worker or the AI Agent connector); this skill weighs the full requirements (reusability, throughput, in-process state, transport, decision style) and hands off to camunda-connectors, camunda-connectors-development, camunda-job-workers, or camunda-ai-agents. Do not use for the actual build — switch to the focused skill it points to.

camunda · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add camunda/skills --skill camunda-development

About this skill


name: camunda-development description: | Use this skill FIRST for any Camunda 8 integration or BPMN step that talks to another system — Slack, REST/HTTPS, webhooks, Kafka, S3, internal microservices, AI/LLM agents. The right implementation can't be read off the request's keywords (a "webhook" might be an OOTB connector or a custom inbound one; "LLM" a custom worker or the AI Agent connector); this skill weighs the full requirements (reusability, throughput, in-process state, transport, decision style) and hands off to camunda-connectors, camunda-connectors-development, camunda-job-workers, or camunda-ai-agents.

Do not use for the actual build — switch to the focused skill it points to.

Camunda Development

Decide between out-of-the-box connectors, custom connector templates, custom Java connectors via the Connectors SDK, and job workers before writing any integration code for Camunda 8.8+. This skill is a thin orientation layer — every path it identifies has its own focused build skill.

Cross-References

  • camunda-connectors: Use for browsing and applying an existing OOTB connector template
  • camunda-connectors-development: Use for building a custom connector (JSON-only template on a protocol connector, or a Java connector via the Connectors SDK; covers both outbound and inbound)
  • camunda-job-workers: Use for implementing a job worker in Java, Spring Boot, or TypeScript
  • camunda-bpmn: Use for the BPMN element (service task, message event, …) that hosts the connector or worker job
  • camunda-process-test: Use for testing the resulting process

Decision matrix

Walk the questions top-down. Stop at the first one whose answer is yes.

  1. Does an out-of-the-box (OOTB) connector cover the integration? Search the local catalog with c8ctl element-template search "<keyword>" (see camunda-connectors). If a template matches the target system, use it as-is. Stop.

  2. Is the integration a single API call over a common protocol (REST, SOAP, GraphQL, Kafka, RabbitMQ, AWS SQS/SNS, …), and do you want a reusable, modeller-friendly building block? → Path A — JSON-only template on a protocol connector. No Java, no separate runtime. Customise the protocol connector's published template: pre-fill the URL with FEEL, hide method / base URL / auth, expose only the domain-specific properties. See camunda-connectors-development.

  3. Is the logic more than a single API call (proprietary protocol, multi-step orchestration with state, non-HTTP I/O, custom inbound trigger) and is the team on Java? → Path B — Custom Java connector via the Connectors SDK. Annotation-driven, auto-generated element template, built-in secrets / intrinsic functions / Camunda Documents. Works for outbound and inbound. See camunda-connectors-development.

  4. Otherwise — non-Java stack, or the logic already lives in your application, or you need low-level Zeebe APIs (job streaming, custom activation). → Path C — Job worker. Implement the handler in your app using one of the official SDKs (Java, Spring Boot, TypeScript covered here; other SDKs follow the same pattern). If you also want a modeller UI for the worker, hand-author an element template JSON. See camunda-job-workers.

Comparison: job worker vs. connector (SDK)

AspectJob workerConnector (SDK)
LanguageAny official SDK (Java, Spring Boot, TypeScript, …)Java only
DeliveryTied to the application that runs itLibrary, deployable into any Connector Runtime
Reusability across environmentsHard — re-wire per projectEasy — same JAR, drop into any runtime
FocusFull Zeebe client (activate, complete, fail, retries)Pure business logic; runtime handles Zeebe wiring
SecretsRoll your own (env vars, secret manager)Built-in {{secrets.NAME}} resolution
Low-level Zeebe APIsYesNo
Modeller UI for the taskOptional — hand-authored element template JSONStandardised — generated from @ElementTemplate
Element template auto-generationNone — author JSON by handMaven plugin generates it from annotations
Intrinsic functions (getText, base64, …)NoYes
Camunda Documents handlingManualBuilt-in
Inbound triggersNo (outbound jobs only)Yes (Webhook / Subscription / Polling)

The table is the why behind the matrix: connectors trade language reach for reusability and a richer surface; workers trade that surface for language choice and direct Zeebe access.

Worked example — applying the matrix

"Notify Slack when an order is approved. The team is on Node.js."

  1. OOTB connector? c8ctl element-template search "slack" returns io.camunda.connectors.Slack.v1. The bot-message operation covers a one-off notification with no custom UI requirement. → Use it. Stop here.

"Submit a job to our internal HTTP pricing API. The team is on Java. We want a reusable connector with only customerId, productSku, and quantity exposed in Modeler."

  1. OOTB? No matching template.
  2. Single API call over a protocol, Java team, reusable building block? Yes — REST. → Path A. Take the published HTTP REST connector template, pre-fill the URL with a FEEL expression that builds the request URL from customerId, hide the method / base URL / auth fields, expose only the three domain properties. JSON-only; nothing to deploy as a runtime. See camunda-connectors-development.

"Periodically pull invoices from an SFTP server and start a process per file. Team is on Java."

  1. OOTB? No SFTP-pull start-event connector that fits.
  2. Single API call over a common protocol? No — SFTP, custom poll cadence, inbound trigger.
  3. Complex integration, Java team? Yes. → Path B, with the Polling inbound flavour. Build it with the Connectors SDK. See camunda-connectors-development.

"Score a customer record using the team's existing Node.js scoring service."

Read the complete source ↗