Workato ONE — When Your Integration Platform Starts Thinking, Every Stack Needs a Rethink

iPaaS has been quietly eaten by AI this year, and Workato ONE is the first product to really show what the end state looks like. Gartner named Workato a Magic Quadrant Leader for iPaaS for the eighth year running — a fact that would be unremarkable except that the category itself has shifted underneath them. "Integration platform as a service" is no longer shaped around connectors and recipes. It's shaped around agents that reason across the connectors and orchestrate the recipes on your behalf.

Workato ONE is the bet that the integration layer and the agent layer converge into a single product, and whoever ships that first owns a lot of the enterprise AI stack.

What Workato ONE actually is

Workato ONE combines three things that traditionally sat in different products:

• Integration. 600K+ pre-built connectors and recipes across Salesforce, SAP, ServiceNow, Workday, and essentially every enterprise SaaS you've heard of.
• Orchestration. The Process Composer handles cross-system multi-agent workflows, giving agents structured hand-offs rather than ad-hoc glue.
• Agent development. Prompt-to-Automate lets users build bots from natural-language instructions, with AI-powered data mapping and error resolution built in.

All three run on the same fabric, which is the point. Pricing from $833/month (paid, no free tier beyond evaluation) signals the positioning: this is enterprise software for teams that were already Workato customers or were going to be.

Why the category is converging

For most of the last decade, iPaaS (Workato, Mulesoft, Boomi) and automation tools (Zapier, Make) sat in different buckets from AI platforms. iPaaS connected SAP to Salesforce. Automation tools wired Slack to a spreadsheet. The AI platform was a separate thing you bought from OpenAI or Anthropic.

That separation doesn't survive contact with agents. If you want an agent that processes a vendor invoice, routes approval through finance, updates the procurement system, and notifies the buyer on Slack, you need three things the agent platform can't provide alone: connectors to the systems, structured workflows for the hand-offs, and a permissioning model that knows who can approve what.

Workato already had the connectors and the workflows. The agent layer is the last piece. Ship that and you don't just have an iPaaS with AI features — you have the default place enterprises put agentic work.

What Prompt-to-Automate actually does

This is the flagship capability and deserves a closer look. You describe a process in natural language: "When a new lead lands in Salesforce with deal size over £50K, pull their company details from LinkedIn, check their ESG score in our compliance system, summarise and post to the deal's Slack channel." Workato generates the recipe — including the API calls, the data transformations, the error handling — and surfaces it for review.

The generated recipe is editable, auditable, version-controlled. It's not a black box. That matters because the objection to agent-generated automation has always been "how do I know what it's going to do when I run it?" Workato's answer: you read the recipe, same as any other Workato recipe, and sign off.

How it compares

Against Mulesoft (Salesforce). Workato is stronger on AI-native automation. Mulesoft is stronger on hardcore API management at huge scale and more deeply integrated with Salesforce's broader product line. If you're already Salesforce-heavy, Mulesoft is the default; multi-vendor shop, Workato.

Against Zapier Enterprise. Different weight class. Zapier is great for small-team workflows; Workato is built for thousands of users, complex permissioning, and enterprise compliance.

Against n8n + a separate AI platform. n8n gives you control and lower cost; Workato gives you less engineering work. For teams with a strong integration engineering function, n8n is viable; for teams without, Workato is cheaper in practice.

Against Dust or other agent-platform-first products. Dust starts with "connect an agent to your company's data." Workato starts with "your company's integrations already run through Workato — now let agents drive them." If you're already a Workato shop, ONE is the clear upgrade path. If you're not, the value is less obvious.

Where the caveats live

Price floor is high. $833/month is not a trial amount. Budgeted enterprise purchase with procurement involvement.

Lock-in is real. Deep Workato adoption means deep Workato adoption. Recipes, connectors, and now agent workflows all live in their fabric. Escaping is possible but expensive.

Prompt-to-Automate is not yet magic. The generated recipes are serviceable but benefit from human review. Teams expecting to describe a process and get production-ready automation in one pass will be mildly disappointed. Teams expecting 70% of the way and 30% cleanup will be happy.

Who should actually care

Existing Workato customers. The upgrade case is immediate. Agent workflows on the platform you already run is the cleanest expansion path available.

Large enterprise IT and operations. If your company has 500+ SaaS apps and you're trying to figure out where agents live in your stack, Workato ONE is a credible "put them here" answer.

Finance, HR, procurement, and CX ops teams. These are the functions where "agent that coordinates across five systems" is the most obvious fit, and where Workato's connector library has the deepest reach.

Not recommended for: small teams, single-system shops, or anyone looking for a free/freemium route. Workato is priced for where the ROI is — at scale.

The signal

iPaaS vendors and agent-platform vendors are both reaching for each other. Expect every major iPaaS provider to ship an agent story in the next year, and expect every agent platform to expand its connector catalogue. The convergence is already visible; Workato ONE is just the clearest expression of it from the iPaaS side.

The long-term question is whether a specialised agent platform (like Dust) or an integration-first platform (like Workato) wins the "place you put enterprise agents" land grab. Our guess: enterprises will use both, with Workato winning the workflows that touch operational systems of record and specialised agent platforms winning the knowledge-worker assistants.

If you're evaluating where to put enterprise agents: Workato ONE on our marketplace has the specifics, and the Operations & Automation category is where we track the alternatives — Dust, n8n, Zapier — worth benchmarking against it before committing.