While Joule is deeply embedded across SAP cloud solutions, many customers operate in heterogeneous landscapes that include non‑SAP applications. Extending Joule into these environments is a key part of SAP’s strategy to deliver a unified AI experience across the entire digital workplace, not just within SAP systems.
Core Principle: Joule Is Extended, Not Embedded, in Non‑SAP Apps
A critical distinction for implementation consultants is that:
- Joule is natively embedded only in SAP applications that explicitly support it.
- Joule is extended to non‑SAP environments through experience and orchestration layers, not by direct embedding or exposed public APIs.
SAP does not currently provide a general‑purpose API that allows third‑party applications to call Joule directly as a standalone AI service. Instead, SAP supports extension patterns that keep Joule anchored to SAP BTP, SAP identity, and SAP governance models.
Supported Approaches for Non-SAP Integration
SAP supports two primary approaches for extending Joule into non‑SAP environments.
Approach 1: Joule Studio for SAP and Non-SAP System Integration
Joule Studio, part of SAP Build, is the primary extensibility mechanism for integrating Joule with both SAP and non‑SAP systems.
Using Joule Studio, organizations can:
- Extend Joule skills that call APIs of non-SAP systems
- Create custom Joule Agents that orchestrate workflows across SAP and non-SAP applications
- Leverage Pro-Code Development Tools for Joule, like Joule Studio CLI to build, compile and deploy capabilities for Joule
- Ground Joule responses in data retrieved from external systems
- Maintain centralized lifecycle management, security, and governance
Joule Studio does not expose Joule externally. Instead, it allows Joule to invoke external systems securely from within SAP BTP using approved integration mechanisms such as destinations and action projects.
Key Architectural Point:
Joule remains on the conversational interface, while non-SAP systems act as back-end data or action providers.
Approach 2: WalkMe and the Joule Action Bar for Cross Application AI
SAP’s acquisition and integration of WalkMe enables Joule to operate across SAP and non‑SAP web applications through the Joule Action Bar.
The Joule Action Bar:
- Provides an omnipresent AI overlay available across SAP and non‑SAP web applications
- Uses screen level context to determine user intent
- Delivers proactive assistance, summaries, and recommendations
- Preserves SAP security and identity by routing Joule interactions through SAP managed services
This approach does not embed Joule into non‑SAP applications at the code level. Instead, it delivers a consistent AI experience in the flow of work, regardless of which application the user is currently using.
What is Not Supported
To avoid common misconceptions:
- Joule is not exposed as a public REST API for arbitrary third‑party consumption
- Non‑SAP applications cannot host Joule natively
- Direct LLM access to Joule is not supported outside SAP‑managed contexts
- Identity and authorization are never delegated to non‑SAP systems
When to Use Each Approach
| Scenario | Recommended Approach |
|---|---|
| Integrating APIs of non‑SAP systems | Joule Studio |
| Cross system workflow orchestration | Joule Studio (Agents) |
| AI assistance across multiple web apps | WalkMe + Joule Action Bar |
| Unified experience without embedding | WalkMe |
| Backend automation and data retrieval | Joule Studio Skills |
Key References
SAP Architecture Center – Extend Joule with Joule Studio
Explains how Joule Studio supports integration across SAP and non-SAP systems
SAP Discovery Center Mission – Build Custom Joule Skills for SAP and Non-SAP Systems
Hands-on guidance for extending Joule using SAP Build and Joule Studio
WalkMe Action Bar with SAP Joule
Describes how Joule delivers AI assistance across SAP and non-SAP applications