Orchestration Model
Most automation tools specialize in one execution style — API routing, RPA, or AI. Wrk is designed around orchestration: a single control plane that coordinates API calls, browser automation, AI steps, and human review in one Wrkflow.
Why orchestration matters
Real business processes rarely fit a single tool category. A typical flow might:
- Receive a webhook (trigger)
- Call an API to fetch data (connector)
- Use AI to classify a document (AI action)
- Automate a legacy portal when no API exists (RPA)
- Pause for human approval (Human-in-the-Loop)
- Write results back to a CRM (connector)
Orchestration keeps these steps in one run with shared state, retries, and monitoring.
Wrk's approach
- One Wrkflow — one process, one run history, one set of inputs and outputs
- Mixed Actions — API, RPA, AI, transforms, and human steps in any order
- Shared data — outputs from any step available to downstream Actions
- Unified monitoring — see the full run, not disconnected tool logs