The question every SAP-centric team faces
You run S/4HANA and several SAP cloud applications. You also run dozens of non-SAP SaaS tools. Every new requirement raises the same question: where should this integration live? SAP sells you SAP BTP and SAP Integration Suite. The market also offers third-generation platforms such as Workato. Both connect SAP and non-SAP systems. They are not interchangeable.
The right choice depends on five things: the system of record, the type of work, who builds it, the volume, and your commercial strategy. This article sets out when each platform fits. It gives sample use cases. It proposes a placement decision tree and the architectural patterns that support it.
What each platform is
SAP BTP. SAP Business Technology Platform is SAP's platform for extension, data, AI, and integration. It groups several services under one commercial and technical roof. Integration sits inside it.
SAP Integration Suite. This is SAP's integration platform as a service. Many teams still call its core capability CPI, or Cloud Integration. The suite also includes API Management, Open Connectors, Integration Advisor, Trading Partner Management, Event Mesh and Advanced Event Mesh, and the Edge Integration Cell for on-premise and edge runtime. SAP ships prepackaged integration content for SAP-to-SAP scenarios. The Cloud Connector links on-premise SAP systems to the cloud without exposing them directly to the internet.
Workato. Workato is a third-generation iPaaS. It combines integration, workflow automation, API management, and, more recently, agentic orchestration. You build flows, called recipes, through a low-code interface. It ships more than 1,200 prebuilt connectors, including an SAP connector and an on-premise agent. Analysts placed it among the iPaaS leaders in 2025 and 2026. It serves both central IT and business technologists.
A note on iPaaS generations
First-generation integration ran on-premise as middleware and enterprise service buses. SAP Process Integration and Process Orchestration belong here. Second-generation iPaaS moved integration to the cloud and focused on connectors and integration flows. Third-generation platforms add business-process automation, human steps, citizen development, and agentic orchestration across mixed estates. SAP Integration Suite has added many of these capabilities. Its design and its economics still centre on SAP process integration.
When SAP Integration Suite is the right home
Use SAP Integration Suite when the system of record and the semantics are SAP, and the work is core process integration. The strongest fits are these:
Core SAP-to-SAP integration with SAP-shipped content. Scenarios such as S/4HANA with SuccessFactors, Ariba, Concur, or Fieldglass. SAP maintains this content and aligns it to the product roadmap while you run it unmodified. Unmodified SAP-to-SAP content also does not count against message-based billing, which lowers the cost of high-volume master-data and document flows.
SAP B2B and EDI. Trading-partner integration using Trading Partner Management and Integration Advisor for mapping guidelines and partner onboarding, tied to SAP document types.
SAP-specific protocols and patterns. IDoc, RFC, BAPI, OData, and master-data distribution, where native adapters and the Cloud Connector simplify access to on-premise SAP systems.
S/4HANA events and extensions. Event-driven flows from S/4HANA business events through SAP Event Mesh and Advanced Event Mesh, feeding extensions built with the Cloud Application Programming Model or on Kyma.
A central SAP integration team. Landscapes with developers skilled in Cloud Integration and Groovy, and a single SAP commercial relationship through a BTP Enterprise Agreement.
Be honest about the constraints. SAP Integration Suite charges per block of messages, and it bills every tenant, including development and test. High-volume chatty SaaS-to-SaaS traffic, or many small automations, can become expensive. Delivery usually needs specialist developers, which slows business-led change.
When a third-generation iPaaS like Workato is the better choice
Choose Workato when the majority of systems sit outside SAP, or when the work is business-process automation rather than system integration. The strongest fits are these:
Processes that span many SaaS applications. For example, lead-to-cash across a CRM, a billing system, an e-signature tool, and a collaboration platform, where SAP is only one touchpoint.
Workflows with human steps. Approvals, notifications, exception handling, and long-running orchestration across teams.
Business-led delivery. Work built and maintained by technologists outside the central integration team, where time-to-value matters more than SAP-certified content.
HR and IT operations automation. Joiner, mover, and leaver provisioning across an HR system, an identity provider, a service desk, and collaboration tools.
Agentic orchestration. AI agents and assistants acting across a mixed estate with human oversight.
Spiky or low-value workloads. Unpredictable volumes, and many small automations, where per-message and per-tenant SAP billing would be inefficient.
Be honest here too. Workato adds another strategic vendor and another platform to govern. It does not replace SAP's prepackaged content or SAP's support alignment for core process integration and certified B2B. Using it for S/4HANA master-data distribution or SAP-certified EDI usually means more build effort and a weaker support position. Connect to SAP through governed APIs rather than coupling to ERP internals.
Sample use cases and recommended placement
1. Employee and procurement master data
S/4HANA to SuccessFactors, Ariba, and Concur. Recommendation: SAP Integration Suite, on one condition. The advantage holds while you adopt SAP's content out of the box. The data and the semantics are SAP, support and roadmap align, and unmodified flows are not message-billed. Once you customise the mappings or logic, which is common, SAP stops maintaining that content and your integration team owns it, and the modified flows can start counting against message billing. Weigh that ongoing cost before you commit.
2. B2B order-to-cash with trading partners
EDIFACT and X12 with partners, plus IDoc inside SAP. Recommendation: SAP Integration Suite with Trading Partner Management and Integration Advisor. SAP provides mapping guidelines, partner management, and native handling tied to SAP documents.
3. Lead-to-cash automation across SaaS
Salesforce, a billing system, DocuSign, and Slack, creating the customer and the order in S/4HANA at the end. Recommendation: Workato, with the S/4HANA step through a governed API. The process is SaaS-centric, has human approvals and notifications, changes often, and benefits from fast business-led delivery.
4. Joiner, mover, and leaver provisioning
SuccessFactors or Workday, Entra ID, ServiceNow, and Google Workspace. Recommendation: Workato. This is cross-SaaS workflow automation with identity provisioning, tasks, and approvals. It needs no SAP-certified content.
5. S/4HANA events driving extensions and analytics
Recommendation: SAP BTP with Advanced Event Mesh and Integration Suite. The work uses native SAP eventing, S/4HANA business events, and SAP extension runtimes.
6. Finance close automation with AI assistance
Figures pulled from several SaaS tools and spreadsheets, with a few SAP calls and agentic assistance. Recommendation: Workato. The work is automation-heavy, covers many smaller systems, uses agents, and has limited SAP coupling.
7. Anti-patterns to avoid
Do not build chatty SaaS-to-SaaS micro-automations in Cloud Integration; message billing and specialist delivery make this slow and costly. Do not rebuild SAP-certified B2B or S/4HANA master-data distribution in Workato; you lose SAP content and support alignment and add effort. Do not run the same integration in both platforms with shared ownership; you get duplication and drift.
A placement decision tree
Apply these gates to each new requirement, in order. Stop at the first gate that fits. The diagram below shows the routing for a single flow. The numbered gates carry the full logic, including ownership, economics, and strategy.
- System of record and content. Is this a core SAP-to-SAP flow, does SAP ship supported prepackaged content for it, or is it core SAP process integration? If yes, and you will run that content unmodified, place it in SAP Integration Suite. If you must customise it, which is common, weigh the maintenance you take on, since SAP no longer maintains modified content and your team owns it.
- SAP B2B and master data. Does it need SAP-certified EDI, trading-partner management, or SAP master-data distribution? If yes, place it in SAP Integration Suite with Trading Partner Management and Integration Advisor.
- Systems and work type. Does the process span mostly non-SAP SaaS, or is it business-process automation with human steps, approvals, notifications, or long-running orchestration? If yes, place it in Workato.
- Ownership and skills. Will a central SAP integration team with Cloud Integration skills own it? That favours SAP Integration Suite. Will business technologists or a federated team build and maintain it for speed? That favours Workato.
- Volume and economics. Is it high-volume standard SAP-to-SAP content that is not message-billed? SAP Integration Suite is efficient. Is it many small, chatty, or spiky automations where per-message and per-tenant billing would inflate cost? Workato is more efficient.
- AI and agents. Do you need agentic orchestration across many SaaS systems with human oversight? Workato fits, unless the agents must sit close to SAP data and Joule, which favours SAP BTP.
- Commercial strategy. Do you want to consolidate on SAP, reduce the number of vendors, and accept SAP-shaped constraints and lock-in? Choose SAP Integration Suite. Do you want vendor-neutral SaaS orchestration that stays independent of the ERP lifecycle? Choose Workato.
Default. Most landscapes need both. Run SAP Integration Suite for core SAP integration, SAP-certified B2B, and S/4HANA events. Run Workato for SaaS automation, human workflows, and agentic orchestration. Connect them through published APIs and events.
Side-by-side comparison
This table summarises the trade-offs that drive the decision.
Supporting architectural patterns
Pattern 1. SAP core with an automation layer
SAP Integration Suite owns core ERP integration, SAP-to-SAP flows, and SAP B2B. Workato owns SaaS automation and business workflows. The boundary is a set of stable contracts: APIs published through SAP API Management, and events from SAP Advanced Event Mesh. Each flow has one home, so ownership is clear and the two platforms do not compete.
Pattern 2. Workato as orchestration hub, SAP as a governed gateway
Workato orchestrates cross-system processes. It calls SAP only through stable APIs that SAP API Management exposes over OData, SOAP, or RFC. This protects S/4HANA internals during upgrades and removes point-to-point coupling. The API contract becomes the unit of change control.
Pattern 3. Event-driven choreography
S/4HANA emits business events to SAP Advanced Event Mesh. SAP Integration Suite handles SAP-internal reactions. Workato subscribes for downstream SaaS reactions. This reduces synchronous coupling and lets each side scale on its own. It also makes new subscribers cheap to add.
Pattern 4. Domain-aligned placement
Assign integration by domain and system of record. The ERP, finance, and supply-chain domain goes to SAP Integration Suite. The CRM, HR, IT, and collaboration domain goes to Workato. Shared canonical contracts sit at the boundaries. Clear domain ownership reduces drift and duplicated flows.
Pattern 5. Anti-patterns to retire
Do not run chatty SaaS micro-automations in Cloud Integration. Do not rebuild SAP-certified B2B or master-data distribution in Workato. Do not let two platforms run the same integration with overlapping ownership. Each of these raises cost or risk without adding capability.
Make placement a decision, not a habit
Teams default to the platform they know. That is how cost and duplication creep in. Give one team, often an integration Centre of Excellence, ownership of the decision tree and the boundary contracts. Apply the tree at design time for every new flow.
Watch the economics on both sides. In SAP Integration Suite, track message consumption by tenant, since development and test tenants are billed and failed retries inflate the count. In Workato, track recipe and task usage and watch for connector sprawl. Review placement when volumes or ownership change.
What to take away
In an SAP-centric landscape, SAP Integration Suite earns its place as the platform for core SAP process integration, SAP-certified B2B, and S/4HANA events. Its standard-content advantage is real, but it holds only for out-of-the-box adoption; once you customise that content, maintenance and cost move to your team. A third-generation iPaaS such as Workato earns its place for SaaS-centric automation, human workflows, business-led delivery, and agentic orchestration.
The economics and the skills differ, so placement matters. Most organisations run both and define a clear boundary between them. Use the decision tree to place each flow once, in the platform that fits its system of record, work type, owner, volume, and strategy.
Sources and notes
Product capabilities and prices change. Confirm specifics with each vendor before you decide. The points below are paraphrased from the sources named.
SAP Integration Suite message-block pricing example, where standard unmodified SAP-to-SAP content is not counted, every tenant is billed, custom exits through ProcessDirect are counted, and Edge Integration Cell runtimes are billed at half: integration-excellence.com, published 2024.
SAP BTP consumption licensing, where the BTP Enterprise Agreement was introduced in 2024, uses prepaid credits, and carries a minimum annual commitment in the low five figures in some cases: redresscompliance.com and saplicensingexperts.com, 2025.
Workato connector count above 1,200, recipe-based delivery, on-premise agent, agentic features, and analyst positioning as an iPaaS leader in the Forrester Wave for the third quarter of 2025 and the Gartner Magic Quadrant for 2026: workato.com and novutech.com, 2025 to 2026.
SAP Integration Suite architecture, including the Cloud Connector and tenant separation: sap-press.com, 2025.