bpmn-to-code

Appearance

bpmn-to-codeYour BPMN model changes. Your code doesn't break.

Stop hardcoding element IDs, messages, and worker types. Generate a type-safe Process API that stays in sync with your BPMN models.

✨ Try in Browser
Get Started (Gradle)
Get Started (Maven)

🛡️ Compile-Time Safety

Rename a BPMN element and the compiler tells you every spot that needs updating. No more silent runtime failures.

🔧 Works With Your Stack

Zeebe, Camunda 7, and Operaton. Java and Kotlin. Gradle and Maven. Fits into what you already use.

🌐 Try It Instantly

Paste your BPMN into the web app and see the generated code in seconds. No installation required.

⚡ Minimal Setup Effort

Available as a Gradle and Maven plugin. Also serves AI skills that auto-configure the plugin and migrate your existing code.

The problem it solves ​

BPMN-based process automation relies on string references scattered across your codebase. When someone renames an element in the BPMN model, nothing warns you until runtime.

kotlin
// Scattered across your codebase, no compiler help
client.newCreateInstanceCommand()
    .bpmnProcessId("newsletterSubscription")      // typo? runtime error.
    .send()

client.newPublishMessageCommand()
    .messageName("Message_FormSubmitted")          // renamed in BPMN? silent failure.
    .correlationKey(subscriptionId)
    .send()

@JobWorker(type = "newsletter.sendConfirmationMail")  // deleted task? no warning.
fun sendConfirmationMail() { /* ... */ }
kotlin
// Generated from your BPMN model. Rename an element → compiler error.
client.newCreateInstanceCommand()
    .bpmnProcessId(NewsletterSubscriptionProcessApi.PROCESS_ID)
    .send()

client.newPublishMessageCommand()
    .messageName(NewsletterSubscriptionProcessApi.Messages.MESSAGE_FORM_SUBMITTED)
    .correlationKey(subscriptionId)
    .send()

@JobWorker(type = NewsletterSubscriptionProcessApi.TaskTypes.NEWSLETTER_SEND_CONFIRMATION_MAIL)
fun sendConfirmationMail() { /* ... */ }