Company
OKRunit exists to put human judgment back into automated work.
OKRunit is a human-in-the-loop approval gateway for teams running automations, AI agents, internal tools, and operational workflows. It sits between a workflow and a sensitive action, pauses execution, routes the request to the right reviewers, and records the decision trail.
What OKRunit does
The product is designed for workflows that should not execute without clear human sign-off.
Central approval queue
Requests from APIs, no-code tools, and agents land in one place with source, priority, context, and decision history.
Routing and notifications
Teams can route approvals to the right people and deliver them through dashboard, messaging channels, and webhook callbacks.
Audit visibility
Every request, comment, decision, and configuration change is recorded so operators can understand what happened and why.
How it fits into a workflow
OKRunit is intentionally simple: it becomes the approval layer between a trigger and a sensitive action.
A workflow creates a request.
This can come from a direct API call or from tools like Zapier, Make, n8n, GitHub Actions, or custom internal services.
Reviewers get context before deciding.
The request includes the title, description, metadata, source, priority, and any configured routing rules or approval steps.
The decision flows back into the system.
Once approved or rejected, OKRunit updates the request state and notifies the calling workflow so it can continue or stop.
Who uses it
OKRunit is built for teams that need reliable control over operational changes, customer-impacting actions, and destructive workflows.
Engineering and platform teams
Use OKRunit to gate production deploys, credential rotation, infrastructure changes, and bulk operations.
Operations and business systems teams
Use it to review CRM edits, account changes, notifications, billing updates, and customer-data workflows before they run.
For implementation details, start with the getting started guide or the API reference.