What are compensation events?

One of the outstanding features provided by Camunda 8 is its ability to easily handle business transactions that went awry. This workflow pattern allows businesses to define compensatory actions and “undo” steps in a workflow if some operations in the sequence fail. In today’s complex business processes spanning across distributed architectures, we can find many examples where executed tasks need to be undone to reflect the real-world state.

For example, when a system runs financial transactions, money transfers, or online credit applications, it needs to confirm the request, process the transaction, and update the account. If any of the stages are not completed, the system has to be capable of rolling the previous steps back to avoid incorrect transactions or data inconsistencies. Namely, it would be inappropriate to leave the credit request in the confirmed state if the loaned money didn’t arrive in the client’s account, say, because of a failure of a microservice.

So, in business operations, Camunda’s compensation events enable the automatic reversal of actions that were successfully completed, but their results and side effects are no longer seen as desirable. Thus, the compensation feature ensures the process is preserved in a consistent state in case of errors, exceptions, and cancellations.

How do compensation events work in Camunda 8?

Saga

To enforce effective compensation, Camunda supports Saga, an interaction pattern that works well in data consistency management across complex microservice architectures. Unlike the two-phase commit protocol frequently used in distributed systems, the Saga pattern doesn’t reduce the overall system availability with transaction locks. It is also perfectly suited to modern NoSQL databases and message brokers that don’t support two-phase commit.

Thus, Saga is the preferable option for long-running business processes and highly distributed systems, which are almost universal in banking nowadays. It breaks complex processes into small, manageable steps, each of them accompanied by a compensation action needed for correct recovery in case of failure. As a result, the system remains fault-tolerant and consistent while retaining scalability and performance.

Zeebe and BPMN

Camunda’s Zeebe engine works as a Saga Coordinator responsible for either completing the overall transaction or aborting it, bringing the system into a known termination state. The engine has a log-based, event-driven design, where every state change is captured in an append-only log. This allows for efficient recovery and state management, which is crucial for implementing compensation events.

Compensation events in Camunda are created using the BPMN 2.0 standard in Camunda Modeler. They work closely with the engine, which handles process execution efficiently and can scale well.

When a process instance enters a compensation intermediate throw or end event, it triggers the compensation within its scope and invokes all compensation handlers of completed activities. The compensation handlers of active or terminated activities are not invoked. The compensation throw event remains active until all invoked compensation handlers are completed.

Specifics for the implementation of Camunda’s compensation events

• Camunda makes it easy to model compensation in complex business processes with visual BPMN representations.
• Users can create a compensation activity for every task in a process model, be it a service task, a human task, or a subprocess.
• Camunda’s compensation can handle complicated situations like multiple instance activities, compensation handler interruption, triggering compensation handlers in a given order, and more.
• Users don’t need to hand-code rollback logic across multiple microservices and can build robust error-handling mechanisms directly into their process models.

All in all, compensation flows built in Camunda save you the trouble of tracking each transaction individually and ease the complexity of rollbacks.

Real case of a compensation event for banking

Let’s look at how Camunda’s compensation works in a real-life banking scenario of transferring funds. As we’d like to focus on compensation events, we will slightly simplify the process by combining all client validations taking place before a fund transfer into one service task. The validation activities include:

• Checking the format and correctness of the data entered, such as IBANs and bank details
• Confirming that the specified amount does not exceed existing limits
• Verifying the sufficiency of funds in the sender’s account
• Identity verification
• Anti-fraud, anti-money laundering, and compliance checks

The diagram below shows the following scenarios:

1. If any problems are detected during the data validation, Camunda sends a notification informing the client about the fund transfer cancellation. The process is completed.
2. If the validation is successful, the process goes on.
3. In the next step, the sending bank writes off the specified amount from the client’s account. All the operations with the account are logged in the system.
4. If something goes wrong during the write-off (the connection was broken, the bank did not send a response about debiting the account, etc.), Camunda informs the client that the fund transfer process ends in an error. The process is completed.
5. If the write-off operation is successful, the process continues.
6. The next step is replenishing the receiver’s account with the specified amount.
7. If the system identifies an error boundary event during the execution of this operation, Camunda informs the client and triggers a compensation event—a rollback of writing off the funds from the client’s account. Then, the process is completed.
8. If the crediting causes no errors, Camunda logs the account replenishment operation and notifies the recipient of the funds added to their balance. The process is completed.

By implementing the compensation event, the bank ensures no funds are lost or incorrectly processed, maintaining data consistency and complying with regulatory requirements.

Compensation events: use cases and benefits for banking

Compensation events aren’t limited to simple debit-credit operations. They can be used across a wide range of banking processes:

• Loan application processing. An approved loan can be rolled back automatically when a post-approval check fails.
• Fraud detection. It is possible to reverse a flagged fraudulent transaction and notify the relevant departments in the process.
• Cross-border payments. In case of exchange rate mismatches or compliance violations, multiple currency conversions and international transfer operations can be efficiently handled with compensatory actions.
• Lending and mortgage transactions. If the credited party changes their mind or calculation errors are detected, it will be appropriate to change the agreement terms or roll the whole process back with compensation events.
• Commission and fee calculation. When a customer is mistakenly charged a commission or fee, a refund is a surefire way of correcting the situation.
• Settlements and clearing operations. In the event of failures in clearing processes (for example, in interbank transfers), compensation events can roll back and re-execute transactions or ensure the funds’ reversal.
• Payment systems and acquiring. When a payment system fails to process a payment, it can use compensation events to cancel the transaction and return the funds to the customer.
• Card transactions. Returning funds or cancelling the transaction will also be helpful in case of an erroneous debiting, for example, because of duplicate transactions.
• Currency transactions. If there is a change in the exchange rate during the conversion process, compensation events may adjust the original transaction or return funds with due regard to the new conditions.
• Deposit transactions. If a client terminates a deposit agreement early or there are errors in interest calculations, compensation events may adjust the maths or roll back the transactions.

By adopting automated compensation and letting Camunda coordinate complex banking processes, financial institutions can reap many benefits:

1. Minimise financial risk. By defining compensation flows, banks can reduce the risk of incomplete or erroneous transactions, ensuring that funds are accurately handled.
2. Ensure compliance. Automated rollbacks help prevent unauthorised or incomplete transactions and thus work toward meeting regulatory requirements like the PCI DSS and GDPR.
3. Reduce manual workload. Compensation events allow banks to eliminate manual intervention in case of transaction failures, freeing up valuable human resources for more high-value tasks.
4. Enhance customer trust. Banks can build greater customer trust by implementing accurate and transparent transaction processing.

Using compensation events beyond banking 
As event-based, distributed architectures are frequently found outside the financial industry, Camunda’s compensation solution has a much broader application area. Here are some examples of the compensation events usage in other industries:

• Supply chain management: Prevent stock discrepancies by reversing inventory changes if a shipment fails.
• Healthcare: Handle errors in patient data processing or treatment scheduling when managing clinical trials.
• E-commerce: Automatically cancel order confirmations and refund payments in case of errors in order processing or payment authorisation.
• Insurance: Ensure accurate financial records by cancelling overpayments or rectifying policy processing errors.

Final thoughts

By leveraging compensation events, organisations can build more resilient and adaptable process automation frameworks. Thanks to the faster recovery from failures and the reduced risk of process downtime ensured by automated compensation, businesses become more agile and competitive. Camunda 8 provides a powerful mechanism for banks to handle the complexity of modern financial transactions with confidence. By automating rollback actions, they can meet regulatory requirements and enhance operational efficiency while offering a more secure and reliable banking experience for their customers. Contact Camunda or a certified Camunda partner to get professional help in designing your compensation events.

Editor’s Note: This post was written by Maria Alish, a Camunda Champion. Would you like to become a Camunda Champion, and potentially have your blog post published here as well? Learn more about our Champion Program and how you can apply.

The post How a Bank Uses Compensation Events in Camunda 8 appeared first on Camunda.

This Pride Month, for our “Meet a Camundi” series we invited a few Camundi to reflect on what Pride means to them, how their identity connects with their work, and what belonging truly feels like.

These are their personal stories: honest, moving, and real.

Jesse Sullivan (he/him), USA

1. What’s your name (and pronouns), role, and where in the world are you based?
   Hi there! I’m Jesse Sullivan (he/him), Senior Talent Acquisition Partner here at Camunda. I have the joy of recruiting across several dynamic teams, such as Revenue Operations, Account Development, and Accounting and Finance, helping us grow by bringing in incredible talent every day. I’m currently based just outside Birmingham, Alabama, where I live with my partner of 12 years and our lovable rescue dog, who’s been part of our little family for the past 7 years.
   
2. What does Pride symbolize to you?
   Pride, to me, means showing up as you are, authentically and freely, while recognizing the strength it takes to get there. It is a celebration of the freedom to live openly and visibly, while honoring the resilience and milestones of those who made and continue to make that freedom possible.
   
3. What does belonging at work look or feel like for you?
   Belonging at work feels like knowing my voice matters and will be respected. At Camunda, I’m grateful to be part of a global team made up of people from many different backgrounds. Diversity brings a multitude of valuable perspectives, and when we genuinely value and learn from one another, it creates a culture of real respect, support, and belonging.
   
4. If you could give your younger self one message during Pride Month, what would it be?
   You’ve entered the world with joy, creativity, and self-expression, but a lot of people will try to dim that. They’ll tease your mannerisms, your love of dolls and girl groups, your vibrant spirit. Those aren’t flaws to be hidden, but some of the best parts of you.
   
5. What’s something fun or surprising people might not know about you?
   Back in middle school, I was absolutely convinced I was destined for Harvard and a career as a lawyer. I even bought a couple of books about getting into law school and joined the debate team, without telling anyone my real motivation. Spoiler alert: it wasn’t some grand passion for law. I just loved the movie ‘Legally Blonde’ way too much.
   
6. Is there anything else that you’d love to talk about or that feels meaningful to share?
   Some years, it feels like more companies show up for Pride, and other years, things go quiet. That shift often seems tied to what’s happening in the broader cultural or political climate, but it shouldn’t be. Supporting the LGBTQIA+ community shouldn’t be driven by trends or appearances, but by consistent commitment, genuine courage, and a dedication to doing what’s right.

Jesse’s reflections on visibility and joy remind us how far we’ve come  and how important it is to protect that progress.

Next, Tassilo shares his own journey and why allyship, visibility, and quirky reality TV obsessions matter just as much.

Tassilo Weidner-Mühl (he/him), Germany

1. What’s your name (and pronouns), role, and where in the world are you based?
   Hello! I am Tassilo Weidner-Mühl (he/him/his), an Engineering Manager based in Berlin, Germany.
   
2. What advice would you give to someone who’s early in their journey or struggling to bring their whole self to work?
   The first thing I’d say is: you are not alone. Remember, diversity is our strength. Don’t stress about blending in too much—celebrate what makes you unique. The majority of people are more accepting and supportive than you might think. Keep shining!
   
3. What gives you hope or energy when it comes to LGBTQIA+ visibility and rights today?
   It’s incredibly inspiring to see how much LGBTQIA+ visibility has grown over the years. When I was younger, it was tough to find any role models or representation in the media. Now, we see openly queer TV show hosts, actors, and entire shows dedicated to queer stories. This shift is monumental for young people exploring their identities and looking for relatable figures. It’s an exciting time to be part of the community!
   
4. What’s something fun or surprising people might not know about you?
   My guilty pleasure is watching reality TV shows. I especially love watching the team dynamics as groups navigate challenging situations. Despite the exaggerated drama, I eagerly tune in for the next episode—it’s one of my quirky ways to relax.
   
5. Is there anything else that you’d love to talk about or that feels meaningful to share?
   As a gay man, it’s heartwarming to witness the advancements in my rights and societal acceptance. However, I recognize that trans individuals still face significant challenges. My personal focus has shifted towards being a strong ally for the trans community. Let’s continue the fight for equality together!

From Berlin to Johannesburg—Wes brings their own story of identity, resilience, and intention. As someone helping shape our systems of fairness and support, their voice is both powerful and personal.

Wesley Hattingh (they/them), South Africa

1.  What’s your name (and pronouns), role, and where in the world are you based?
   My name is Wes Hattingh (pronouns: they/them), and I’m the Manager of Total Rewards at Camunda. I’m based out of Johannesburg, South Africa. It’s a privilege to be part of a global team from here, working to make Camunda a place where the best talent wants to invest their time and energy in creating a world-class product.
   
2. Have there been ways Camunda has supported your identity, or are there things you’d love to see more of?
   From my first day, I have never felt the need to hide my identity at Camunda. While assumptions can happen anywhere (and do), the environment here is fundamentally built on trust, acceptance, and treating others with respect and dignity. That’s not an easy culture to create, as it requires a really strong baseline of respect, and I’m genuinely grateful for it. Looking forward, I’m really excited to see more life breathed back into our Employee Resource Groups (ERGs). Especially in a world where human rights for queer folk and other identities are globally eroding to some degree, having an intentional space where we can come together is not just important, it’s vital.
   
3. What advice would you give someone just starting to explore their identity?
   Have courage and be kind to yourself; it’s a journey that takes time and doesn’t happen in one day. Seek out support, whether in-person or in safe digital spaces. Where you have the energy, be prepared to correct people or surround yourself with those you trust who can advocate on your behalf, but importantly, always be unapologetically you. Life is too short to be overly invested in what other people think, a lesson I continue to learn as a recovering people-pleaser. It’s a statement that comes with privilege, as I know it isn’t always safe for everyone to live so openly. And to everyone, I’d add: be kind and offer a smile to others as you go about your day. That small act of being seen and acknowledged goes farther than people think.
   
4. Any queer icons, books, movies, or media that inspire you?
   I’m deeply inspired by the work of Alok Vaid-Menon. Their advocacy and how they are themselves is a powerful reminder to look beyond binaries and see the beauty in authentic self-expression. I’ve also been moved by media like Heartstopper and Love, Simon. Even though they’re aimed at a younger audience, they’ve been quite emotional to watch (tissues anyone?), and it makes me think parts of me would be different now if this had been around when I was that age. They’re a reminder that parts of the world are improving, offering hope even as we see backwards movement elsewhere. This really highlights how important it is for allies to step up and help create that sense of belonging for queer folk, an emotion we have all struggled with at some point and likely continue to even as we are well into our adult years.
   
5. Is there anything else that you’d love to talk about or that feels meaningful to share?
   My work in Total Rewards is deeply connected to my identity and values. I am passionate about building systems and processes that are transparent, fair, and equitable. My goal is always to improve the everyday lived experience of those I serve in ways that align with the business. It’s incredibly meaningful for me to contribute to a workplace where people feel seen and valued for their unique talents, knowing that the structures in place are designed to support them, regardless of their background or identity.

From Johannesburg to across the globe, Wes’ story reminds us how inclusion is both personal and systemic. But allyship plays just as vital a role in shaping belonging.

Allyship in action: Creating space to grow

At Camunda, allyship is about showing up in everyday actions, often quietly, but with lasting impact. One Camundi shared their personal experience:

“Coming out as trans early in my transition was nerve-wracking, but my fears were quickly squelched by the amazing support from my colleagues at Camunda. I was touched by how many people quietly helped me update my name across systems, never making it a big deal or slipping up. I’ve come to see Camunda as a safe space where I’ve been able to grow at my own pace, whether reintroducing myself to customers or changing my appearance at in-person events.” 
—Lena Schönburg (she/her), Senior Software Engineer at Camunda.

True inclusion is built in these small moments where trust, courage, and community intersect. It’s what makes showing up as your full self possible.

Looking forward

Pride isn’t just a moment, it’s a movement. Whether through community conversations, inclusive policies, or simply showing up for each other every day, we remain committed to creating a workplace where every person is empowered to be their full, authentic self.

To the LGBTQIA+ members of our team and beyond: we see you, we celebrate you, and we stand with you—this month and always.

The post Pride at Camunda: Living Out Loud, Together appeared first on Camunda.

It’s one thing to get a large language model (LLM) to generate a summary, write an email, or classify a support ticket. It’s another entirely to make sure that use of AI fits your company’s legal, ethical, operational, and technical policies. That’s where governance comes in—and frankly, it’s where most organizations are struggling to find their footing.

The challenge isn’t just technical. Sure, you need to worry about prompt injection attacks, hallucinations, and model drift. But you also need to think about compliance audits, cost control, human oversight, and the dreaded question from your CEO: “Can you explain why the AI made that decision?” These aren’t abstract concerns anymore—they’re real business risks that can derail AI initiatives faster than you can say “responsible deployment.”

That’s where Camunda comes into the picture. We’re not an AI governance platform in the abstract sense. We don’t decide your policies for you, and we’re not going to tell you whether your use case is ethical or compliant. But what we do provide is something absolutely essential: a controlled environment to integrate, orchestrate, and monitor AI usage inside your processes, complete with the guardrails and visibility that support enterprise-grade governance.

Think of it this way: if AI governance is about making sure your organization uses AI responsibly, then Camunda is the operational backbone that makes those policies actually enforceable in production systems. We’re the difference between having a beautiful AI ethics document sitting in a SharePoint folder somewhere and actually implementing those principles in your day-to-day business operations.

This post will explore how Camunda fits into the broader picture of AI governance, diving into specific features—from agent orchestration to prompt tracking—that help you operationalize your policies and build trustworthy, compliant automations.

What is AI governance, and where does Camunda fit?

Before we dive into the technical details, it’s worth stepping back and talking about what AI governance actually means. The term gets thrown around a lot, but in practice, it covers everything from high-level ethical principles to nitty-gritty technical controls.

We’re framing this discussion around the “AI Governance Framework” provided by ai-governance.eu, which defines a comprehensive model for responsible AI oversight in enterprise and public-sector settings. The framework covers organizational structures, procedural requirements, legal compliance, and technical implementations.

Camunda plays a vital role in many areas of governance, but none more so than the “Technical Controls (TeC)” category.. This is where the rubber meets the road—where your governance policies get translated into actual system behaviors. Technical controls include enforcing process-level constraints on AI use, ensuring explainability and traceability of AI decisions, supporting human oversight and fallback mechanisms, and monitoring inputs, outputs, and usage metrics across your entire AI ecosystem.

Here’s the crucial point: these technical controls don’t replace governance policies—they ensure that those policies are actually followed in production systems, rather than just existing as aspirational documents that nobody reads.

1. Fine-grained control over how AI is used

The first step to responsible AI isn’t choosing the right model or writing the perfect prompt—it’s being deliberate about when, where, and how AI is used in the first place. This sounds obvious, but many organizations end up with AI sprawl, where different teams spin up AI integrations without any coordinated approach to governance.

With Camunda, AI usage is modeled explicitly in BPMN (Business Process Model and Notation), which means every AI interaction is part of a documented, versioned, and auditable process flow.

You can design processes that use Service Tasks to call out to LLMs or other AI services, but only under specific conditions and with explicit input validation. User Tasks can involve human reviewers before or after an AI step, ensuring critical decisions always have human oversight. Decision Tables (DMN) can evaluate whether AI is actually needed based on specific inputs or context. Error events and boundary events capture and handle failed or ambiguous AI responses, building governance directly into your process logic.

Because the tasks executed by Camunda’s AI agents are defined with BPMN, those tasks can be deterministic workflows themselves, ensuring that, on a granular level, execution is still predictable.

This level of orchestration lets you inject AI into your business processes on your own terms, rather than letting the AI system dictate behavior. You’re not just calling an API and hoping for the best—you’re designing a controlled environment where AI operates within explicit boundaries.

Here’s a concrete example: if you’re processing insurance claims and want to use AI to classify them as high, medium, or low priority, you can insert a user task to verify all “high priority” classifications before they get routed to your fraud investigation team. You can also add decision logic that automatically escalates claims above a certain dollar amount, regardless of what the AI thinks. This way, you keep humans in the loop for critical decisions without slowing down routine processing.

2. Your models, your infrastructure, your rules

One of the most frequent concerns about enterprise AI adoption centers on data privacy and vendor risk. Many organizations have strict requirements that no customer data, internal business logic, or proprietary context can be sent to third-party APIs or cloud-hosted LLMs.

Camunda’s approach to agentic orchestration supports complete model flexibility without sacrificing governance capabilities. You can use OpenAI, Anthropic, Mistral, Hugging Face, or any provider you choose, and, starting with Camunda 8.8 (coming in October 2025), you can also route calls to self-hosted LLMs running on your own infrastructure. Whether you’re running LLaMA 3 on-premises, using Ollama for local development, or connecting to a private cloud deployment, Camunda treats all of these as different endpoints in your process orchestration.

There’s no “magic” behind our AI integration—we provide open, composable connectors and SDKs that integrate with standard AI frameworks like LangChain. You control the routing logic, prompt templates, authentication mechanisms, and access credentials. Most importantly, your data stays exactly where you want it.

For example, a financial services provider might route customer account inquiries to a cloud-hosted model, but keep transaction details and personal financial information on-premises. With Camunda, you can model this routing logic explicitly using decision tables to determine which endpoint to use based on content and context.

3. Design AI tasks with guardrails: Preventing prompt injection and hallucinations

Prompt injection isn’t just a theoretical attack—it’s a real risk that can have serious business consequences. Any time an AI model processes user-generated input, there’s potential for malicious content to manipulate the model’s behavior in unintended ways.

Camunda helps mitigate these risks by providing structured approaches to AI integration. All data can be validated and sanitized before it is used in a prompt, preventing raw input from reaching the models. Prompts are designed using FEEL (Friendly Enough Expression Language), allowing prompts to be flexible and dynamic. This centralized prompt design means prompts become part of your process documentation rather than buried in application code. Camunda’s powerful execution listeners can be utilized to analyze and sanitize the prompt before it is sent to the agent.

Decision tables provide another layer of protection by filtering or flagging suspicious content before it reaches the model. You can build rules that automatically escalate requests containing certain keywords or patterns to human review.

When you build AI tasks with Camunda’s orchestration engine, you create a clear separation between the “business logic” of your process and the “creative output” of the model. This separation makes it much easier to test different scenarios, trace unexpected behaviors, and implement corrective measures. Camunda’s AI Task Agent supports guardrails, such as limiting the number of iterations it can perform, or the maximum number of tokens per request to help control costs.

4. Monitoring and auditing AI activity

You can’t govern what you can’t see. This might sound obvious, but many organizations deploy AI systems with minimal visibility into how they’re actually being used in production.

Optimize gives you comprehensive visibility into AI usage across all your processes. You can track the number of AI calls made per process or task, token usage (and therefore associated costs), response times and failure rates, and confidence scores or output quality metrics when available from your models.

This monitoring data supports multiple governance objectives. For cost control, you can spot overuse patterns and identify inefficient prompt chains. For policy compliance, you can prove that AI steps were reviewed when required. For performance tuning, you can compare model outputs over time or across different vendors to optimize both cost and quality.

You can build custom dashboards that break down AI usage by business unit, region, or product line, making AI usage measurable, accountable, and auditable. When auditors ask about your AI governance, you can show them actual data rather than just policy documents.

5. Multi-agent systems, modeled with guardrails

The future of enterprise AI isn’t just about better individual models—it’s about creating systems where multiple AI agents work together to achieve complex business goals.

Camunda’s agentic orchestration lets you design and govern these complex systems with the same rigor you’d apply to any other business process. Each agent—whether AI, human expert, or traditional software—gets modeled as a task within a larger orchestration flow. The platform defines how agents collaborate, hand off work, escalate problems, and recover from failures.

You can design parallel agent workflows with explicit coordination logic, conditional execution paths based on agent outputs, and human involvement at any point where governance requires it. Composable confidence checks ensure work only proceeds when all agents meet minimum quality thresholds.

Here’s a concrete example: in a legal document review process, one AI agent extracts key clauses, another summarizes the document, and a human attorney provides final review. Camunda coordinates these steps, tracks outcomes, and escalates if confidence scores are low or agents disagree on their assessments.

6. Enabling explainability and traceability

One of the most challenging aspects of AI governance is explainability. When an AI system makes a decision that affects your business or customers, stakeholders want to understand how and why that decision was made—and this is often a legal requirement in regulated industries.

Modern AI models are probabilistic systems that don’t provide neat explanations for their outputs. But Camunda addresses this by creating comprehensive audit trails that capture the context and process around every AI interaction.

For every AI step, Camunda persists the inputs provided to the model, outputs generated, and all prompt metadata. Each interaction gets correlated with the exact process instance that triggered it, creating a clear chain of causation. Version control for models, prompts, and orchestration logic means you can trace any historical decision back to the exact system configuration that was in place when it was made.

Through REST APIs, event streams, and Optimize reports, you can answer complex questions about AI usage patterns and decision outcomes. When regulators ask about specific decisions, you can provide comprehensive answers about what data was used, what models were involved, what confidence levels were reported, and whether human review occurred.

Camunda as a cornerstone of process-level AI governance

AI governance is a team sport that requires coordination across multiple organizational functions. You need clear policies, compliance frameworks, technical implementation, and ongoing oversight. No single platform can address all requirements, nor should it try to.

What Camunda brings to this collaborative effort is operational enforcement of governance policies at the process level. We’re not here to define your ethics policies—we provide the technical infrastructure to ensure that whatever policies you establish actually get implemented and enforced in your production AI systems.

Camunda gives you fine-grained control over exactly how AI gets used in your business processes, complete flexibility in model and hosting choices, robust orchestration of human-in-the-loop processes, comprehensive monitoring and auditing capabilities, protection against AI-specific risks like prompt injection, and support for cost tracking and usage visibility.

You bring the policies, compliance frameworks, and business requirements—Camunda helps you enforce them at runtime, at scale, and with the visibility and control that enterprise governance demands.

If you’re looking for a way to govern AI at the process layer—to bridge the gap between governance policy and operational reality—Camunda offers the controls, insights, and flexibility you need to do it safely, confidently, and sustainably as your AI initiatives grow and evolve.

Learn more

Looking to get started today? Download our ultimate guide to AI-powered process orchestration and automation to discover how to start effectively implementing AI into your business processes quickly.

The post Ensuring Responsible AI at Scale: Camunda’s Role in Governance and Control appeared first on Camunda.

That’s what NatWest Bank, a leading retail and commercial bank in the UK, set out to do with the help of Camunda. Joanne Barry, Head of Technology Fraud Prevention COE at NatWest, led off her recent CamundaCon presentation by quoting the CEO of NatWest, Paul Thwaite, whose stated goal is to “build a simpler, more integrated and technology-driven bank that is capable of even greater impact.” One of the most powerful ways to do that in 2025 is by operationalizing AI.

A complex environment

Milesh Chudasama, Digital Transformation Director at NatWest, then took the stage to set the scene. The Fraud Center of Excellence group at NatWest includes over 800 fraud center agents using an average of 14 applications per call, with over 60 tools available to them across a range of platforms.

As you can imagine, this is a complex setup and it takes a long time to train people well to provide a good customer experience and to be in full compliance with regulations. And when they leave, all that painstaking training goes with them.

The lack of standardization

Inconsistency from a lack of standardization is a big problem. This not only means that customers are not served in the same way every call, but it also means that processes are often recreated across multiple platforms, duplicating effort.

Milesh explained that a lack of orchestration is holding them back, and that “what we want to do is create a good solid process orchestration engine.” This will enable a headless architecture that they can replicate across as many platforms as they need to, saving enormous amounts of time and effort.

Unlocking the value of AI for fraud detection

NatWest is looking for AI to drive specific business outcomes. Joanne explained, “We know AI will transform our ability to deliver” these key results:

1. Increase customer engagement
2. Maximize agility
3. Drive operating leverage

To drive those outcomes, they have outlined a series of initiatives where AI can produce valuable results. As Milesh put it, the goal is to “use AI in the right way, and not let it run free… and do some stuff that can damage your reputation.”

Analyzing and digesting large amounts of data, along with writing and testing code, were powerful ways that the team is able to use AI to speed up their work and reduce their time to market. AI can also build on existing rules-based systems for something like anomaly detection, helping them detect patterns quickly and be more proactive, rather than reactive.

One exciting initiative included using AI within Camunda to move “the creation of initial BPMN diagrams to the left, so that the business generates it themselves,” which will result in much tighter business-IT alignment and accelerate the way they build processes to begin with. AI will also help the team reduce the number of applications they need to touch to solve a problem, improving the way a process is “governed and managed by a human and an AI agent” or by straight-through processing.

Disrupt and transform

AI clearly has the power to both disrupt and transform banking and financial services. The team at NatWest has identified a number of opportunities.

• Customer experience: AI can respond faster and automate more cases, improving customer satisfaction.
• Engineering productivity: AI tools can help teams write code or design BPMN diagrams much more rapidly than before, speeding up production and making collaboration easier.
• Process simplification: Features like Optimize give them data points so they can understand what works and what doesn’t, and where AI can be most effective.
• Fraud/Financial crime: Understanding patterns and which things to react to and which not to, which is critical with the reports of fraud growing daily.

One key Milesh highlighted was the ability to determine “how far you want the AI to service a customer before you break out from the AI” and hand off to a human. This is a critical step in ensuring a good customer experience and avoiding the problems of AI attempting to navigate an issue that is too complex for it.

What’s next?

Milesh noted that what he really wants his team to do is make sure the customer gets the same journey no matter how they interact with the company. “Not omnichannel,” he observed, “let’s call it optichannel—the right customer to the right journey to get the right output.” Using tools like Optimize to simplify and automate processes, and orchestrating end-to-end with Camunda to better understand processes and remove human touchpoints where it’s most effective, will help them get there faster.

See the full presentation and more from CamundaCon Amsterdam 2025

You can check out the full presentation from NatWest here or watch it below, and for more be sure to check out all the recordings from CamundaCon Amsterdam 2025.

If you liked this and wish you’d seen it live, don’t miss your chance to join us at the next CamundaCon! Register now for CamundaCon New York 2025.

The post Reinventing Fraud Detection: NatWest’s Journey to Operationalize AI with Camunda appeared first on Camunda.

We’re taking a bit more time to ensure the program continues to offer a rewarding experience for all Champions—past, present and future.

How to become a Camunda Champion

There’s no single path to becoming a Champion—we recognize and value a wide range of contributions. Whether you’re writing code, giving talks, creating tutorials, or supporting others, we want to hear from you!

Here are some of the ways you can contribute and we consider key for the program:

• Camunda 8 Expert – Demonstrate deep expertise in Camunda 8
  
• Code Contributor – Enhance Camunda projects with your coding skills
  
• Tutorial Creator – Share your knowledge through engaging YouTube videos
  
• Marketplace Innovator – Build and maintain connectors or blueprints
  
• Blog Writer – Share insights via blog posts, internally or externally
  
• Event Speaker – Present your work and ideas at meet-ups or conferences
  
• Meet-up Organizer – Bring people together by hosting local meet-ups
  
• Knowledge Sharer – Lead knowledge-sharing sessions in your organization
  
• Supportive Mentor – Help others in the community through the Forum
  
• Passionate Advocate – Spread the word and inspire others to build with Camunda
  

If you’re unsure whether you should apply—go for it! When the time comes, fill out the application form when it opens in October.

Learn more about the program and current Champions here: Camunda Champion Program.

Stay Informed

We’ll share more details as the date approaches through the Camunda Developer Newsletter and our social media channels. Be sure to follow us to stay in the loop!

We can’t wait to welcome a new cohort of passionate, engaged, and inspiring Champions this October!

The post 2025 Camunda Champion Program Launching in October appeared first on Camunda.

Update: The alpha release is officially live for all who wish to download.

Below is a summary of everything new in Camunda for this June with the 8.8-alpha5 release.

This blog is organized using the following product house, with E2E Process Orchestration at the foundation and our product components represented by the building bricks. This organization allows us to organize the components to highlight how we believe Camunda builds the best infrastructure for your processes, with a strong foundation of orchestration and AI thoughtfully infused throughout.

E2E Process Orchestration

This section will update you on the components that make up Camunda’s foundation, including the underlying engine, platform operations, security, and API.

Zeebe

The Zeebe team focused on big fixes for this release.

Operate

For this release, our Operate engineering team worked on bug fixes.

Tasklist

For this release, we have continued to work on bug fixes in Tasklist as well.

Web Modeler

With this alpha release of Web Modeler, we’re introducing powerful new features that streamline process modeling and enhance the developer experience.

Azure Repos Sync

Camunda now supports an integration with Azure DevOps, which allows for direct synchronization with Azure repositories.

FEEL Copilot

Pro- and low-code developers using Web Modeler SaaS can develop FEEL expressions with an integrated editor that pulls process variables and process context, making it easy for anyone to perform business logic in Camunda.

For Web Modeler SaaS customers, it also features the ‘FEEL Copilot’ which takes advantage of integrated generative AI to write and debug executable FEEL (Friendly Enough Expression Language) expressions.

Desktop Modeler

This alpha, we have also provided more functionality for our Desktop Modeler.

Process application deployment

A process application is now deployed as a single bundle of files. This allows using deployment binding for called processes, decisions, and linked forms.

Deployed decision link to Operate

After a DMN file is deployed to Camunda, links to the deployed decisions in Operate are displayed in the success notification.

Enhanced FEEL suggestions

Literal values like true or false are now displayed in the autocompletion for fast and easy expression writing.

Check out the full release notes for the latest Desktop Modeler 5.36 release right here.

Optimize

Our Optimize engineering team has been working on bug fixes this release cycle.

Identity

Camunda’s new Identity service delivers enhanced authentication and fine-grained authorization capabilities across both Self-Managed and SaaS environments. Key updates include:

• Self-Managed Identity Management: Administrators can natively manage users, groups, roles, and memberships via the Identity database—without relying on external systems.
  
• OIDC Integration: Supports seamless integration with standards-compliant external Identity Providers (IdPs), including Keycloak and Microsoft Entra (formerly Azure AD), enabling single sign-on (SSO) and federated identity management.
  
• Role-Based Access Control (RBAC): Provides resource-level access control with assignable roles and group-based permissions, enabling precise scoping of user capabilities across the platform.
  
• Flexible Mapping: Users, groups, and roles can now be dynamically mapped to resource authorizations and multi-tenant contexts, supporting complex enterprise and multi-tenant deployment scenarios.
  
• Migration Support: Simplified tooling facilitates migration from legacy Identity configurations to the new service, reducing operational overhead and enabling a phased rollout.
  
• Organizational Identity for SaaS: In SaaS deployments, customers can integrate their own IdP, allowing centralized management of organizational identities while maintaining cluster-specific resource isolation.
  
• Cluster-Specific Roles & Groups: SaaS environments now support tenant-isolated roles, groups, and authorizations per cluster, ensuring that customer-specific access policies are enforced at runtime.

Please see our release notes for more on the updates to Identity management.

Console

The Console engineering team has been working on bug fixes this release cycle.

Installation Options

This section gives updates on our installation options and various supported software components.

Self-Managed

For our self-managed customers, we have introduced a graceful shutdown for C8Run by rebuilding how we manage C8Run started processes. This resolves an issue where stopping C8Run during the startup process can create zombie processes.

We have also added features to support supplying image.digest in the values.yaml file instead of an image tag as well as the support for an Ingress external hostname.

Task Automation Components

In this section, you can find information related to the components that allow you to build and automate your processes including our modelers and connectors.

Connectors

We have introduced two connectors to support agentic AI with Camunda. You can find more on Camunda and Agentic in the Agentic Orchestration section in this blog post.

• The AI Agent connector which was recently published on Camunda Marketplace is now officially included as part of this alpha release and directly available in Web Modeler. This connector is designed for use with an ad-hoc sub-process in a feedback loop, providing automated user interaction and tool discovery/selection.
  
  The connector supports providing a custom OpenAI endpoint to be used in combination with custom providers and locally hosted models (such as Ollama).
  
• The Vector Database connector, also published to Camunda Marketplace, allows embedding, storing, and retrieving Large Language Model (LLM) embeddings. This enables building AI-based solutions for your organizations, such as context document search and long-term LLM memory and can be used in combination with the AI Agent connector for RAG (Retrieval-Augmented Generation) use cases.

Agentic Orchestration

With a continued focus on operationalizing AI, this section provides information about the continued support of agentic orchestration in our product components. This new Agentic Orchestration documentation section of our release blog is a great starting point to explore Camunda’s Agentic Orchestration approach. 

To support modern automation requirements, Camunda has adopted orchestration patterns that enable AI agents and processes to remain adaptive by combining deterministic with dynamic orchestration.

This architecture allows agents to incorporate dynamic knowledge into their planning loops and decision processes. The same mechanisms also support continuous learning, by updating and expanding the knowledge base based on runtime feedback.

To support this approach, Camunda has incorporated both our Vector Database connector and AI Agent Outbound connector directly into its orchestration layer.

Together, these capabilities allow Camunda to support agentic orchestration patterns such as:

• Planning loops that select and sequence tasks dynamically
• Use of short-term memory (process variables) and long-term memory (vector database retrievals)
• Integration of event-driven orchestration and multi-agent behaviors through nested ad-hoc subprocesses.

As mentioned in the Connectors section, we have recently released two connectors to support our approach:

• The AI Agent connector is designed for use with an ad-hoc sub-process in a feedback loop, providing automated user interaction and tool discovery/selection.
  
  This connector integrates with large language models (LLMs)—such as OpenAI or Anthropic—giving agents reasoning capabilities to select and execute ad-hoc sub-processes within a BPMN-modeled orchestration. Agents can evaluate the current process context, decide which tasks to run, and act autonomously—while maintaining full traceability and governance through the orchestration engine.
  
• The Vector Database connector which allows embedding, storing, and retrieving Large Language Model (LLM) embeddings. This enables building AI-based solutions for your organizations, such as context document search and long-term LLM memory and can be used in combination with the AI Agent connector for RAG (Retrieval-Augmented Generation) use cases.
  

If you would like to see these new connectors in action, we encourage you to review our website and see a video of how Camunda provides this functionality. We also have a step-by-step tutorial for using the AI Agent Connector in our blog.

Camunda 7

There are several updates in this release for Camunda 7.

Support for Spring Boot 3.5

This alpha release features support for Spring Boot 3.5.0.

New LegacyJobRetryBehaviorEnabled process engine flag

Starting with versions 7.22.5, 7.23.2 and 7.24.0, the process engine introduces a new configuration flag: legacyJobRetryBehaviorEnabled.

By default, when a job is created, its retry count is determined based on the camunda:failedJobRetryTimeCycle expression defined in the BPMN model.

However, setting legacyJobRetryBehaviorEnabled to true enables the legacy behavior, where the job is initially assigned a fixed number of retries (typically 3), regardless of the retry configuration.

In 7.22.5+ and in 7.23.2+ the default value is true for legacyJobRetryBehaviorEnabled. For 7.24.0+ the default value is false for legacyJobRetryBehaviorEnabled .

External task REST API and OpenAPI extended

Now the External task REST API is extended with the createTime field. OpenAPI is updated as well along with the extensionProperties for the LockedExternalTaskDto.

You can find the latest OpenAPI documentation here. Thank you for this community contribution.

Camunda 7 to Camunda 8 Migration Tools

With our Camunda 7 to Camunda 8 Migration Tools 0.1.0-alpha2 release, the Camunda 7 to Camunda 8 Data Migrator brings many quality of life improvements for our customers that are moving from Camunda 7 to Camunda 8.

Auto-deployment with Migrator Application

To help you migrate seamlessly, the BPMN diagrams that are placed in ./configuration/resources directory are auto-deployed to Camunda 8 when starting the migrator application.

Simplified Configuration

We’ve also made it easier to configure the Camunda 8 client allowing you to define client settings such as the Zeebe URL directly in the application.yml file.

Logging Levels

In addition, logging has been enhanced with the introduction of logging levels, as well as more specific warnings and errors.

For example, if a Camunda 7 process instance is in a state that cannot be consistently translated to Camunda 8, a warning is logged and the process instance is skipped.

To proceed, these instances must be adjusted in Camunda 7. Once complete, with the recent updates, you can resume migration for previously skipped and adjusted instances.

While the Camunda 7 to Camunda 8 Migration Tools are still in alpha, you can already check out the project and give it a try! Visit https://github.com/camunda/c7-data-migrator.

Thank you

We hope you enjoy our latest minor release updates! For more details, be sure to review the latest release notes as well. If you have any feedback or thoughts, please feel free to contact us or let us know on our forum.

If you don’t have an account, you can try out the latest version today with a free trial.

The post Camunda Alpha Release for June 2025 appeared first on Camunda.

In this post, we’ll walk through what RPA is, how to tackle the RPA Challenge using Camunda’s tools, from scripting the bot to deploying and executing it within a BPMN workflow, and finally how process orchestration can help super-charge your RPA bots.

What is RPA, and why should you care?

Robotic Process Automation (RPA) is a technology that allows you to automate repetitive, rule-based tasks typically performed by humans. Think of actions like copying data between systems, filling out web forms, or processing invoices—if it follows a predictable pattern, RPA can probably handle it. The goal is to free up people from mundane work so they can focus on higher-value tasks that require creativity, problem-solving, or empathy.

At the heart of RPA is the RPA bot, a small script that mimics human actions on a computer. These bots can click buttons, read emails, move files, enter data, and more. They’re like digital assistants that never sleep, don’t make typos, and follow instructions exactly as given. And unlike traditional software scripts, RPA bots are often designed to work with existing user interfaces, so you don’t need to rebuild backend systems to automate work.

If you already use process orchestration, why use RPA at all? Because it’s a fast, cost-effective way to automate existing business processes without major changes to your IT infrastructure. Whether you’re streamlining internal workflows or integrating legacy systems with modern platforms like Camunda, RPA gives you the power to get more done, faster—and with fewer errors. When combined with process orchestration, it becomes even more powerful, allowing bots to operate as part of larger, end-to-end business processes.

Follow along with the video

We’re going to dig into the RPA Challenge with a full tutorial below, but feel free to follow along with the video as well.

Understanding the RPA script

To solve the RPA Challenge, we used a script written in Robot Framework, a generic open-source automation framework. The script is built with Camunda’s RPA components, allowing seamless orchestration within a BPMN process. You can view the full script, as well as a BPMN model that uses the script, by clicking here. In this section, we’ll walk through the script in detail.

Settings

*** Settings ***
Documentation       Robot to solve the first challenge at rpachallenge.com,
...                 which consists of filling a form that randomly rearranges
...                 itself for ten times, with data taken from a provided
...                 Microsoft Excel file. Return Congratulation message to Camunda.
Library             Camunda.Browser.Selenium    auto_close=${False}
Library             Camunda.Excel.Files 
Library             Camunda.HTTP
Library             Camunda

The Settings section defines metadata and dependencies for the script:

• Documentation: A human-readable description of what the robot does. In this case, it describes the task of filling a dynamically rearranging form using Excel data.
• Library: These lines load external libraries required for the script to run. Robot Framework supports many built-in and third-party libraries. When using Camunda’s implementation, you can also use Camunda-specific RPA libraries tailored to browser automation, Excel file handling, HTTP actions, and integration with the Camunda platform.

When writing a RPA script, you can import as many libraries as needed to accomplish the task at hand. Here’s what each library used in this challenge does:

• Camunda.Browser.Selenium: Enables browser automation via Selenium. The auto_close=${False} argument ensures the browser doesn’t automatically close after execution, useful for debugging.
• Camunda.Excel.Files: Provides utilities to read data from Excel files, which is essential for this challenge.
• Camunda.HTTP: Used to download the Excel file from the RPA Challenge site.
• Camunda: Core Camunda RPA library that helps interact with the platform, such as setting output variables for process orchestration.

Tasks

*** Tasks ***
Complete the challenge
    Start the challenge
    Fill the forms
    Collect the results

The Tasks section defines high-level actions that the robot will execute. In Robot Framework, a “task” is essentially a named sequence of keyword calls and defines every action the robot will take.

Each task is given a friendly name (for this challenge, the task is named “Complete the challenge”). This task is composed of three keyword invocations:

• Start the challenge: Opens the site and prepares the environment.
• Fill the forms: Loops through the Excel data and fills out the form.
• Collect the results: Captures the output message after the form submissions are complete.

Each of these steps corresponds to a custom keyword defined in the next section.

Keywords

The Keywords section is where we define reusable building blocks of the automation script. Keywords are like functions or procedures. Each keyword performs a specific operation, and you can call them from tasks or other keywords. The order keywords are defined does not matter, as they are executed individually as defined in the task.

Let’s break down each one.

Start the challenge

Start the challenge
    Open Browser   http://rpachallenge.com/         browser=chrome
    Maximize Browser Window
    Camunda.HTTP.Download
    ...    http://rpachallenge.com/assets/downloadFiles/challenge.xlsx
    ...    overwrite=True
    Click Button    xpath=//button[contains(text(), 'Start')]

This keyword sets up the browser environment and downloads the data file required for the challenge. It begins by launching a Chrome browser using the Open Browser keyword, which is part of the Camunda.Browser.Selenium library imported earlier, and navigates to rpachallenge.com. Once the site loads, the Maximize Browser Window keyword ensures that all elements on the page are fully visible and accessible for automation.

The script then uses the Camunda.HTTP.Download keyword from the Camunda.HTTP library to download the Excel file containing the challenge data; the overwrite=True argument ensures that an up-to-date version of the file is used each time the bot runs. Finally, it clicks the “Start” button on the page using the Click Button keyword, targeting the element via an XPath expression that identifies the button by its text. This action triggers the start of the challenge and reveals the form to be filled.

This keyword sets the stage for the main task by ensuring we’re on the correct page and have the necessary data.

Fill the forms

Fill the forms
    ${people}=    Get the list of people from the Excel file
    FOR    ${person}    IN    @{people}
        Fill and submit the form    ${person}
    END

This keyword performs the core automation logic by iterating over the data and filling out the form multiple times. It starts by calling the custom keyword Get the list of people from the Excel file, which reads the downloaded Excel file and returns its contents as a table—each row representing a different person.

The script then enters a loop using Robot Framework’s FOR ... IN ... END syntax, iterating through each person in the dataset. Within this loop, it calls the Fill and submit the form keyword, passing in the current person’s data. This step ensures that the form is filled and submitted once for every individual listed in the Excel file, effectively completing all ten iterations of the challenge.

The keyword demonstrates how modular and readable Robot Framework scripts can be. Each action is broken into self-contained logic blocks, which keeps the code clean and reusable.

Get the list of people from the Excel file

Get the list of people from the Excel file
    Open Workbook    challenge.xlsx
    ${table}=    Read Worksheet As Table    header=True
    Close Workbook
    RETURN    ${table}

This keyword is responsible for reading and parsing the data from the Excel file. It begins by using the Open Workbook keyword to open the downloaded challenge.xlsx file. Once the file is open, the Read Worksheet As Table keyword reads the contents of the worksheet and stores it as a table, with the header=True argument ensuring that the first row is treated as column headers—making the data easier to work with.

After reading the data, the Close Workbook keyword is called to properly close the file, which is a best practice to avoid file access issues. Finally, the keyword returns the parsed table using RETURN ${table}, allowing the calling keyword to loop through each row in the dataset.

The result is a list of dictionaries, where each dictionary represents a person’s data (e.g., first name, last name, email, etc.).

Fill and submit the form

Fill and submit the form
    [Arguments]    ${person}
    Input Text    xpath=//input[@ng-reflect-name="labelFirstName"]    ${person}[First Name]
    Input Text    xpath=//input[@ng-reflect-name="labelLastName"]    ${person}[Last Name]
    Input Text    xpath=//input[@ng-reflect-name="labelCompanyName"]    ${person}[Company Name]
    Input Text    xpath=//input[@ng-reflect-name="labelRole"]    ${person}[Role in Company]
    Input Text    xpath=//input[@ng-reflect-name="labelAddress"]    ${person}[Address]
    Input Text    xpath=//input[@ng-reflect-name="labelEmail"]    ${person}[Email]
    Input Text    xpath=//input[@ng-reflect-name="labelPhone"]    ${person}[Phone Number]
    Click Button    xpath=//input[@type='submit']

This keyword fills out the web form using data for a single person. It begins with the [Arguments] ${person} declaration, which accepts a dictionary containing one individual’s details—such as name, email, and company information—retrieved from the Excel file. The form fields are then populated using multiple Input Text keywords, each one targeting a specific input element on the page. These fields are identified using XPath expressions that match the ng-reflect-name attributes, ensuring the correct data is entered in the right place regardless of how the form rearranges itself. Once all fields are filled in, the Click Button keyword is used to submit the form, completing one iteration of the challenge.

The challenge dynamically rearranges form fields on each iteration, but these attributes remain consistent, making them a reliable way to target inputs.

Collect the results

Collect the results
    ${resultText}=    Get Text    xpath=//div[contains(@class, 'congratulations')]//div[contains(@class, 'message2')]
    Set Output Variable    resultText    ${resultText}
    Close Browser

After all the forms have been submitted, this keyword captures the final confirmation message displayed by the RPA Challenge. It starts by using the Get Text keyword to extract the congratulatory message shown on the screen, targeting the message element with an XPath expression that identifies the relevant section of the page.

The retrieved message is then passed to Camunda using the Set Output Variable keyword, which makes the result available to the surrounding BPMN process—allowing downstream tasks or process participants to use or display the outcome. Finally, the Close Browser keyword is called to shut down the browser window and clean up the automation environment.

Testing, deploying and executing with Camunda

Once your RPA script is ready, the next step is to test and integrate it into a Camunda workflow so it can be executed as part of a larger business process. To begin, you’ll need to download and install Camunda Modeler, a desktop application used to create BPMN diagrams and manage automation assets like RPA scripts. (Note: RPA scripts cannot be edited in Web Modeler currently; this feature is in development.) Desktop Modeler includes an RPA Script Editor, which allows you to open, write, test, and deploy Robot Framework scripts directly from within the application.

Before deploying the script to Camunda, it’s a good idea to test it locally. Start by launching a local RPA worker—a component that polls for and executes RPA jobs. You can find setup instructions for the worker in Camunda’s Getting Started with RPA guide. Once your worker is running, use the RPA Script Editor in Camunda Modeler to open your script and run it. This will launch the browser, execute your automation logic, and allow you to verify that the bot behaves as expected and completes the RPA Challenge successfully.

After confirming the script works, you can deploy it to your Camunda 8 cluster. Ensure that you have set an “ID” for the RPA script; this ID is how your BPMN process will reference and invoke the script. In the Modeler, click the “Deploy” button in the RPA Script Editor and choose the target cluster.

Next, create a new BPMN model in the Camunda Modeler to orchestrate the RPA bot. Start with a simple diagram that includes a Start Event, a Task, and an End Event. Select the Task and change it to the “RPA Connector”. Then, in the input parameters for the task, set the “Script ID” parameter to the ID you set in the RPA script earlier.

Once your BPMN model is ready, deploy it to the same Camunda cluster. To execute the process, you can either use the Camunda Console’s UI to start a new process instance or call the REST API. The RPA Worker will pick up the job, run the associated script, and return any output variables—like the final confirmation message from the RPA Challenge—back to Camunda. You can monitor the execution and troubleshoot any issues in Camunda Operate, which provides visibility into your running and completed processes, including logs and variable values.

With that, your RPA script is fully integrated into a Camunda process. You now have a bot that not only completes the challenge but does so as part of a well-orchestrated, transparent, and scalable business workflow.

How Camunda supercharges your RPA bots

RPA is great at automating individual tasks—but what happens when you need to coordinate multiple bots, connect them with human workflows, or make them part of a larger business process? That’s where Camunda comes in.

Camunda is a process orchestration platform that helps you model, automate, and monitor complex business processes from end to end. Think of it as the brain that tells your RPA bots when to run, what data to use, and how they fit into the bigger picture. With Camunda, your bots are no longer isolated automation islands—they become integrated, managed components of scalable workflows.

For example, you might use a Camunda BPMN diagram to define a process where:

1. A customer submits a request (via a form or API),
2. An RPA bot retrieves data from a legacy system,
3. A human reviews the output,
4. Another bot sends the results via email.

Camunda handles all of this orchestration—making sure each task runs in the right order, managing exceptions, tracking progress, and providing visibility through tools like Camunda Operate. And because Camunda is standards-based (using BPMN), you get a clear, visual representation of your processes that both developers and business stakeholders can understand.

When you combine RPA with Camunda, you’re not just automating tasks—you’re transforming how your organization runs processes. You get flexibility, scalability, and transparency, all while reducing manual effort and human error. Whether you’re scaling up existing bots or orchestrating new workflows from scratch, Camunda makes your RPA investments go further.

Conclusion

Automating the RPA Challenge with Camunda showcases our ability to handle dynamic, UI-based tasks seamlessly. By combining Robot Framework scripting with Camunda’s orchestration capabilities, you can build robust automation workflows that integrate both modern and legacy systems.

Ready to take your automation to the next level? Explore Camunda’s RPA features and see how they can streamline your business processes. Be sure to check out our blog post on how to Build Your First Camunda RPA Task as well.

The post Solving the RPA Challenge with Camunda appeared first on Camunda.

Camunda is designed to make these and many other challenges far easier when it comes to business process orchestration and automation, not to mention adding numerous features you may never have thought of. Let’s explore how a Camunda-based solution adds value to an organization, accelerates solution development, increases agility, and helps in reducing the TCO (total cost of ownership) and shortening the TTM (time to market) for companies using it over a homegrown solution.

Improved business-IT collaboration

With Camunda, business teams get end-to-end visibility and control over the business process flow. What you see is what runs in the system!

Compare the BPMN flow below with the same logic living in a verbose document or a piece of code—the visual graphical model speaks for itself in terms of intuitiveness and clarity. With Camunda, the same BPMN model is used to design, implement, operate the solution and create business user reports. This gives all stakeholders visibility into what logic exactly runs inside the system.

The need to keep the documentation updated as the project evolves is obsolete. The BPMN is live documentation as well.

Reduced development effort

Why reinvent the wheel? Camunda helps you reduce development effort and focus only on implementing your use case specific business logic.

BPMN provides out-of-the-box support for complex logic, like asynchronous waits on an incoming message, timer-based action triggers, clearly defined compensation activities to implement rollbacks in a distributed transaction, automated error handling with an option for human intervention, and open standards based business rules with DMN;. all of this with the powerful scalability that Camunda provides.

Programming all of these on your own is redundant when Camunda does this out of the box. Leverage Camunda accelerators like connectors and reusable assets like blueprints.

Calling a REST API, SOAP service, Lambda function, RPA system, SAP, CRM, Database, or any of the other cloud services? We have you covered! Use the out-of-the-box connectors and accelerate your efforts! Here’s a sample of how easy it is to make a REST call:

Leverage the greatness of AI without additional integration effort—use the AI connectors to bring in intelligent process flow execution with Camunda. AI becomes just another endpoint to be orchestrated rather than investing development effort to establish this integration.

Leverage our AI-based BPMN Copilot to convert your verbose use case documentation or existing programs with business logic to create BPMN. Save time and accelerate your implementation!

Create UI forms in a low-code fashion—make use of Camunda forms to quickly create UI forms using the drag-drop Camunda forms editor. Nontechnical business users can quickly create UI forms themselves, and for the cherry on top? You can create forms in Camunda and display them in your custom front end applications!

Gain end-to-end visibility across the process model

Camunda enables true end-to-end visibility across your whole process model. For example:

• Diagnostics and troubleshooting get easier since you can exactly pinpoint the status of the workflow or the point of failure without having to devour log files from multiple systems, especially in case of distributed systems or microservice architectures.
• This enhances the efficiency of the operations and support teams, which need fewer FTE, freeing up IT teams to focus on innovation.

Check out the screenshot below of a sample Operate dashboard demonstrating the data variables and point of failure.

Business reports and insights out of the box

With Optimize, Camunda helps you generate detailed reports automatically. We provide the ability for business users to create self-service reports that are near real time using a wizard-based approach without any query languages.

Use Optimize’s wizard-based approach to:

• Define your business KPIs and business audit reports
• Identify opportunities to improve the business process flow
• Create datasets that are ML-ready for further analysis
• Set up alerts in case of KPI accomplishments/SLA breaches and so on

Take a look at the sample Optimize dashboard below:

Increased operational agility

Changes to your business flows become much clearer and faster when you use Camunda. For example:

• Moving the business logic into BPMN and DMN cuts down on a lot of complexity, and maintenance over the longer term becomes easier.
• With traditional systems, you could need a daunting amount of time to analyze the impact of the change in the code base and implement the code changes while keeping the code base maintainable.
• With the business process depicted in the graphical BPMN notation, the impact analysis is short. Implementing the change could range from simply reorganizing the tasks in the BPMN to adding or removing tasks from the BPMN to modifying your service-task or custom connector implementations to changing the rules in DMN tables. All much easier and more straightforward.

Agile and IT teams can quickly respond to change requirements to meet business needs, ensuring that your solution can remain compliant to ever-changing regulatory compliance requirements. This of course also enables your business to remain competitive in the market.

Disaster Recovery

Zeebe has built-in active-active replication, which means you have Disaster Recovery (DR) out of the box. This lays the foundation for a resilient and highly available stage engine. Additionally we also support multi-region setups, enabling active-active or active-passive modes of Disaster Recovery across different geographical regions to ensure resilience for mission critical applications.

Innovate at any scale

Since there is no database backing its state, Camunda can scale almost linearly to meet your growing throughput requirements as your business grows! Need more throughput? It could be as simple as adding more nodes and scaling the Zeebe Cluster.

Our benchmarks have demonstrated that we can handle hundreds of process instances and thousands of task instances per second. Camunda can also handle both high throughput and low-latency use cases. Take a look at the following Grafana snapshot from a Camunda benchmark run using a BPMN process with 11 service tasks.

An open, composable, and flexible architecture

We use open standards for building the process models and implementing business rules. Camunda strives to provide low-code features to accelerate solutioning while also being developer-friendly to implement customised solutions.

By now, we all know that customisations to out-of-the-box features are often necessary. Camunda is flexible and composable, allowing you to replace out-of-the-box components with custom coding where needed. Design standardized solutions without vendor lock-in!

We’ll take care of process orchestration so you can focus on your business problems

Rather than building all these capabilities from scratch again, leverage our orchestration platform’s capabilities to help your IT teams focus on just solving your business problems. We’ll take care of orchestrating your business process flows end-to-end at scale!

The rest of the iceberg

What’s next? Camunda’s flexible, scalable, and intelligent orchestration and automation platform empowers you to create a composable and best-of-breed architecture. Operationalize AI to meet your current business requirements while staying comfortably poised to leverage other new technological disruptors as they become available in the future.

The platform provides a number of out-of-the-box components like RPA to integrate with legacy systems, Tasklist to enable human interaction, a DMN-based business rules engine, and Intelligent Document Processing.

Camunda is also flexible enough to be used in a plug-and-play fashion. Swap a certain OTB component with your specific solution. For instance, you could swap Camunda’s RPA with your existing RPA solution, or swap the Tasklist with your custom UI.

Similar to a building made of LEGO blocks, Camunda provides the flexibility to swap out the components that you want with other implementations to suit your needs. This lets you eliminate vendor lock-in and discover more value for your business!

Moving from a legacy solution to Camunda

Hopefully the value Camunda provides is easy to see, but of course it’s still a change if you’re already using something else. If you’re evaluating the effort to migrate from your programming-based solution to Camunda, be sure to:

• Check out Camunda’s BPMN Copilot to convert the business process logic in your programming code like Python, Java, C# etc into BPMN quickly. This saves a huge chunk of time while migrating your business process flow to Camunda.
• Consider that you can refactor business-specific logic into service tasks or project/enterprise-specific connectors, promoting standardisation and reuse.
• Talk to us! We’re happy to explore the possibilities and benefits for your specific use case!

The post The Benefits of Using Camunda Compared to Traditional IT Solutions appeared first on Camunda.

In this special “Meet a Camundi” series highlight, we’re celebrating some of the people behind the momentum of Camunda’s Account Development (ADR) team. You’ll hear directly from a few ADR team members as they share their unique career journeys, the challenges they’ve tackled, proud moments they’ve experienced, and the culture, camaraderie, and growth opportunities that keep them inspired.

Whether you’re already a Camundi or just getting to know Camunda, we hope this spotlight gives you a fresh perspective and a glimpse into the vibrant, fast-moving world of ADR at Camunda.

Belén Cangiano

What is your name and your role at Camunda?

My name is Belén Cangiano, and I’m an account development representative (ADR) at Camunda, covering Iberia and the Middle East. My main focus is to generate high-quality pipeline opportunities that ultimately convert into annual recurring revenue (ARR) for our account executives and Camunda. I achieve this by leveraging a variety of channels, whether it’s inbound leads, outbound outreach, collaborations with partners, or working alongside Customer Success for expansion opportunities.

What experiences have shaped your career and led you to where you are today?

I studied languages and began my career as a school teacher and translator, working with children of all ages, NGOs, asylum seekers, and in prison settings. These experiences taught me to listen deeply, adapt quickly, and communicate with empathy across diverse contexts. Many things encouraged me to look for a change, and my partner suggested I try sales.

My first role in sales was as an enterprise SDR, where I learned the fundamentals of the job and how to be creative in my outreach to spark interest. I later transitioned into a 360 sales role at a startup, gaining firsthand insight into the full sales cycle, customer success, and the fast-paced reality of building something from the ground up.

These experiences shaped my ability to connect with people, understand their challenges, and help them discover real value through the right tools and solutions.

How did you learn about Camunda, and what motivated you to join the team?

I first heard about Camunda through a friend, an ADR at that time and today, one of the account executives working with me. He believed my profile aligned well with both the role and the company’s culture.

Once I explored more about Camunda, I saw how much the organization resonated with what I was looking for: a strong, supportive team, leadership that invests in people, and a clear path for growth. The company’s global presence and scaling momentum made it an exciting challenge.

What drew me to the ADR role in particular was the opportunity to be part of a company solving real, modern problems. It was clear that more and more organizations are seeking automation and orchestration technologies to improve efficiency and scalability, and I found that incredibly relevant. I wanted to be part of that journey by helping drive growth while learning in an innovative and evolving space. The remote setup was an added bonus, allowing me to maintain a healthy work-life balance.

Can you describe your team’s structure and how you collaborate day-to-day?

Our ADR team is divided by regions, which allows us to focus on specific markets while also delivering a more tailored experience (taking into account language, cultural nuances, market trends, and account knowledge).

Within the team, we collaborate daily by sharing what’s working (and what’s not), testing creative outreach strategies, refining messaging, and supporting each other in overcoming challenges. We also have an ADR board that helps surface and address key topics related to operations, marketing alignment, or team well-being, ensuring our voice is heard across the team.

While the role requires autonomy, we frequently work cross-functionally with account executives, partner managers, and customer success teams. These collaborations are key to building a more holistic understanding of each account or client, helping us see the full picture, not just from a sales perspective, but through the lens of long-term value and support.

By bringing together different expertise and points of view, we’re better equipped to identify where we can truly make an impact. These interactions not only enhance our results but also help us grow by exposing us to smarter, more effective ways of working.

What excites you the most about your work?

What I love most is the performance-driven nature of the role and how it pushes me to be both strategic and creative every day. Even though some tasks may repeat, outreach must always feel fresh, relevant, and personalized to capture someone’s attention.

It’s like solving a puzzle each day, figuring out what message or approach will truly resonate. The mix of challenge and creativity is what keeps me engaged.

Where are you currently based, and how has your experience been working with teammates in a fully remote setup?

I’m based in Auxy, a small village in France, and I genuinely enjoy the remote setup at Camunda. It allows me to organize my day with intention and maintain a healthy balance between work and personal life. Despite the distance, I make it a point to meet colleagues every month or two, whether at events or coworking spaces in Paris or around the world.

Camunda’s well-documented processes and collaborative culture make remote work not just possible, but productive and enjoyable.

What is a project or idea you’ve worked on at Camunda that you’re particularly proud of?

I’ve been involved in a cross-regional initiative to strengthen collaboration between ADRs and partner managers to drive pipeline growth. While it’s an ongoing project rather than a one-time deliverable, we’ve already seen positive results and stronger alignment across different regions.

It’s rewarding to contribute to a scalable effort that has impact beyond individual targets. This project has also allowed me to learn from peers and improve the way we engage with our partner ecosystem.

What’s one piece of advice you’d share with someone considering an ADR role at Camunda—especially someone earlier in their career?

Mindset is key. Skills can be learned, but having curiosity, resilience, and a willingness to consistently show up are what truly make the difference. Being an ADR comes with highs and lows (some days are full of wins, others are more challenging), but staying consistent and committed will take you far.

Can you share something about your personal life that colleagues might not know about you?

Something many colleagues might not know is that when I’m not on calls, I find my productivity sweet spot by drinking mate (yes, the Argentinian tea!) while listening to techno music. It’s my own quirky mix of focus and energy. Whether I’m writing emails or planning a strategy, that combo keeps me focused.

Joe White 

What is your name and your role at Camunda?

I’m Joe White, an account development representative at Camunda, covering the North American market.

What experiences have shaped your career and led you to where you are today?

I was an All-American track athlete while at Georgetown and have always loved working with people. This led me to seek a career in sales where I can have a healthy mix of both competition and helping others.

How did you learn about Camunda, and what motivated you to join the team?

What led me to join was the great product and even better people during my interview process. Everyone was extremely welcoming, and I saw great growth potential on the ADR team. The exciting thing about Camunda’s growth is meeting new and interesting colleagues from all over the world.

Can you describe your team’s structure and how you collaborate day-to-day?

Our team is structured regionally (NA, EMEA, APAC), with weekly syncs to align on goals and share best practices. My favorite thing about being part of the sales team is how willing everyone is to help and the incredible growth opportunities.

I collaborate cross-functionally daily, whether with Marketing, Customer Success, or other teams. It’s been incredible learning from their expertise and seeing how we all contribute to the bigger picture.

What excites you the most about your work?

I enjoy working with our customers and helping them toward their goals. What’s exciting to me is helping people see where Camunda could help their day-to-day operations.

Where are you currently based, and how has your experience been working with teammates in a fully remote setup?

I’m currently based in Philadelphia, Pennsylvania. My experience has been great! Camunda has offered a great deal of opportunities to see my coworkers. I’ve had the pleasure of traveling to places like London, Vienna, and Seattle to work together in person.

What is a project or idea you’ve worked on at Camunda that you’re particularly proud of?

One highlight was being named chief of staff for the ADR team. Since then, we’ve revamped our outbound strategy and even hit a quarterly record for opportunities generated!

What’s one piece of advice you’d share with someone considering an ADR role at Camunda—especially someone earlier in their career?

Take time to learn about our customers and what’s important to them. Also, reach out to cross-functional colleagues to ask questions and learn; everyone here is more than happy to help!

Can you share something about your personal life that colleagues might not know about you?

Here’s a fun fact: I competed in the 2016 and 2020 US Olympic track and field trials!

Matteo Gori

What is your name and your role at Camunda?

I’m Matteo Gori, account developer at Camunda. I work across a super diverse region, from Italy to Turkey and from Eastern Europe to Africa and Central Asia.

What experiences have shaped your career and led you to where you are today?

I started out with a bachelor’s degree in political science, driven by a curiosity for how the world works. That curiosity led me to pursue a master’s in international business management, a pivot that opened new doors. I had a brief stint in lobbying, trying to follow a long-time passion, but quickly realized it wasn’t quite the path for me.

As many of my peers jumped into consulting, I took a step back and thought: Do I really want the long hours and rigid environment? The answer was a clear no.

That’s when I found myself at Digimind (now Onclusive Social), a software company in Paris, where I got my first taste of sales in tech. I loved the energy of the role, the fast pace, the conversations, the strategy, but the company culture didn’t quite click. So I started looking around…and that’s when I found Camunda. It felt different from day one, open, ambitious, and human—and I’ve been here ever since!

How did you learn about Camunda, and what motivated you to join the team?

I actually hadn’t heard of Camunda before. One Sunday evening, while I was job hunting and not feeling great about my current role, a recruiter reached out on LinkedIn about an ADR position for the Italian market. The role was fully remote, and the company seemed to be growing fast, so I took the first call out of curiosity. After that, everything just clicked. The team, the culture, the mission—it all felt like a great fit. And that’s how it started.

What drew me in right away was how closely the ADR role matched what I was already doing—and enjoying—in my previous job as a BDR. I knew I wanted to stay in tech sales, and this felt like the natural next step.

The remote aspect was also a big plus. The idea of working from anywhere, without being stuck in a cubicle, really appealed to me. But what truly convinced me were the people. Everyone I spoke with during the interview process gave me a great feeling. Genuine, smart, and down-to-earth.

And finally, knowing the role wasn’t limited to just the Italian market made it even more exciting. I was hoping for something international and dynamic, and that’s exactly what I got.

Can you describe your team’s structure and how you collaborate day-to-day?

Our ADR team currently has 16 people, split into regional subteams:

• EMEA South (which I’m part of) with 3 ADRs
• EMEA North with 2
• DACH with 3
• APAC with 1
• The North America team, which is also divided into smaller group

And we’re still growing!

The team is led by our ADR director, Marli, along with regional ADR managers who support each group. Day-to-day, we’re constantly in touch—sharing best practices, asking questions, and helping each other out to book more quality meetings for our AEs.

What I love most about the role is how people-focused it is. You talk to someone new every day, each with a different personality, background, and way of thinking. And because my territory spans across very different regions, I get to experience all kinds of cultural nuances, which keeps things fresh and genuinely fascinating.

I work cross-functionally with other teams at Camunda pretty much every day, especially with the RevOps, Marketing, and Pre-Sales teams. Whether it’s checking in on a marketing lead, fixing an issue with lead routing, or looping in a sales engineer to help answer a technical question from a prospect, there’s always collaboration involved.

What I’ve learned is how valuable it is to have that support network. Everyone brings a different perspective, and working together helps us move faster and be more effective. It’s also a great way to keep learning—about the product, the process, and the people.

What excites you the most about your work?

What I love most is that no two days are the same. Every day brings a new challenge, a new question, or a conversation I’ve never had before and that constant learning is what keeps me sharp and motivated. It’s a role that pushes me to grow, think on my feet, and stay curious.

And then there’s the travel! At Camunda, I’ve had the chance to visit new places, attend local events and conferences, and meet partners and prospects face-to-face. It’s a great mix of professional growth and cultural discovery, and that’s something I really value.

Where are you currently based, and how has your experience been working with teammates in a fully remote setup?

I’m currently based in Noisy-le-Grand, just outside of Paris, only about 20 minutes from the city center by train. I’m originally from Italy and moved to France two years ago for my first job.

Even though we’re remote, I’ve never felt disconnected. There’s actually another ADR here in Paris, so we often co-work from a WeWork space and keep that team vibe going. What’s great about Camunda is that wherever you are in the world, chances are there’s another Camundi not too far away. We’re truly global.

And with daily huddles, constant messaging, and a culture of support, remote doesn’t mean isolated. If anything, it feels like we’re always just one Slack message away from each other.

What is a project or idea you’ve worked on at Camunda that you’re particularly proud of?

Over the past year at Camunda, I’ve grown a lot, both professionally and personally. One project I’m particularly proud of is an initiative I started to help ADRs better qualify OEM opportunities. It was part of my promotion path, but more important, it was something I genuinely believed could make a difference.

The goal is to increase the number of accepted SQOs from these kinds of leads so that ADRs can hit their targets more consistently. It’s still a work in progress, but it’s been really rewarding to take ownership of something that supports the whole team. I’m excited to see the impact it will have in the coming months.

What’s one piece of advice you’d share with someone considering an ADR role at Camunda—especially someone earlier in their career?

Start by mastering the basics: how to reach out, how to spark interest, and how to keep a prospect on the phone. These are the foundations of everything that comes next, especially if your goal is to grow into an AE role down the line.

Also, take the time to understand how your account executives work and what their goals are. Building a strong relationship with your AEs is key: your success is closely tied to theirs, and the better you collaborate, the more impact you’ll have together.

Can you share something about your personal life that colleagues might not know about you?

Not many people know this, but I’m a total history nerd. It’s a passion that stuck with me from my university days. Give me any historical topic, from ancient civilizations to obscure moments in European history, and I can easily go off on a 20-minute tangent. It’s my go-to fun fact and probably why I always end up winning at trivia nights!

The post Meet Belén, Joe, and Matteo from Camunda’s ADR Team appeared first on Camunda.

Most agent builders will wrap up those three requirements into a single, static, synchronous system, but at Camunda we decided not to do this. We found that it creates too many use case limitations, it’s not scalable and it’s hard to maintain. To overcome these limitations, we came up with a concept that lets us decouple these requirements and completely visualize an agent in a way that opens it up to far more use cases, not only on a technical level, but also in a way that  alleviates a lot of the fears that people have when adding AI agents as part of their core processes.

The value of a complete visualization

Getting insight into how an AI Agent has performed in a given task often requires someone to read through its chain of thought (this is like the AI’s private journal, where it details how it’s thinking about the problem). This will usually let you know what tools it decided to use and why. So in theory if you wanted to check on how your AI Agent was performing, you could read through it. In practice, this is just not practical for two reasons:
1. It limits the visibility of what happened to a text file that needs to be interpreted.
2. AI agents can sometimes lie in their chain of thought—so it might not even be accurate.

Our solution to this is to completely visualize the agent, its tools and its execution all in one place.

Gain full visibility into AI agent performance with BPMN

The diagram above shows a BPMN process that has implemented an AI agent. It’s in two distinct parts. The agent logic is contained within the AI Task Agent activity and the tools it has access to is displayed with an ad-hoc sub-process. This is a BPMN construct that allows for completely dynamic execution of the tasks within it.

With this approach the action of an agent is completely visible to the user in design time, during execution, and can even be used to evaluate how well the process performs with the addition of an agent.

The diagram above shows a headmap which shows which tools take the longest to run. This is something impossible to accurately measure with a more traditional AI agent building approach.

Decoupling tools from agent logic

This design completely decouples the agent logic from the available tool set. Meaning that the agent will find out only in runtime what tools are at its disposal. The ramifications of this are actually quite profound. It means that you can run multiple versions of the same process with the same agent, but a completely different tool set. This makes context reversing far easier and also lets us qualitatively evaluate the impact of adding or removing certain tools through AB testing.

Improving maintainability for your AI agents

The biggest impact of this decoupling in my opinion though is how it improves maintainability. Designers of the process can add or remove new tools without ever needing to change or update the AI agent. This is a fantastic way of separating responsibilities when a new process is being built. While AI experts can focus on ensuring the AI Task Agent is properly configured, developers can build the tooling independently. And of course, you can also just add pre-built tools for the agent to use.

Composable design

Choosing, as we did, to marry AI agent design with BPMN design means we’ve unlocked access for AI agent designers to all the BPMN patterns, best practices and functionality that Camunda has been building over the last 10 years or so. While there’s a lot you gain because of that, I want to focus on just one here: Composable architecture.

Composable orchestration is the key to operationalizing AI

Camunda is designed to be an end-to-end orchestrator to a diverse set of tools, rules, services and people. This means we have designed our engine and the tools around it so that there is no limitation on what can be integrated. It also means we want users to be able to switch out services and systems over time, as they become legacy or a better alternative is found.

This should be of particular interest to a developer of AI agents because it lets you not only switch out the tools the AI Agent has access to, but more importantly, it lets you switch out the agent’s own LLM for the latest and greatest. So to add or even just test out the behaviour of a new LLM no longer means building a new agent from scratch—just swap out the brain and keep the rest. This alone is going to lead to incredibly fast improvements and deployments to your agents, and help you make sure that a change is a meaningful and measurable one.

Conclusion

Building AI agents the default way that other tools offer right now leads you to adding a new black box to your system. One that is less maintainable and and far more opaque in execution than anything else you’ve ever integrated. This is going to make it hard to properly maintain and evaluate.

At Camunda we have managed to open up that black box in a way that integrates it directly into your processes as a first-class citizen. Your agent will immediately benefit from everything that BPMN does and become something that can grow with your process.

It’s important to understand that you’re still adding a completely dynamic aspect to your process, but this way you mitigate most concerns early on. For all these reasons, I can imagine that of all the many, many AI agents that are going to be built this year, I’m sure the only ones that will still be used by the end of next year will be built in Camunda with BPMN.

Try it out

All of this is available for you to try out in Camunda today. Learn more about how Camunda approaches agentic orchestration and get started now with a free trial here.

The post The Benefits of BPMN AI Agents appeared first on Camunda.