RPA fits systems without APIs, volatile processes, and short-term cost cuts; stable high-frequency paths prefer APIs or middleware. Using RPA as fake integration leaves fragility for ops. Answer frequent questions first, then the summary table.
All RPA forever?
Short-term savings; long-term you run a bot ops shop.
When to switch to APIs?
Watch failure rate, maintainer months, and peak load survival.
Can business users build RPA?
Simple flows yes; credentials, access, and change control still need governance.
Relation to AI agents?
RPA clicks; agents reason. Critical transactions still want deterministic APIs.
Treat fragile automation as debt, not as assets
| Decision lens | Common trap or cost | Safer cut |
|---|---|---|
| No API/short-term | RPA bridge | Retirement clause |
| Stable high-freq | API/middleware | Auditable |
| Priority | High-freq clear rules | Few exceptions |
- Ask first whether a stable API and sandbox exist.
- UI churn makes RPA maintenance explode.
- High audit needs favor interface trails that are easier to prove.
- RPA can bridge until APIs exist, with an explicit retirement condition.
- Prioritize high-frequency, clear rules, few exceptions.
