What’s New in WSO2 Integrator 5.1
- Anupama Pathirage
- Director & Head of Product Management - Integration, WSO2
Earlier this year, WSO2 Integrator 5.0 brought our integration technologies together into a single product and made AI a more central part of how developers build integrations.
WSO2 Integrator 5.1 builds on that foundation with AI as the primary integration development experience. WSO2 Integrator 5.1 expands support for building more capable enterprise AI agents, and introduces first-class workflow integration support, which brings long-running business processes into the same development environment. The release also strengthens observability and operations across cloud and self-managed deployments, and enhances event, file, and enterprise connectivity.
Here are the major additions in this release.
AI-native integration development
Integration development usually starts by translating a requirement into implementation: choosing the right triggers and connectors, constructing a flow, configuring each component, mapping data, and then testing the result.
With WSO2 Integrator 5.1, developers can start with the requirement itself.
WSO2 Integrator Copilot can take an integration requirement expressed in natural language and generate a complete integration flow. The generated flow can then be inspected visually, refined with AI assistance, or edited directly through the underlying code.
This doesn't remove the precision required for integration development. APIs still have contracts, data needs to be mapped correctly, authentication must be configured, and failures need to be handled. Instead, it changes the starting point: describe the intent, generate a concrete implementation, inspect it, and refine it.
Copilot is also more extensible in this release. Developers can configure Model Context Protocol (MCP) servers at user or project scope, manage reusable skills, and customize AI behavior through a unified configuration experience that brings together MCP servers, skills, and agent instructions. The range of supported AI services expands as well, with support for GPT-5, AWS Bedrock, and Google Gemini models and embedding providers.
Learn more about the Copilot capabilities here.
Expanded AI agent capabilities
There is a significant difference between an agent that can answer a question or invoke a tool, and one that can reliably participate in an enterprise process. An agent investigating a claim, handling an operational incident, or processing an order may need to retrieve enterprise information, call multiple tools, retain context, involve a person in a decision, and continue based on that decision.
WSO2 Integrator 5.1 expands its agent capabilities for these types of scenarios. Persistent memory providers allow agents to retain context beyond an individual interaction, while reusable agent composition makes it possible to build larger solutions from multiple agents. Parallel tool execution allows independent tool calls to run concurrently, and human-in-the-loop interactions provide a way to involve people when a decision should not be fully automated.
The ways agents can interact with their environment are expanding as well. Event-driven triggers allow agents to respond to events and participate in event-driven processes rather than relying only on conversational interactions. Voice-enabled agents provide another way for people to interact with them.
There are also improvements aimed at making agent-based solutions easier to validate and refine. Evaluation templates help teams assess agent behavior more systematically. Retrieval-augmented generation (RAG) adds more enterprise data loaders, while retrieval capabilities within ingestion pipelines make it easier to verify what can actually be retrieved and troubleshoot issues before they surface in the final integration.
Learn more about AI agents here.
Long-running workflows
Many business processes don't complete within a single request. An order may need approval. A claim may wait for supporting documents. An onboarding process may need to pause until another system responds. An operation may fail temporarily and need to be retried later. These processes need to preserve their progress while they wait and continue when the required event occurs.
WSO2 Integrator 5.1 introduces first-class workflow support for orchestrating these long-running processes. Long-running workflows can pause and maintain durability while waiting for human interaction, timers, or external data, and then resume execution. The workflow engine also provides retry handling and activities for integrating with external systems.
Separately, workflow management and monitoring capabilities provide visibility into workflow instances, execution status, and failures. A dedicated user portal complements these capabilities by giving business users a place to view and complete human tasks assigned to them.
This gives integration developers another execution model alongside traditional integration flows: one designed specifically for processes that may need to wait and resume over an extended period.
Learn more about long-running workflows here.
Durable agents
WSO2 Integrator 5.1 also brings agents and long-running workflows together. A traditional workflow follows a path defined during development. But there are processes where the overall goal is known while the best sequence of actions may depend on information discovered at runtime.
With a durable agentic workflow, the goal can be described in natural language at development time and an AI agent determines the appropriate path at runtime. Like a durable workflow, the agent can save progress, maintain state while waiting for external events, and resume execution later.
This combines the runtime decision-making of an AI agent with the ability of a durable workflow to reliably execute a long-running process.
Learn more about durable agents here.
Observability across cloud and self-managed deployments
Once integrations are running, teams need to understand whether they are healthy, investigate failures, and trace what happened across a flow. That becomes increasingly important as integration environments include APIs, events, workflows, and AI agents.
WSO2 Integrator 5.1 introduces a more consistent observability experience across cloud and self-managed deployments. Moesif is introduced as the default observability platform for metrics, logs, and traces, providing consistent visibility across Integration Cloud and Integration Control Plane.
Additionally, organizations that already have an observability platform are not limited to the default. Expanded OpenTelemetry support includes generic OTLP exporters for traces, metrics, and logs, allowing telemetry to be sent to compatible observability platforms already in use within the organization.
Integration Cloud and Integration Control Plane
WSO2 Integrator 5.1 extends the platform experience beyond integration developers. Integration Cloud introduces a new User Portal for integration consumers to trigger automations, complete approval tasks, monitor execution, and review automation history without having to work within the developer environment.
AI assistance is extended across the cloud experience as well, helping users discover integrations, generate solutions, troubleshoot failures, and understand platform capabilities using natural language.
For teams exposing existing enterprise capabilities to AI agents, Integration Cloud provides an integrated MCP Inspector, REST-to-MCP conversion, and MCP component generation. These capabilities make it easier to take services that already exist and make them available as tools for AI agents to consume via MCP.
Integration Control Plane continues to align the self-managed operational experience with Integration Cloud. This release adds enhanced automation visibility, service monitoring, AI-assisted operations, and observability, together with federated authorization for enterprise identity providers, single sign-on, and role-based access control. A dedicated User Portal is also available for self-managed deployments, giving business users a similar way to interact with integrations across both deployment models.
Event, file, and enterprise connectivity
Alongside the AI and workflow additions, this release continues to expand the core integration capabilities needed to connect enterprise systems.
For event-driven integration, the release adds support for Solace SMF events and Oracle Change Data Capture (CDC). It also introduces SAP JCo listeners, enabling integrations to receive IDocs and inbound RFC calls from SAP systems such as SAP ECC. OpenTelemetry tracing for event-driven applications has also been improved, providing better visibility into asynchronous integration flows.
This release also brings several improvements to file integration. FreeMarker template processing can be used to generate HTML, email content, configuration files, and other text-based artifacts. The EDI library improves parsing of large and complex EDI documents, while connector enhancements expand support for SMB, SharePoint, Azure Storage, and AWS S3, together with streaming XLSX processing.
The connector ecosystem also expands with Microsoft Dynamics 365 Finance & Operations, additional SAP connectors, Redis enhancements, and a shared AWS authentication library. The shared authentication library reduces the need to implement the same AWS authentication capabilities independently across AWS connectors.
Additional improvements in WSO2 Integrator: MI 4.7
This release also includes WSO2 Integrator: MI 4.7, with improvements across runtime operations, developer productivity, AI-assisted development, and connectivity.
Runtime improvements include Brotli compression support, improved cluster visibility, cloud-native configuration management, AWS Secrets Manager integration, and priority-based Composite Application deployment.
Developer productivity improvements include Data Services Try-It support, an enhanced Data Service Call Mediator, Workspace Overview, and simplified dependency management.
AI-assisted development is also more adaptable to enterprise development practices. Organizations can define custom AI instructions and reusable skills so that Copilot recommendations better reflect their own standards and practices.
Connectivity expands with new connectors for Solace, Azure Service Bus, and PGP, while Amazon S3 support is enhanced with streaming to support more efficient processing of large files.
Get started with WSO2 Integrator 5.1
WSO2 Integrator 5.1 is available today.
Explore the complete set of changes in the WSO2 Integrator 5.1 release notes, download WSO2 Integrator 5.1 to get started locally, or try WSO2 Integration Cloud to build and run integrations as a managed service.