What does Zatanna do?

Zatanna maps human-only software workflows and exposes them as reliable APIs. Instead of building brittle browser automation scripts, you show the task once and Zatanna reconstructs the underlying request flow into a stable endpoint your AI agents and internal tools can call in production.

How is Zatanna different from web scraping or RPA?

Traditional web scraping replays clicks and waits on page elements, which breaks whenever the UI changes. RPA tools automate screen-level interactions but require constant maintenance. Zatanna reconstructs the actual HTTP request behavior behind a workflow, producing a stable API that doesn't depend on the UI layer at all.

How does Zatanna handle anti-bot detection?

Zatanna manages TLS fingerprinting, proxy rotation, and detection-sensitive request behavior below the API layer. Sessions, cookies, retries, re-authentication, and error recovery are all handled automatically so your integration stays reliable.

What types of workflows does Zatanna support?

Zatanna works best for workflows that are important, repetitive, and stuck behind a UI — including back-office systems with no API, document and record workflows involving uploads, claim forms, and status checks, and AI agent actions in external third-party software.

How do I integrate with Zatanna?

Integration is a three-step process: (1) A human runs the workflow once while Zatanna observes the real behavior, (2) Zatanna builds a request model that reconstructs the calls, state transitions, and recovery logic, (3) Your systems call a single stable API endpoint while Zatanna manages the fragile workflow underneath.

← All articles2025-08-24 · 5 min read

UiPath and Automation Anywhere: Where Enterprise RPA Excels and Where It Struggles

Enterprise RPA platforms like UiPath and Automation Anywhere dominate screen-level automation. Here's where they shine, where they struggle, and what's changing in 2026.

TL;DR

UiPath and Automation Anywhere are the dominant enterprise RPA platforms, with thousands of enterprise deployments automating screen-level tasks. They excel at desktop automation, have strong governance and compliance features, and benefit from large partner ecosystems. They struggle with speed, web application reliability, and integration with modern AI agent architectures. As the industry shifts toward API-first automation, RPA platforms are adapting — but the fundamentals of screen-level automation create inherent limitations.

Where enterprise RPA excels

Desktop application automation — RPA was built for automating desktop applications like SAP GUI, Citrix environments, and legacy Windows applications. For these use cases, screen-level automation is often the only option, and UiPath and Automation Anywhere do it well.

Enterprise governance — both platforms offer robust audit trails, role-based access control, centralized bot management, and compliance reporting. For regulated industries, these features are often requirements.

Citizen developer programs — RPA platforms have invested heavily in low-code/no-code tools that let business users build automations without engineering involvement. This democratizes automation in large organizations.

Partner ecosystems — both have extensive implementation partner networks, training programs, and certification paths that de-risk enterprise adoption.

Where enterprise RPA struggles

Speed — bots operate at UI speed, clicking through screens at roughly human pace. A workflow that takes a human 2 minutes might take a bot 90 seconds. HTTP request automation does the same workflow in under a second.

Web application reliability — RPA bots struggle with modern web applications that use dynamic rendering, single-page architecture, and frequent UI updates. Browser-level automation is inherently fragile for web-based systems.

AI agent integration — RPA bots are not APIs. Connecting them to AI agents requires middleware, orchestration layers, and additional complexity. AI agents need to call endpoints, not trigger bot processes.

Maintenance cost — industry data suggests 30-50% of RPA program budgets go to maintaining existing automations rather than building new ones. UI changes in target applications require bot updates.

Scaling economics — running hundreds of concurrent bots requires significant infrastructure. Each bot instance consumes compute resources comparable to a human workstation.

The 2026 evolution

Both UiPath and Automation Anywhere are actively adding API-based capabilities, AI features, and cloud-native deployment options. They recognize that the market is shifting from screen-level to API-level automation.

However, the core product architecture — built around recording and replaying UI interactions — creates challenges in making this transition. Adding API capabilities to an RPA platform is different from building automation around APIs from the start.

When to use enterprise RPA

Enterprise RPA remains the right choice when:

Your primary targets are desktop applications (not web-based)
You need enterprise governance and compliance features
You have an existing RPA program with established bots
Your organization prefers citizen developer tools over engineering solutions

When to use request-level automation

Request-level workflow APIs are better when:

Your targets are web-based systems
Speed and reliability at scale matter
AI agents need direct endpoint access
You want to avoid the maintenance overhead of screen-level automation

The bottom line

UiPath and Automation Anywhere built the RPA category and serve thousands of enterprises. Their strengths in desktop automation and enterprise governance are real. For web-based workflow automation — especially for AI agent integration — request-level approaches like Zatanna offer a fundamentally different trade-off: less governance tooling, but dramatically faster, more reliable, and more maintainable automation.