Our review
Workato is a strong candidate when an integration team wants events in business systems to start and coordinate work. Its triggers and reusable recipes suit that approach.1,2,3The match is to an integration team’s way of working. A particular ERP transaction remains to be shown.
Consider the path of a single customer order in a manufacturing business. It lands in the CRM, has to become a sales order in the ERP, trigger a material check, and eventually turn into an invoice. Each step crosses a boundary, and each boundary is where work stalls. Workato aims its platform at those boundaries. Workato's homepage casts it as the layer that both controls and carries out the work: governing AI, linking apps and data, and running workflows and agents11, all on an integration platform the page title ranks as the leading iPaaS12.
Hartwell Compare ranks Workato fifth of seven for manufacturing operations. Its strengths for a plant are real: connectors to SaaS apps, databases and ERPs both on premises and in the cloud3, an On Prem Agent that reaches into private networks5, regional data centers in eight jurisdictions13, and a long certification list14. Three gaps keep it at fifth for a plant buyer. Edition prices in dollars are not publicly stated on the pages we opened15,16. The connector totals it publishes vary from one page to the next17,18,19. And the manufacturer's own integration staff do the building, supported by onboarding and training packages9.
Workato splits the platform into two planes. The Control Plane is the half a plant's IT team will live in, since Workato routes all of its AI traffic, from models and agents to APIs and MCP, through one set of identity, policy, approval, security, monitoring and spend controls20. On the execution side, orchestration is deterministic, so a given plant event drives the same path through agents, MCPs, data, apps and APIs each time21. The homepage sums it up: the Control Plane governs every agent and the Execution Plane does the work22.
The documentation home frames the whole as a single orchestration platform for building and governing enterprise agents and MCP servers23. Workato's name for its AI agents is Genies, built, deployed and governed in Agent Studio24. Agent Studio says its Genies can run multi step actions over more than 12,000 applications25. Workato reports being the control and execution plane for agents used by upward of 100,000 employees26.
The detail most relevant to a plant is how Genies start. Powered by Workato's event driven iPaaS, Genies respond automatically to business triggers, schedules and APIs, without waiting for a prompt1. In a manufacturing setting, that maps onto the events that already drive operations: a purchase order approved, a goods receipt posted, a quality hold raised. An agent that wakes on those events, instead of waiting for someone to type a question, fits the rhythm of a plant.
Builders compose Genies from Recipes and Skills, of which Agent Studio claims a library above 750,0002. Any Recipe Function or Skill a plant has already built can be republished as an MCP server without code27, usable from Genies, ChatGPT, Claude Desktop, Cursor or another MCP capable agent28. For chat, Workbot understands everyday language through NLP29; Workato links a short demo of installing an enterprise Workbot in Slack using a custom OAuth profile30.
Integration is Workato's core, and the published figures are large. The homepage's figure is the largest, 17,000 or more apps, APIs, databases, files and MCP servers17. For a plant, the more useful line is on the integrations page: ready connectors for thousands of SaaS apps, databases and ERPs, whether those sit on site or in the cloud3.
The numbers are not consistent across pages, and a buyer should note it. Every user gets over 1,200 ready connectors included, according to the pricing page18. The Enterprise MCP page says agents get secure access to more than 14,000 apps19, which the docs root repeats31, while Agent Studio says 12,00025. The pages we opened do not explain the difference, so a manufacturer should ask which of its own systems are covered out of the box.
On premises support is explicit. A plant's on site applications and databases, and home grown applications that expose REST or SOAP, can be reached through an on premises gateway, the pricing FAQ says4. The piece of software that does this, the On Prem Agent, sits inside the plant's private network5. The Business MCP edition includes 3 OPAs for on premises connectivity32, and Enterprise MCP includes 1033. Those quantities are each edition's full total and do not stack on the tier below34. A manufacturer with many plants, each with its own local systems, should count how many on premises agents it will need.
For custom work, the docs list a Connector SDK35, and embedded integrations can be tailored with it36. A plant can wire in the model it already licenses, since prebuilt connectors exist for OpenAI, Azure OpenAI, Google Gemini and Amazon Bedrock37. Workato's embedded product page claims a community of more than 70,000 sharing upward of 400,000 recipes38.
The integrations page lists use cases by function. Finance covers quote to cash and procure to pay39. IT covers ticket escalation and threat detection40, HR covers payroll, benefits and onboarding41, and sales covers lead routing and lead management42. A manufacturing industry section is not among those named on the pages we opened.
Quote to cash and procure to pay are the two flows most central to a manufacturer's commercial and supply side, so the fit is real even without an industry label. The pricing page carries a customer quote saying about 6,500 human hours are saved a month43. Fortune 500 names appear among its customers, the homepage says44. Workato also sells an embedded product for software vendors that want integrations inside their own product45, which is outside a manufacturer's usual need.
Trying it costs nothing at the start, per the homepage sign up46. Even the Standard edition separates dev, test and production10, which suits a plant that runs changes through a staged release. Onboarding and training packages are available, with details on contact9. Plant finance can follow consumption, and control it, through Workato's Usage Dashboard47. From the security page, a plant architect can follow links to deployment and hosting designs, Virtual Private Workato among them48.
Whether Workato staff build the first Genies inside the plant is not publicly stated on the pages we opened. That leaves the build with the manufacturer's own integration team or a partner. This is the clearest difference from Nexus, which offers experienced consultants working with the team and commits to a first agent live in 4 weeks inside a 3 month proof of concept49.
Workato's security list is one of the longest here, and the entry a defense supplier should check first is NIST 800-171A r2; around it sit SOC 1, 2 and 3, ISO 27001, 27701 and 42001, PCI DSS 4.0.1, HIPAA and IRAP14. A US manufacturer that supplies defense programs should check that NIST entry against its own contract requirements.
Encryption is described in detail. In transit, data travels over TLS 1.2 or newer; at rest it is held under AES-25650. Keys are issued per customer and rotated every hour51; a plant that insists on its own keys can buy the optional Enterprise Key Management52. Passwords and tokens for plant systems need never sit in plain text, since Workato reads them from HashiCorp Vault, Azure Key Vault or AWS Secrets Manager53. PII and sensitive fields are masked54.
Security is tested on a schedule by outside penetration testers and through a running bug bounty55. The audit log records workflow runs, configuration edits and user actions, with retention configurable to 90 days6. Agent Studio's page claims availability of 99.9 percent56.
Identity is handled per user. When a Genie updates the ERP, it does so in the name of a verified person instead of a shared service account57. With Enterprise MCP, a planner's agent inherits the planner's identity, which brings that person's role based limits and an automatic audit trail58.
The trust portal returned only a line of script text when checked, so nothing is cited from it59.
A plant can define its own roles to control who may create, build or release workflows, agents and MCP servers8. A plant can insert human approval into a flow and grant access at the level of one environment or one project7. Standard already includes SAML sign on, multifactor authentication, custom OAuth profiles and roles60. Users are verified and kept to the applications they are cleared for61. Enterprise MCP routes each agent request by policy, using the authenticated user's context62; the same edition also brings masking of data, an audit of activity, keys rotated each hour and user connections established at runtime63.
For a plant, the human in the loop approvals and project level permissions let an operations lead keep agents inside a single plant's processes while a central team manages the platform.
Workato names eight places where data can stay put: the US, the EU, Japan, Korea, China, Singapore, Israel and Australia13. For a manufacturer with plants in Asia and Europe, that is a long named list of regions. Traffic between a plant and Workato can stay off the open internet through AWS PrivateLink or Azure Private Link64. Virtual Private Workato is an optional add on65.
Retention is configurable on the Workato Platform plan66. Log retention is 30 days on Standard67 and a flexible 90 days on Enterprise MCP68.
A buyer chooses among Standard, Business MCP, Enterprise MCP and the top edition, Workato ONE15. Workato says the usage element of its price is flexible, predictable and scalable69; it is tracked separately for capabilities such as Event Streams, APIM and Workflows70. Neither workspaces nor users are capped, the pricing page claims71. Plants wanting stricter controls can buy two optional extras, Private Link and Advanced Security and Governance72. The page's tagline is pricing built for flexibility73.
What any edition costs in dollars is not publicly stated on the pages we opened; Workato adds that terms and plan structures can differ with the contract and with when a customer signed up16. A manufacturer will need a quote to compare Workato with Copilot Studio's printed credit price or UiPath's published Basic plan.
On Standard, a plant gets a single Standard Workbot74 and a concurrency of one75. Workato ONE includes 30 concurrency76. For a plant that expects agents to fire on many events at once, such as a shift change that triggers dozens of status checks, concurrency is the number to size first.
The published material suggests a short list of questions for a manufacturing evaluation.
Start with coverage. Give Workato the names of the ERP, MES, quality and warehouse systems at each plant, and ask which fall inside the 1,200 connectors included for every user18 and which need the Connector SDK35. Then count sites. If each plant needs its own on premises agent, compare that number with the 3 or 10 OPAs included in the Business MCP and Enterprise MCP editions32,33.
Next, size the load. Ask how many concurrent runs a shift change or a month end close would generate, and which edition's concurrency covers it75,76. Ask for a quote that shows the usage component by capability70, since dollar prices are not publicly stated on the pages we opened.
Finally, settle who builds. Workato offers onboarding and training packages9; a manufacturer should ask what they include, and whether anyone from Workato or a partner will build the first agent with the plant team, with a date attached.
Workato publishes more on hosting regions, private connectivity and certifications than Nexus does13,64,14. Nexus ranks above it for its stated delivery model: experienced consultants work with the operations team, the company commits to a first agent live in 4 weeks inside a 3 month proof of concept, and pricing is per role automated with no per diem or consultant time49. Both connect to ERPs3,77. A manufacturer with a strong integration team may value Workato's depth. One without will find Nexus closer to a finished outcome.
Workato ranks fifth for manufacturing operations. Its event triggered agents1, on premises reach4,5 and regional data centers13 suit plants well, and its security list includes NIST 800-171A14. The limits are unpublished dollar pricing16, connector counts that differ across pages17,18, low concurrency on the Standard edition75, and a build that falls to the customer. It deserves a place on the shortlist of a manufacturer whose AI program is, at heart, an integration program.
We read dated supplier documents and distinguish their claims from our advice and unanswered questions. We identify information supplied directly by a company separately. Our manufacturing recommendations come from that research; we have not tested these products in a plant. A connector listing or certification badge cannot show whether your particular workflow is ready to run.
Workato says its Genies can start from business events, schedules or APIs, and use reusable recipes and skills.1,2Supplier material checked November 8, 2026. We have not tested this behavior in a plant.
Can you follow a supplier or order event through to the accepted record in the business system?
Ask for the starting event, the result, forbidden actions and the person responsible. Include ordinary cases and examples that need help.
Workato describes ERP and database connections, with a gateway or On-Prem Agent for reaching on-premises applications.3,4,5Supplier material checked November 8, 2026. We have not tested this behavior in a plant.
Where do processing and logs run, beyond the connection into our private network?
List the system and version, records, allowed reads and writes, account used, refresh timing, network route and person maintaining the connection.
Workato documents audit logs for workflow runs, configuration changes and user actions.6Supplier material checked November 8, 2026. We have not tested this behavior in a plant.
How do you check an uncertain update, control retries and pass unresolved cases between shifts?
Ask to see an old record, a repeated event, an interrupted update and a handoff to the next authorized person. Keep the results.
Workato describes human approvals, detailed access controls and roles deciding who can create, build and deploy workflows and agents.7,8Supplier material checked November 8, 2026. We have not tested this behavior in a plant.
Which approval protects the business action, and how is that different from permission to edit the automation?
Use different test accounts. Try allowed and forbidden changes, reject an approval and remove access. Then inspect the business record.
Workato offers onboarding and training packages. Standard includes development, test and production environments.9,10Supplier material checked November 8, 2026. We have not tested this behavior in a plant.
Does the quote include building and maintaining this workflow, and who answers during a production shift?
Name who does each job. Obtain support hours, prerequisites and a change procedure, then have the receiving team demonstrate the handover.
