BPA vs RPA vs iPaaS vs agentic automation: which one you need
Abstract
This guide compares business process automation, RPA, iPaaS and agentic automation by the problem each one solves. A sourced decision table shows where each one breaks, and a short sequence shows the order to add them in. It links the Atlas definition pages rather than repeating them.
Which one fits your problem
With no API to connect to, RPA is the only approach of the four that reaches the app.
UiPath points RPA at systems that lack APIs, UiPath RPA and selectors Microsoft Learn, UI elements are what break when that app changes.
Each question is one row of the decision table, read 16 Nov 2026, and the grey line is where that approach breaks. The table's cells, with sources, are in words below.
In words
- Legacy app with no API: RPA. UiPath points RPA at systems that lack APIs. UiPath RPA Where it breaks: changes to the app's structure, which selectors depend on. Microsoft Learn, UI elements
- Many SaaS apps must share data: iPaaS. Direct connections between systems, not screens. Zapier blog Where it breaks: an app with no API to connect to. UiPath RPA
- Approval steps across departments: BPA or BPM. Coordinates predefined steps across systems and people. Camunda Where it breaks: a path nobody predefined. Camunda
- Next step depends on judgement: Agentic. The model directs its own process and tools. Anthropic Where it breaks: compounding errors and higher cost. Anthropic
Start from the problem, because the four approaches solve different ones. Each row pairs a problem with the approach vendors describe for it, and names where that approach breaks, with every cell sourced as of 16 Nov 2026.
If your problem is mixed, split it, and give each part to the approach that fits, then connect the parts instead of forcing one tool to do everything.
How does RPA differ from workflow automation?
RPA works at the user interface, so a bot depends on how the screen looks. Zapier blog
One app with two ways in, where the bot goes through the screen and the iPaaS goes through the API.
In words
- RPA works at the user interface level, while iPaaS creates direct connections between systems. Zapier blog
- A desktop flow reaches the app through UI elements, images or screen coordinates, Microsoft Learn, desktop flows which is the green line into the screen.
- An iPaaS reaches the same app through its API, the blue line. UiPath places RPA where systems lack APIs. UiPath RPA
RPA is software that operates other software through its user interface, and workflow automation moves data and steps between systems through their connections. UiPath describes RPA as software robots handling repetitive, rule-based tasks, UiPath RPA as well as mimicking human actions on screens and systems. UiPath RPA
Desktop flows, selectors and the rule that follows
Microsoft's desktop flows work the same way, driving modern apps as well as legacy software through UI elements, images or screen coordinates. Microsoft Learn, desktop flows That is the whole appeal and the whole risk, since selectors must survive changes in the app's structure. Microsoft Learn, UI elements
Workflow automation, in the iPaaS sense, connects systems directly. Zapier puts the split plainly, saying RPA works at the user interface level while iPaaS creates direct connections between systems. Zapier blog A direct connection does not depend on how the screen looks, and a bot does.
The rule follows from that. If the app has an API, use workflow automation, and if it does not, RPA may be your only route, UiPath RPA so budget for repairs.
iPaaS: the connector layer
Zapier's agents page cites 9,000+ apps, and an iPaaS reaches each one directly instead of through its screen.
The count was read on 16 Nov 2026, Zapier agents and an app with no API still leaves an iPaaS nothing to connect to. Zapier blogUiPath RPA
Choose iPaaS when many apps must exchange data and each has a usable API. Workato defines iPaaS as a cloud service to build, run and govern integration flows, Workato and Zapier's agents page cites 9,000+ apps, Zapier agents as of 16 Nov 2026.
Where an iPaaS stops: no API, and human approval chains
The catch is the API, since an iPaaS connects systems directly Zapier blog and an app with no API leaves it nothing to connect to. Which is exactly where UiPath points RPA. UiPath RPA
An iPaaS is also the wrong shape for a human approval chain. Camunda says workflow automation and iPaaS connect predefined actions and applications. Camunda Process orchestration, in its words, coordinates predefined execution across systems and people. Camunda
BPA and BPM: when people are in the loop
BPA and BPM coordinate predefined steps across systems and people, Camunda particularly where someone has to approve or sign.
An example route rather than a vendor's. Green marks the steps a person takes, and the dashed stub is a case the model never drew.
In words
- Process orchestration coordinates predefined execution across systems and people, Camunda and the figure shows one example route rather than a vendor's own.
- A request comes in on the systems side, then a person approves, the system updates the record, a person signs and the route ends. The two people steps are green.
- The route is drawn before it runs, so a case nobody predefined has no route Camunda and a new exception needs a change to the model.
Choose BPA or BPM when the process crosses teams and someone has to approve, correct or sign. Camunda describes process orchestration as coordinating predefined execution across systems and people, Camunda and the key word is predefined.
That gives you a governed process, and Camunda ties BPA to governance and auditability, Camunda but the cost is modelling effort up front, because a path nobody predefined has no route. Camunda Which means a new exception needs a change to the model.
Atlas defines business process automation and business process management elsewhere, so this page doesn't repeat them.
Agentic automation: when the path is open
Run it five times and the fixed steps repeat, whereas in 1 of the 4 approaches the model picks the next step.
Camunda says iPaaS and workflow automation connect predefined actions, Camunda whilst agents, in Anthropic's terms, direct their own processes and tool usage. Anthropic
Five example runs, illustrated rather than measured, drawn one behind the other. The tool dots are unnamed because the model picks them at run time, and on a phone one run is drawn flat.
This figure in words
- RPA, iPaaS and BPA all follow a path fixed when the workflow is built. AnthropicCamunda RPA drives screens Microsoft Learn, desktop flows and iPaaS connects systems directly, Zapier blog with BPA routing work between people and approvals. Camunda
- Run them five times and they take the same steps five times. The figure draws those five example runs one behind the other, and through the fixed steps they run together as one blue band. The runs are an illustration rather than a measurement.
- Only agentic automation lets the model choose the next step at run time, so its path can differ each run. AnthropicCamunda In the figure the five lines split in green at the agent step. Each run reaches its own mix of three unnamed tools, then rejoins the band.
- n8n keeps the agent as one step inside an otherwise fixed workflow, n8n which is why the band carries on after the agent step.
Choose agentic automation when the next step depends on what the model reads. Anthropic separates the two cleanly, since workflows run through predefined code paths Anthropic and agents dynamically direct their own processes and tool usage. Anthropic
Camunda's definition adds the goal, describing a goal-directed software system that interprets information, Camunda and its page says agentic orchestration adds autonomous decision-making when the path cannot be fully predefined. Camunda
That being said, the cost is control. Anthropic notes that agents carry higher costs and the potential for compounding errors, and it recommends sandbox testing with guardrails. Anthropic Keep an agent inside a fixed flow, with a human check on anything irreversible, and do not hand it a payment run.
Where the four overlap and vendors blur the terms
Of the four vendors we read on agents, two keep the agent inside a fixed flow.
n8n and Copilot Studio do, n8nCopilot Studio whilst UiPath and Camunda run agents beside people and other automation. UiPath MaestroCamunda
Each box names only what that vendor's own page names, read 16 Nov 2026, and the steps around the agent are generic.
In words
- On the left, the agent sits inside a fixed flow as one step on a path the designer set. Its green box is the only highlight.
- n8n calls workflows its deterministic backbone, with the AI Agent node as one step inside a workflow. n8n
- Copilot Studio says its workflows combine the predictability of automation with the flexibility of AI. Copilot Studio
- On the right, one process layer runs agents beside other work. UiPath Maestro orchestrates AI agents, robots and people. UiPath Maestro
- Camunda coordinates AI agents as well as people and systems across end-to-end business processes. Camunda
Vendors blend the four, so a product label rarely tells you which one you are buying. UiPath's Maestro orchestrates AI agents as well as robots and people in one process layer, UiPath Maestro which puts BPM, RPA and agents under one name.
The pattern runs the other way too. n8n calls workflows its deterministic backbone, with the AI Agent node as one step inside a workflow. n8n Microsoft's Copilot Studio says its workflows combine the predictability of automation with the flexibility of AI. Copilot Studio In Anthropic's terms, a fixed flow with an LLM step is a workflow. Anthropic
So ask one question of any product, namely who picks the next step, the designer or the model? For the wider comparison, see the Atlas pages on RPA vs workflow automation and iPaaS vs RPA vs workflow automation.
Hyperautomation and intelligent process automation as umbrella labels
Both terms name a combination of the four rather than a fifth technology. IBM describes hyperautomation as automating everything in an organisation that can be automated, using AI, RPA and other technologies. IBM, hyperautomation It describes intelligent automation as combining AI and automation technologies. IBM, intelligent automation
Atlas's own hyperautomation page says Gartner popularised the term in 2019, and that as of May 2026 agentic automation increasingly absorbs it. Atlas Treat both labels as marketing envelopes, and when a vendor says either, ask which of the four they actually sell.
What order should a team add them in?
Add an agent last, for one judgement step with a human check after it.
The agent then starts on data the earlier steps have connected.
Each tread adds one approach, from 0 to 4 in place, and the four steps are written out in words below.
In words
- Step 1: Connect your apps with iPaaS wherever an API exists. After it, 1 of the four approaches is in place.
- Step 2: Add BPA or BPM for the approval chains that cross teams. After it, 2 of the four approaches are in place.
- Step 3: Use RPA only for the apps with no API, and log each bot as a debt item. After it, 3 of the four approaches are in place.
- Step 4: Add an agent last, for one judgement step, with a human check after it. After it, 4 of the four approaches are in place.
- The agent step is the green tread, and the dark dot at its end is the human check after it. Anthropic
Start with iPaaS where each app has an API, then add the others only where it falls short, although this order is editorial advice and no vendor page states it.
Skipping to step four leaves an agent working on data nobody has connected, and agents carry the potential for compounding errors. Anthropic For the agent definition, see the Atlas page on agentic automation.
Example products per approach
Synthetic example, not a client case: a team approves supplier invoices. An iPaaS moves the data, a BPM flow routes approvals, RPA keys one legacy ledger, and an agent reads the PDF.
Example products, one sourced fact each (7 rows)
| Approach | Product | Sourced fact |
|---|---|---|
| RPA | Power Automate desktop flows | Drives UI elements, images or coordinates Microsoft Learn, desktop flows |
| RPA | UiPath | Software robots for repetitive, rule-based tasks UiPath RPA |
| iPaaS | Workato | Cloud service to build, run and govern integration flows Workato |
| iPaaS | Zapier | Agents page cites 9,000+ apps Zapier agents |
| BPA/BPM | Camunda | Process orchestration of predefined execution Camunda |
| Agentic | Anthropic agents | LLMs direct their own processes and tool usage Anthropic |
| Agentic | OpenAI agents | Agents plan and complete tasks using tools OpenAI |
Questions
What is the difference between RPA and iPaaS?
RPA works at the user interface level, while iPaaS creates direct connections between systems. Zapier blog RPA fits apps that lack an API. UiPath RPA
When do I need BPA or BPM rather than an iPaaS?
When the process crosses teams and someone has to approve, correct or sign. Process orchestration coordinates predefined execution across systems and people. Camunda
What makes automation agentic?
The model picks the next step, and Anthropic defines agents as systems where LLMs dynamically direct their own processes and tool usage. Anthropic
Is a workflow with an AI step an agent?
No, in Anthropic's terms a fixed flow with an LLM step is a workflow. Anthropic The n8n page puts its AI Agent node as one step inside a workflow. n8n
Is hyperautomation a separate technology?
No. IBM describes it as automating everything that can be automated, using AI, RPA and other technologies. IBM, hyperautomation Ask which of the four a vendor sells.
Which approach should a team add first?
An iPaaS, wherever an API exists, and an agent last, for one judgement step with a human check after it. This order is Atlas's editorial advice, and no vendor page states it.
Sources
RPA and iPaaS vendors
- UiPath, What is robotic process automationPage undated. Read 16 Nov 2026.
- Microsoft, Introduction to desktop flows, Power AutomateDated 23 Aug 2026. Read 16 Nov 2026.
- Microsoft, UI elements in desktop flows, Power AutomatePage undated. Read 16 Nov 2026.
- Workato, What is iPaaSDated 18 Sep 2026. Read 16 Nov 2026.
- Zapier, What is iPaaSDated Sep 2021, updated Aug 2025. Read 16 Nov 2026.
- Zapier, Zapier AgentsPage undated. Read 16 Nov 2026.
Process and agent vendors
- Camunda, Agentic orchestrationDated 9 Nov 2026. Read 16 Nov 2026.
- UiPath, Maestro overview, Automation Cloud user guidePage undated. Read 16 Nov 2026.
- Anthropic, Building effective agentsDated 19 Dec 2024. Read 16 Nov 2026.
- n8n, AI agentsPage undated. Read 16 Nov 2026.
- Microsoft, What is Copilot StudioDated 27 Oct 2026. Read 16 Nov 2026.
- OpenAI, Agents guidePage undated. Read 16 Nov 2026.
Definitions and Atlas pages
- IBM, What is hyperautomationPage undated. Read 16 Nov 2026.
- IBM, What is intelligent process automationPage undated. Read 16 Nov 2026.
- Automation Atlas, What is hyperautomationDated May 2026. Read 16 Nov 2026.
Each chip in the text opens its source here. A secondary glossary credited Gartner with the term hyperautomation; it was read but not used.