Stop hard-coding approvers into every workflow.
Use Roster to resolve the right user, group, role, or delegate at runtime — then let your existing workflow platform deliver and manage the task.
Build routing logic once and reuse it across automation systems, agentic workflows, and business processes.
One workflow. One pause point. One current participant.
Automation platforms are excellent at moving work forward. They are less good at knowing who should touch it next. Roster owns a single resolve() step — before your engine assigns, notifies, escalates, or hands off.
Every engine, the same call
Whatever runtime you already operate, Roster is a single HTTP or MCP call away. The rest of the workflow keeps its native shape — HTTP nodes, service tasks, approval connectors, subflows.
// one routing model — many engines · REST + MCP + CLI
Before Roster / After Roster
Same procurement workflow. Two very different maintenance stories — as roles change, people leave, and coverage shifts.
Delegation without touching the workflow
When an active participant hands off responsibility, the workflow definition doesn't change. Roster changes its answer — with the trail back to the original owner preserved.
The workflow YAML you shipped in April keeps running. The organizational reality is what moves.
Common workflow use cases
Route each vendor review to the right procurement, finance, security, or legal approver based on project and request context.
Send work to the current account owner, implementation lead, regional team, or delegated contact — not last quarter's owner.
Determine which participant should review a policy exception, access request, vendor, or data-processing action.
Use directory or Workday context to route HR, payroll, management, or employee-service requests.
Resolve release approvers, service owners, change reviewers, and escalation contacts.
Let an agent determine which human should review or approve before it executes a sensitive action.
One routing model across every workflow engine you run
The same Roster participant can serve an AI agent, an n8n workflow, a Power Automate flow, a Camunda process, a CI pipeline, a custom application, and a human — so every automation team stops maintaining its own version of organizational responsibility.