Should ServiceNow acquire Workato to compete in iPaaS in 2027?

What the iPaaS gap actually is and why it matters

ServiceNow sells workflow. Workflow only works when the systems on either side of it talk, and that is precisely where ServiceNow's own integration story thins out. IntegrationHub is genuinely good at what it was built for: pulling data into the Now Platform, pushing actions out of it, and wrapping both in flow templates and pre-built spokes so a ServiceNow admin never has to write a REST client by hand. It is a *ServiceNow-anchored* integration layer. That is a different product category from a general-purpose integration platform-as-a-service, and enterprise buyers know the difference even when vendors pretend they don't.

The distinction shows up in the shape of the question a customer asks. "How do we get Workday data into our ServiceNow HR case flow?" is an IntegrationHub question, and ServiceNow wins it comfortably. "What is our enterprise integration platform for the next five years?" is an iPaaS question, and in that room ServiceNow is not usually on the shortlist. MuleSoft, Boomi, and Workato are. That second question carries the larger budget, the longer contract, and — critically — the architectural authority. Whoever wins it becomes the connective tissue of the stack, and every downstream tool negotiates on their terms.

Workato is a credible answer to that second question. It is an enterprise iPaaS built cloud-native from inception, with a recipe-based, event-driven model rather than a hub-and-spoke one bolted to a single system of record. Public positioning and analyst coverage consistently place it in the enterprise integration leader set alongside MuleSoft and Boomi. Its connector library is roughly 1,000+ pre-built integrations against Salesforce, Workday, NetSuite, SAP, and the long tail of SaaS; IntegrationHub's spoke catalog is materially shallower once you leave the ServiceNow-adjacent orbit. Reported ARR sits in the low hundreds of millions with growth in the 30%-plus range, which is rare air for a private integration vendor in 2026 — most of that cohort decelerated hard after 2022.

Why this matters for RevOps specifically is worth stating plainly, because integration debates usually get framed as an IT-architecture problem and then everyone stops paying attention. Revenue operations lives or dies on data movement between CRM, CPQ, billing, marketing automation, product telemetry, and the data warehouse. Every broken sync is a forecast that's wrong, a territory assignment that's stale, a renewal alert that never fired. When ServiceNow tells a RevOps leader it wants to own the workflow layer for go-to-market, the immediate and fair objection is that ServiceNow does not own the pipes. Acquiring Workato is how that objection gets answered in one move instead of three years of roadmap slides.

There is also a defensive dimension. Microsoft has been steadily compressing the standalone integration category the same way it compressed standalone RPA — Power Automate and Logic Apps arrive bundled inside an E5 agreement that the customer already signed, and "good enough and free-ish" is a brutal competitor to "excellent and $400K." That compression is exactly why a best-in-class private iPaaS asset is more buyable now than it will be later, and also why waiting is not a neutral choice. The window where a category leader is both available and rationally priced is not permanent.

How the deal would actually get evaluated, step by step

Serious corporate development does not start with "should we buy Workato." It starts with a capability gap, tests whether that gap is worth closing, then tests whether buying is cheaper than building or partnering. Running the sequence honestly is what separates a disciplined acquisition from a narrative-driven one.

Step one — name the gap in customer language. Not "we lack iPaaS" but "we lose the enterprise integration platform decision in Global 2000 accounts where we already own the workflow layer." That framing is testable. Pull the last 200 competitive losses, tag which ones involved an integration platform evaluation, and measure how often ServiceNow was excluded from the shortlist entirely versus shortlisted and beaten. Exclusion is the more damning outcome, because it means the product isn't losing on features — it isn't considered a category participant.

Step two — size the addressable revenue, not the market. Total iPaaS TAM numbers from analyst firms are useful for a board slide and useless for a decision. The number that matters is the installed base overlap: how many existing ServiceNow enterprise accounts are running an integration platform ServiceNow does not sell, at what average contract value, renewing when. If the overlap between Workato's enterprise roster and ServiceNow's is meaningful — and public customer logos on both sides suggest substantial overlap across large enterprises — then a bundled renewal motion has a real, near-term revenue path rather than a speculative one.

Step three — build-versus-buy with an honest clock. ServiceNow could invest a few hundred million over 36 months to extend IntegrationHub toward general-purpose iPaaS. The problem is not money; it's that the competitive window closes inside that clock, and connector breadth plus a community recipe ecosystem are not things you can hire your way to quickly. Network effects in an integration marketplace compound in favor of whoever started earlier.

Step four — valuation bands with pre-committed walk-away. Set the bands before the banker calls, in writing, approved by the board. This is the single most-skipped step and the one that prevents the most damage.

Step five — integration design before signing, not after. Decide in advance whether Workato runs as a semi-independent business unit with its own GTM, or gets absorbed into the Now Platform sales motion. That decision drives the retention pool, the product roadmap, and whether the self-service funnel survives.

Step six — regulatory and partner-conflict review. An enterprise software deal in the multi-billion range draws antitrust attention in the US, EU, and UK. Additionally, Workato integrates deeply with vendors who compete with ServiceNow; some of those partnerships will cool the moment a ServiceNow logo goes on the door, and that churn needs to be modeled, not assumed away.

Costs, timelines, and the ranges that anchor the price

The comparable set for enterprise integration assets is small enough that everyone in the room already knows it, which is useful — it means the negotiation is a debate about adjustments, not about first principles.

Salesforce / MuleSoft, 2018, roughly $6.5B. This is the anchor comp and the most-cited one. MuleSoft was a public company with revenue in the low hundreds of millions, growing fast, and Salesforce paid a multiple that made sense in a zero-interest-rate environment where high-growth SaaS traded at premium revenue multiples. It also, notably, worked strategically — MuleSoft became a real product line rather than an orphan — while being widely regarded as expensive.

Boomi carve-out from Dell to Francisco Partners and TPG, 2021, around $4B. This established a floor: even a slower-growth iPaaS asset at scale clears $4B. It also established that private equity is a live bidder for these assets, which matters because it means ServiceNow would not be negotiating against a vacuum.

SAP / WalkMe, 2024, approximately $1.5B. Adjacent rather than direct — digital adoption, not integration — but it's a useful datapoint that even a sub-scale automation-adjacent asset cleared over a billion dollars in the current market. Tuck-ins are not cheap anymore.

IBM / Red Hat, 2019, $34B. Different category entirely, but instructive on one point: large infrastructure-software acquisitions require 24 to 36 months of integration patience before anyone can judge them. Boards that expect synergy in four quarters are the ones that panic and dismantle the thing they bought.

Applying those comps to Workato: reported ARR in the low-to-mid hundreds of millions with 30%-plus growth, against a last announced private valuation near $5.7B from the 2023 round. The 2023 mark was set in a different rate environment and late-stage secondary activity since then has generally priced private software below peak-era primary marks. That gives a realistic negotiating structure: a friendly floor somewhere around $4B–$4.5B where existing investors would seriously engage, a disciplined target zone of $5B–$5.5B, a stretch band of $5.5B–$7B that only works with structure, and a hard ceiling around $7B above which the deal fails any defensible multiple test in a 2026 market.

Structure matters as much as headline price in the stretch band. A deal at $6B with $1B in earnout tied to net revenue retention and self-service pipeline sustaining through year two is a very different risk profile than $6B all cash at close. Retention pools are a real line item — keeping a founder-led engineering organization intact through a two-to-three-year integration typically requires meaningful equity refresh on top of the purchase price, and that cost belongs in the model rather than as a post-close surprise.

Timeline expectations should be set the same way. Signing to close on a deal this size, with US, EU, and UK regulatory review, realistically runs six to twelve months. Product integration — shared identity, unified billing, a genuine story about where IntegrationHub ends and Workato begins — is an 18-to-24-month project minimum. Meaningful cross-sell attach against the overlapping installed base tracks renewal cycles, which means the second full fiscal year post-close is the first honest read on whether the thesis worked. Anyone promising faster is selling something.

Where acquirers get integration platform deals wrong

The failure modes here are well documented across enterprise software, and they repeat because the incentives that cause them are structural rather than accidental.

Paying for the narrative instead of the asset. When a strategic story is compelling enough — "we become the automation layer for the enterprise" — price discipline erodes. The narrative is usually correct; the price is what kills it. A great asset bought at a bad number is a bad deal, and the market prices that judgment into the acquirer's multiple almost immediately. Pre-committed walk-away numbers exist specifically to protect against a room full of smart people talking themselves past their own analysis.

Forcing a product-led motion through an enterprise sales overlay. This is the most reliably destructive mistake in the category. Workato's growth engine includes self-service onboarding, developer and citizen-integrator adoption, and a community recipe ecosystem — bottoms-up motion where individual practitioners adopt the tool and expansion follows usage. ServiceNow's motion is top-down: account executives, six-figure landing deals, long cycles, heavy professional services. Both are legitimate. They are not compatible when one is bolted onto the other. Routing self-service signups through an enterprise AE queue reliably strangles the funnel, because the friction that an AE adds is the entire thing the self-service user was avoiding. The correct answer is a semi-independent business unit that keeps its own funnel, its own pricing tiers, and its own developer relations, with a defined joint-selling motion at the enterprise tier only.

Under-funding retention and then acting surprised. Founder-led companies carry institutional knowledge in a small number of people. If the founder, the CTO, and the top handful of platform engineers leave in year one, the acquirer owns a codebase and a customer list but not the capability that made either valuable. Retention needs to be structured over the full integration horizon, not a one-year cliff, and it needs to include the layer below the executives.

Killing the partner ecosystem by accident. Integration platforms are Switzerland by design — they connect everything, including tools that compete with the acquirer. Once ServiceNow owns Workato, some vendors will quietly deprioritize the partnership, and some customers will worry about neutrality. Salesforce faced exactly this with MuleSoft. The mitigation is explicit, public commitments to platform neutrality plus continued investment in connectors for competitive systems, maintained long enough that the market believes it.

Letting the internal product become the political winner. The IntegrationHub team will, understandably, argue that they can close the gap. Post-close, unresolved overlap turns into two teams building toward the same target with neither one funded to win. The boundary needs to be drawn explicitly at signing: IntegrationHub owns Now Platform-anchored connectivity, Workato owns general-purpose enterprise integration, and shared runtime investment is jointly governed. Ambiguity here is the most common way a good acquisition rots.

Measuring the wrong thing in year one. Bookings synergy is the number executives reach for and the least informative. Better early indicators: does self-service signup volume hold, does Workato's net revenue retention stay flat or improve, does voluntary attrition among Workato engineers stay near pre-deal baseline, and does connector release velocity for non-ServiceNow systems continue. Those four tell you whether the asset is intact. Revenue synergy tells you whether the sales org got a new SKU.

Decision framework: buy, build, partner, or pick a different target

The choice is not binary, and the alternatives deserve real evaluation rather than being staged as strawmen next to the preferred answer.

Acquiring Workato at $4.5B–$5.5B is the strongest outcome available. Best-in-class asset, real category credibility, aligned AI-agent roadmap direction, substantial account overlap for a near-term bundled renewal motion, and a price defensible against the MuleSoft and Boomi comps. Execute with a semi-independent business unit and funded retention.

Acquiring at $5.5B–$7B works only with structure — meaningful earnout tied to retention and self-service health, plus a retention pool sized honestly. Without structure, this band starts eroding the return before integration even begins.

Above $7B: walk. No adjustment to the comps supports it. The deal would be paying peak-cycle multiples in a market that repriced years ago.

Building IntegrationHub into a full iPaaS is already underway and is a reasonable ongoing investment regardless of what happens on M&A. As a *substitute* for acquisition it fails on clock speed: connector breadth and marketplace network effects take years, and the competitive window is shorter than that. As a *complement* it's fine — the Now Platform-anchored use case is real and worth serving well.

Partnering with Workato without acquiring is the correct interim position and a genuinely acceptable permanent one. Joint go-to-market, deep certified connectors, co-selling into overlapping enterprise accounts. It captures a real share of the customer value at a fraction of the risk, and it keeps the option open. The cost is that ServiceNow never owns the integration layer, which means it never gets the architectural authority that comes with it.

Alternative targets deserve honest treatment. MuleSoft has been inside Salesforce since 2018 and is not realistically available. Boomi sits under private equity ownership with an IPO or strategic-sale path, but its growth profile is more modest and its brand less differentiated on the AI-native axis. Smaller integration vendors would be feature acquisitions rather than category acquisitions — they close a product gap without closing the credibility gap, which is the actual problem. A mid-market target at a lower price point is the cheaper option, not the better one, and buying cheap to avoid buying right is how companies end up doing two deals instead of one.

The adjacent scenario worth naming: if ServiceNow passes and Microsoft, Salesforce, IBM, or a large private equity firm takes Workato instead, ServiceNow's position gets worse, not merely unchanged. A Microsoft-owned Workato accelerates the bundling pressure. A Salesforce-owned one consolidates the integration category under a direct competitor in go-to-market workflow. That asymmetry is a legitimate input to the price band — though it's also exactly the argument that talks acquirers past their ceiling, so it belongs in the analysis with a clear label on it.

What this means downstream for RevOps and the wider automation stack

Whatever ServiceNow decides, the second-order effects land on operations teams, and those are worth thinking through independently of the deal itself.

If the acquisition happens, integration procurement consolidates. RevOps teams currently running Workato alongside ServiceNow would find both arriving on one paper contract, which is genuinely good for negotiating leverage in the first renewal and genuinely bad in the third, once the alternative has been decommissioned. The practical hedge is to keep integration logic portable: define recipes and flows around documented APIs and event contracts rather than vendor-specific conveniences, and keep an inventory of which business processes would be hardest to move. That inventory is the actual source of negotiating power.

If it doesn't happen, the status quo persists a while longer — a workflow layer and an integration layer sold separately, with the seams owned by whoever operates them. That's more vendors to manage and more contracts to negotiate, but it also preserves genuine competition, which tends to keep both roadmaps honest.

The broader pattern to watch is convergence between workflow orchestration, integration, and AI agents. Agentic automation only functions when an agent can actually reach systems, authenticate, read state, and take action — which is an integration problem wearing new clothes. Every major automation vendor has arrived at the same conclusion from a different starting point: ServiceNow from workflow, Workato from integration, Microsoft from productivity and cloud, Salesforce from CRM. The consolidation logic in this deal is the same logic driving the whole category, which is why a version of this question applies to nearly every vendor pair in the space, not just this one.

For a RevOps leader reading this while evaluating their own stack, the operational takeaway is straightforward. Do not architect around a merger that may not happen. Build integration on documented contracts, keep credentials and connection logic in one governed place rather than scattered across teams, instrument the syncs that feed forecasting and territory logic so failures surface as alerts rather than as a bad number in a QBR, and know your switching cost per critical process before your renewal conversation rather than during it. Those practices pay off whether or not ServiceNow ever writes the check.

Related questions

Does ServiceNow need iPaaS to sell AI agents?

Practically, yes. Agents need authenticated access to systems of record to take real action. IntegrationHub covers Now Platform-anchored paths; a general-purpose integration layer covers everything else. Without one, agentic use cases stall at the boundary of ServiceNow's own data.

Why not just extend IntegrationHub instead?

Money isn't the constraint — time is. Connector breadth across the SaaS long tail and a community recipe marketplace compound over years. A 36-month build lands after the competitive window closes, though continued IntegrationHub investment still makes sense for ServiceNow-anchored workflows.

What would a partnership look like instead of an acquisition?

Certified deep connectors both directions, joint go-to-market into overlapping enterprise accounts, co-selling compensation for both field organizations, and shared reference architectures. Lower risk, lower reward, preserves optionality — and it's the sensible interim posture while any acquisition case is being tested.

How would this affect existing Workato customers?

Short term, very little — contracts and roadmaps continue. Medium term, the risks are neutrality perception among customers using competing workflow tools, and pricing changes at renewal. Watch whether self-service tiers and non-ServiceNow connector velocity are maintained; those are the health signals.

Is antitrust a realistic blocker?

Review is certain at this deal size across US, EU, and UK regulators, but a workflow vendor buying an integration vendor is adjacent-market rather than horizontal consolidation. The likelier friction is timeline — six to twelve months to close — rather than outright prohibition.

FAQ

What is Workato and why would ServiceNow want it?

Workato is an enterprise integration platform-as-a-service built around low-code recipes and event-driven automation, with a connector library reported at over 1,000 pre-built integrations. ServiceNow's IntegrationHub handles Now Platform-anchored connectivity well but isn't positioned as a standalone enterprise integration platform. Acquiring Workato would close that category gap immediately rather than over a multi-year build.

What price range would actually make sense?

Anchored on Salesforce paying roughly $6.5B for MuleSoft in 2018 and the Boomi carve-out at around $4B in 2021, plus Workato's reported ~$5.7B private valuation from 2023 in a higher-multiple environment, a disciplined band lands near $4.5B–$5.5B. Between $5.5B and $7B, only with earnout structure. Above $7B, walk.

Would this help ServiceNow compete with Microsoft?

It would help ServiceNow compete in the integration category generally, Microsoft included. Power Automate and Logic Apps arrive bundled inside agreements enterprises already hold, which compresses standalone integration pricing. Owning a differentiated best-in-class platform is a stronger defense than extending a hub-and-spoke tool that wasn't designed for that fight.

What is the single biggest execution risk?

Culture and motion mismatch. Workato grows partly through self-service adoption and a developer community; ServiceNow sells top-down with account executives and long cycles. Routing a bottoms-up funnel through an enterprise sales overlay reliably damages it. Running Workato as a semi-independent unit with its own funnel and pricing is the mitigation.

Should a RevOps team change anything based on this speculation?

No — architect for portability regardless. Build integrations against documented APIs rather than vendor-specific shortcuts, centralize credentials and connection governance, alert on sync failures that feed forecasting and territory data, and document switching cost per critical process before renewal. Those hold up under any ownership outcome.

What happens if a competitor acquires Workato first?

ServiceNow's position worsens rather than staying flat. A Microsoft acquisition accelerates bundling pressure; a Salesforce acquisition consolidates integration under a direct workflow competitor. That asymmetry is a legitimate input to the valuation band — but it's also the exact argument that pushes acquirers past their ceiling, so it should be weighed explicitly, not absorbed into enthusiasm.

Sources

• https://www.gartner.com/en/documents/topics/integration-platform-as-a-service — Gartner research coverage of the iPaaS category and vendor evaluations
• https://www.forrester.com/research/ — Forrester research on enterprise integration and automation platforms
• https://investors.servicenow.com/ — ServiceNow Investor Relations: filings, earnings materials, and strategy commentary
• https://www.workato.com/ — Workato product documentation, connector library, and customer case studies
• https://www.salesforce.com/news/press-releases/2018/03/20/salesforce-signs-definitive-agreement-to-acquire-mulesoft/ — Salesforce press release announcing the MuleSoft acquisition
• https://boomi.com/ — Boomi platform positioning and company information following the Dell carve-out
• https://www.idc.com/ — IDC market sizing and forecasts for integration and automation software
• https://learn.microsoft.com/en-us/power-automate/ — Microsoft Power Automate documentation, relevant to bundled-automation competitive pressure
• https://news.sap.com/2024/06/sap-to-acquire-walkme/ — SAP announcement of the WalkMe acquisition, an adjacent automation comp
• https://www.reuters.com/technology/ — Reuters technology coverage of enterprise software M&A

Related on PULSE

• Should ServiceNow acquire Workato in 2027?
• What is Workato and why is it a hot RevOps integration and automation platform for 2027?
• Workato vs 11x — which should you buy?
• How does Workato defend against Okta in 2027?
• Is a Workato Sales Engineer role still good for my career in 2027?
• How'd you fix Workato's revenue issues in 2026?