Explainer

Workato explained: recipes, credits and where business led automation stops

Workato sells itself as an automation platform for the whole business rather than an integration tool for IT. This explainer covers how recipes and connectors work, how the usage based pricing is metered, where the governance risks sit and who should be looking at it.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

What Workato is and who is behind it

Workato was founded in 2013 and is headquartered in Mountain View, California. It is privately held, with investors including ServiceNow, Altimeter Capital, Insight Partners and Redpoint Ventures, and its Series E round in November 2021 raised more than 200 million US dollars at a valuation of 5.7 billion US dollars. It opened Dublin and Singapore offices in 2021, and in 2025 bought DeepConverse, a support automation company, and the AI company XMAD.ai.

The product began as an integration and automation tool that non developers could use, and that remains the pitch: one platform where IT and business teams build automations from recipes, with more than 1,200 prebuilt connectors included for every user and no limit on workspaces or users. In 2026 the editions are Standard, Business MCP, Enterprise MCP and Workato ONE, the MCP in the names signalling how hard Workato is leaning into connecting AI agents to enterprise applications.

Be precise about what Workato is not. It is not an ERP data migration tool. It is not a master data hub in the Boomi sense, although a Data Hub add on from Reltio is listed. It is not a managed EDI service, although an EDI add on from Orderful is. It is a platform for automating processes across SaaS applications, with integration as the means rather than the end.

Recipes, connectors and how a Workato automation is built

Everything in Workato is a recipe: a trigger followed by a sequence of action steps, built in a browser from connector operations, conditions, loops and data mappings. A trigger might be an opportunity closed in the CRM, a row landing in a database, a webhook, a schedule or a message to a Workbot in Slack or Teams. The actions then create the customer in the ERP, raise the invoice, post to the finance channel and open a ticket if anything fails.

Connectors are prebuilt and included; where one does not exist, you build your own against an HTTP API with the connector SDK. Systems behind your firewall are reached through an on premises agent, with three included at Business MCP, ten at Enterprise MCP and thirty at Workato ONE, and more sold as an add on. Concurrency, the number of jobs a recipe can run at once, is also fixed by edition: one at Standard and Business MCP, fifteen at Enterprise MCP, thirty at Workato ONE.

Around the recipes sit development, test and production environments, SAML single sign on and multi factor authentication, log retention of 30 days at the lower editions and 90 days at Enterprise MCP and above, and a set of adjacent capabilities: a managed API platform and API proxy, Event Streams, data pipelines, intelligent document processing, Workflow Apps for building forms and approval screens, and Workato GO, a front end for end users.

One tool can replace a tangle of departmental scripts, but every capability is metered separately.

How Workato pricing works

Workato publishes no prices. Its pricing page in November 2026 offers a quote or a demo; the documentation explains the model. Customers who joined before February 2024 are on an older arrangement and should read their own contract.

The bill has three parts: a platform edition, which sets the capabilities you can use; usage, measured in Workato credits; and optional add ons billed separately. Each capability converts its own metric into credits:

  • Tasks for workflow recipes, counted per action step executed in a job. Skipped steps and failed or cancelled jobs do not count, although steps completed before a failure do.
  • API calls for the managed API platform, counted per successful request, with a slow response able to count as more than one call. API proxy calls count one per request.
  • Pages for document processing, events per message published to Event Streams, and rows per row extracted by a data pipeline.
  • Prompts sent to a Genie, Workato’s name for an agent, whether from a person or another system, and seats for end users of Workato GO and Workflow Apps.

Workspaces, users and connectors are unlimited, so the controllable costs are the edition, the number of steps your recipes execute and the add ons you need: on premises agents, extra concurrency, Private Link, a Virtual Private Workato deployment, Advanced Security and Governance, RPA through RobotiQ, EDI through Orderful and the Reltio Data Hub. Small teams can sign up online for Free and Pro plans.

The trap in step based pricing is design. A recipe that polls every minute, loops through every record and calls a lookup for each one will consume credits far faster than one that triggers on events and processes in batches. Estimate credits from your real use cases before you negotiate, because the vendor’s estimate will assume well designed recipes.

Business led automation versus IT led integration

Workato’s pitch is business led automation: the finance team automates the month end close, HR automates onboarding, revenue operations automates lead routing, with IT providing the platform rather than building every recipe. For an organisation running mostly SaaS applications, with a lot of departmental process and a willingness to invest in an automation team, that pitch is largely real.

IT led integration is a different job. It is the thirty interfaces that must run every night between the ERP, the warehouse, the banks and the payroll, with reconciliation, replay and audit, built once by specialists and left alone. Workato can do this work, and its on premises agents, environments and API platform are there for it, but usage pricing and design assumptions aimed at business users make it a less obvious choice than a connection licensed platform when volumes are high and the processes are stable.

So the question to ask is which of the two jobs dominates. If it is automation breadth, Workato belongs on the shortlist with Power Automate and, at the low end, Make and Zapier. If it is high volume system to system integration around an ERP replacement, compare it with Boomi, MuleSoft and, for NetSuite estates, Celigo, and read the pricing section of iPaaS compared with your volumes in hand. Many organisations end up with both an automation platform and an integration platform, which is defensible as long as someone has decided which does what.

Governance: the question that decides whether Workato pays off

Governance decides whether Workato pays off or becomes sprawl. When anyone can build a recipe, within a year you will have hundreds, some business critical, some abandoned, some built by people who have left.

  • Who may build what. Separate workspaces or projects by team, with roles that distinguish building from deploying to production.
  • Promotion. Recipes move from development to test to production through a controlled path, with a review step for anything that writes to the finance system or touches personal data.
  • Budgets. Credit consumption is visible on the billing dashboard; give each team a budget and an alert, because a looping recipe spends real money.
  • Error ownership. Every recipe has a named owner and an error route. An unowned recipe that fails silently is worse than no recipe.
  • Data. Decide what personal data may pass through recipes and how long job logs holding it are retained; 30 or 90 days by edition is a setting to understand, not a default to accept.
  • Lifecycle. A quarterly review that retires recipes nobody has run.

The Advanced Security and Governance add on and the API and MCP gateways help, but the harder part is organisational: an integration design authority, usually in IT, that owns standards while the business owns outcomes. This is where the platform decision meets the data governance work most organisations have been postponing.

Where Workato stands on AI agents

Workato has repositioned itself as the platform through which AI agents reach enterprise systems. The MCP in its edition names refers to the Model Context Protocol, the standard that lets an AI assistant call tools in other systems. Business MCP includes prebuilt MCP servers and an AI and MCP gateway; Enterprise MCP adds AI by Workato; Workato ONE adds Agent Studio for building agents, a Workato Knowledge Base and Workato GO. Pre packaged Genies, Workato’s ready made agents, are sold as an add on.

The billing model follows. A prompt to a Genie is metered, an MCP call is metered as the usage of whatever asset it invokes, and a proxy call to an external MCP server is metered per request. Skills invoked by a Genie are not billed, but the same skill invoked over MCP is billed as tasks.

My reading for a UK buyer is this. If you already run Workato, it is a credible way to let agents act on your systems under existing roles, logging and gateways. If you do not, do not buy an integration platform for its agent story alone. Buy it for the automations you can name today, and treat the agent capabilities as an option you are keeping open.

What adopting Workato involves

Adopting Workato is less about installation and more about operating model.

  1. Name the first ten automations and the business owner of each. Favour processes with a clear trigger, a defined end state and a measurable saving.
  2. Estimate credits for those ten using Workato’s usage documentation, then ask the vendor to price the edition and add ons you need against your figures rather than theirs.
  3. Decide the operating model: which teams build, which review, how recipes are promoted and who holds the credit budget.
  4. Stand up the plumbing: single sign on, environments, on premises agents for anything behind the firewall, and the error routing standard.
  5. Build the first wave with a small mixed team, document as you go, and review consumption after the first month against the estimate.
  6. Negotiate the contract on credit rates at volume, overage treatment, add on prices and renewal uplift.

I have no reseller, referral or alliance agreement with Workato or any other vendor and take no commission. PEF’s consultants have between them led and analysed the choices that come before, during and after system migrations, and we work either as independent assurance alongside your team and whoever is implementing, or by leading the delivery ourselves. Fees are set out openly on our pricing page. If the automation programme touches the CRM, the CRM integration page covers that side.

Related reading: iPaaS compared, Boomi explained, Celigo explained, CRM integration, ERP integration, Data strategy and governance.

Common questions

What is Workato used for?

Workato is used to automate business processes across cloud applications by building recipes: a trigger followed by action steps that read and write data in systems such as a CRM, ERP, HR platform or ticketing tool. Typical uses are lead to cash handoffs, employee onboarding, month end data movement, support escalations and, increasingly, giving AI agents governed access to enterprise systems through its MCP gateway.

How does Workato pricing work?

Workato charges a platform edition plus usage measured in credits, with add ons priced separately, and publishes no list prices. Tasks are counted per action step executed in a recipe job, API calls per successful request, document processing per page, Event Streams per message published, data pipelines per row and agents per prompt. Workspaces, users and connectors are unlimited. Customers who joined before February 2024 are on an older model.

Is Workato an iPaaS or an automation tool?

Both, which is the source of most confusion. It has the integration platform capabilities: connectors, on premises agents, environments, an API platform and event streams. But its design and pricing are built for business led process automation measured in steps, rather than for high volume system to system interfaces licensed by connection. Decide which job dominates in your organisation before comparing it with Boomi or MuleSoft.

Workato vs Boomi: which should I choose?

Choose Workato when the goal is broad automation of SaaS processes by business teams within IT guardrails, and usage based pricing suits variable volumes. Choose Boomi when the goal is IT led integration around an ERP, with EDI, API management and master data on one platform licensed by connection. Many organisations run both; the mistake is buying one for the other’s job.

Does Workato replace Power Automate or Zapier?

It can, but it is aimed higher. Zapier and Make suit individual teams automating small tasks for tens of US dollars a month. Power Automate suits Microsoft 365 users at £11.50 per user a month for the Premium plan. Workato is an enterprise platform with environments, governance, on premises agents and an API layer, priced by quote, for organisations automating across many departments at once.

What is a Workato recipe?

A recipe is Workato’s unit of automation: a trigger, such as a new record, a webhook, a schedule or a chat command, followed by a sequence of action steps that call connectors, apply conditions and loops, and map data between applications. Each action step executed in a job counts as a task for billing. Recipes are built in a browser and promoted through development, test and production environments.

Thinking about Workato for your automation programme? We will size the credits from your real use cases, set the governance and tell you whether it is the right platform.

Book a confidential conversation

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.