Rubie decomposes every data workflow into six discrete, production-hardened operations. Each primitive can be used in isolation or chained into a Playbook. Together, they cover every step between a locked portal and a clean system of record.
The entry point for every Rubie workflow. Authenticate handles getting in (and staying in) across the full range of enterprise login patterns. All credentials are AES-256 encrypted at rest, scoped to a single workflow run, and never exposed.
// Covers //
Navigate drives the agent through multi-step flows the way an experienced operator would — clicking, filtering, drilling down, and handling pagination no matter how many layers deep the data sits. Unlike traditional RPA, Rubie navigates by semantic context rather than pure CSS selectors. When a portal updates its UI, Rubie adapts without re-scripting.
// Covers //
Raw portal data is rarely usable as-is. Rubie normalizes it before anything downstream is affected — dates, phone numbers, currency, names, and any field that arrives inconsistently across rows or sources. Every operation is rule-based and auditable. Define the target format once and Rubie enforces it consistently across every record, every run.
// Covers //
// Common in //
Clean data still needs to fit somewhere. Rubie reshapes records to match the exact schema of your target system. This goes beyond formatting: direct field mapping, type coercion, calculated fields, conditional logic, lookup tables, and nested object construction. The step that makes extracted data usable.
// Covers //
// Common in //
A human-in-the-loop checkpoint before anything gets written. Review routes transformed records through your validation rules, automatically advancing clean data while sending flagged records to a review queue for approval, correction, or rejection. You decide how much human oversight each run needs, from full auto-approval to selective review to mandatory sign-off.
// Covers //
// Common in //
Rubie writes transformed, reviewed records precisely into your target system — transactionally, with full auditability. Supports REST API writes and flat-file handoffs. Every operation produces a full write receipt: record count, field confirmations, and any system-generated IDs returned from the target.
// Covers //
// Common in //
