October 2026 Release: SAP integration, now AI-ready
The October 2026 release of the ASAPIO Integration Add-on brings AI-agent control over your integration configuration, native no-code automation via n8n, and faster, more resilient streaming to Kafka, Confluent, Solace and Advanced Event Mesh.
- Release
- 9.32610
- Published
- 7 October 2026
- Download
- Download Portal (licensed customers)
- What changed
- Full changelog
- Install
- Installation & upgrade
Event Studio is now AI-enabled
Two new capabilities bring AI directly into Event Studio:
Event Studio MCP Server (BTP Edition) – runs on SAP BTP and connects to your SAP system, with separate reader and writer role collections, giving MCP-capable AI assistants such as Claude access to interface configuration and monitoring via the Model Context Protocol (MCP), an open standard for connecting AI assistants to business systems. Describe what you need in plain language, and the assistant calls the tools, applies the change and reports back, with the same governance and traceability as manual changes.
AI Assistant sidebar – Event Studio's in-app assistant can now use SAP AI Core or a bring-your-own LLM, so the underlying model fits your landscape and governance requirements.
Illustrative example of an MCP Server conversation – not a real product screenshot.
Dynamic topic builder
Topics are now easier to build: compose the outbound topic from segments directly in Event Studio's Create Interface or Deployment screen – a fixed value, a field from the SAP document, or the result of a conversion class/method – instead of a fixed string. Available for Solace and Advanced Event Mesh connections. See the Event Studio docs.
Undeployment
Interfaces can now be undeployed directly from Event Studio's deployment page, right next to Deploy – no manual backend step needed to take an interface out of service.
Custom Namespace
Create CDS payloads and other Event Studio objects in your own custom namespace instead of being limited to ASAPIO's reserved one – fitting your team's existing naming conventions. Added based on customer feedback.
Packed Load settings & new Monitoring filters
Configure packed-load settings directly in Event Studio, without a separate backend step. The Monitoring screen also gets additional filters, including by connection instance, object and status code, to narrow down large result sets faster.
Trigger n8n workflows directly from SAP events
A new community node lets n8n workflows react to events dispatched from SAP in real time: the ASAPIO Event Trigger node receives them over a standard REST connection as a signed webhook, so there's no custom HTTP setup on the n8n side to get started. Requires ASAPIO Integration Add-on Release 9.32610 or higher with the REST Connector – not available in the SAP OEM editions. Built for teams who automate processes in n8n but aren't SAP integration specialists.
Every event is signed: the node verifies an HMAC-SHA256 signature that ASAPIO attaches to each dispatched event, using a shared secret configured as the Signing Secret on both sides, plus a timestamp check to guard against replayed requests. An optional "Reject Invalid Signatures" setting can hard-block invalid or stale events with an HTTP 401, instead of just flagging them in the workflow output.
View the package on npm → · Read the full n8n connector docs →
Browse every RAP event before you install anything
Event handler classes for all available RAP events are now published on our Content Catalog – install only the Event Handler classes you actually need, package by package, domain by domain.
ASAPIO is also publishing the matching payload definitions – built on standard SAP CDS views – to the SAP Business Accelerator Hub, so prospects and customers can inspect exactly what an event payload looks like before installing the ASAPIO Integration Add-on.
Faster, more resilient streaming – and better handling of large data volumes
Alongside more than 20 quality improvements and new features across the product, this release focuses on streaming connectivity and performance at scale. Every change is listed in the changelog.
Kafka & Confluent connectivity
-
Connect to Kafka directly, no REST Proxy in the loop
Talks to Kafka brokers over the native protocol instead of going through a REST Proxy layer.
Native Kafka protocol -
Multi-partition topics via bootstrap-server discovery
The connectivity model Confluent Cloud and most multi-broker Kafka clusters require.
Native Kafka protocol -
Apache Avro schema support
A new format function serializes outbound messages against a schema registered in the Confluent Schema Registry. We support Avro JSON serialization encoding (not Avro binary).
Confluent REST Proxy -
Outbound only for now, no inbound (Sink) yet
Applies to both connectors in this release – inbound Kafka support is planned for early 2027.
Native Kafka protocolConfluent Cloud V3 API
Faster Solace & Advanced Event Mesh messaging
AMQP performance work for the Solace and Advanced Event Mesh connectors: support for multiple concurrent connections for more throughput, and more robust initial loads. See the Solace and Advanced Event Mesh connector docs.
Better large-data-volume handling
Performance optimizations for packed loads and large data handling – including Microsoft Fabric scenarios – plus a higher thread-count ceiling for the Max Threads feature, with thread counting itself corrected to remove a prior performance loss.
Correlation IDs, user properties & partitioned queues
Map payload fields to correlation IDs, message IDs and custom user properties on outbound Solace and Advanced Event Mesh messages, and route same-document messages to the same partition via JMSXGroupID – comparable to Kafka key-based partitioning, for ordering and higher throughput. Available for REST-based connectivity. See the Solace and Advanced Event Mesh connector docs.
Solace Event Portal integration
Publish schemas, topics and queues from the SAP backend to Solace Event Portal via the Solace API, for stronger discoverability of your events. See the Event Portal integration docs.
Interfaces discoverable in SAP Developer Hub
Interfaces published through our existing Event Portal integration for Advanced Event Mesh connections also become discoverable in SAP Developer Hub, once your Advanced Event Mesh instance is connected there as an event source.