Workflow engine for HR teams
Oasis HR gives HR operations a canvas for approval logic. States, conditions, and approval chains are drawn, validated, and routed — without a ticket to engineering.
The engine owns the rules. HR operations owns the design.
Start, normal, condition, complete, denied, and cancelled states. Drag them onto the canvas and connect transitions with named conditions.
Every state resolves its approver from a typed target: approver, request owner, record owner, or group. Actions carry email, webhook, and notification dispatch.
The editor rejects unnamed states, missing terminal states, and malformed payloads before a workflow can be published.
In build. Three places, and nowhere else.
HR policy already lives in documents and intranet pages. AI retrieves the rule that applies to the process the manager describes.
It returns a workflow draft: states, conditions, approval chain, and the edge cases the document mentions. The manager edits it on the canvas.
Nothing publishes itself. The manager reviews the draft, fixes it, and approves it before it becomes a live route.
Model choice. We build on Claude. It is the only model in our AI layer, and it is not a placeholder we plan to replace later.
The same engine reads every domain. Only the sentence changes.
Each module ships its own states, fields, and conditions.
Annual, medical, and parental requests with balance fields.
Claim review, budget thresholds, and finance queues.
Offer stages, approval gates, and rejection paths.
Task sequences across IT, payroll, and the hiring manager.
Review cycles with self, manager, and calibration steps.
We would rather you read this than find out on a call.
We run the product on a call, from an empty canvas to a published route. If it is not a fit for your HR team, you will know in ten minutes.