Overview
Connect any machine to Mandala, no API required.
Live in production. Karma RPA is deployed and has been confirmed end-to-end on both staging and production, each with a real client machine, a real dispatch, and a real result.
Karma RPA is how Mandala reaches systems that have no API at all -- a legacy desktop ERP, a government portal, an internal tool that only exists as a screen on one particular machine. Instead of asking that system to expose an API, you run a small client program on a machine that already has access to it. That client registers once with your workspace, stays connected, and tells Mandala what it can do. From then on, Mandala can ask it to do those things -- from a workflow, or from an agent -- without ever needing direct network access to the machine itself.
This section covers the feature from two different angles:
Registering a Client
How a workspace admin registers a new client machine, and how that machine trades its registration token for a working credential.
Client Protocol
The wire protocol reference for building the client program itself: how it connects, publishes capabilities, and receives/reports on jobs.
Security
How to handle the client's credential safely, and what a revoked-credential disconnect means and how to recover from it.
If you're a workflow author rather than the person building or running a client machine, you likely want the block reference instead: Karma RPA (blocks) covers the canvas block, the agent-tool pair, the settings dashboard, and per-capability approval.
How the Pieces Fit Together
- A client machine runs your own program -- built against the protocol in this section -- with access to whatever system you're automating.
- Your Mandala workspace is where you register that client, approve its capabilities, and build workflows or agents that dispatch jobs to it.
- The connection between them is a single persistent, authenticated connection the client itself opens outward to Mandala. Nothing ever connects inward to the client machine, so it can sit behind a NAT or firewall with no inbound ports opened at all.
Only the client machine ever initiates the connection. Mandala never needs to reach the client directly -- which is exactly what makes this workable for a machine with no public IP, sitting behind an ordinary home or office network.