Integration
Connect OKrunit to Browser Use
When something happens in OKrunit, your agent does the next thing in Browser Use. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want OKrunit and Browser Use to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with OKrunit and Browser Use
Triggers and actions 2 triggers ยท 11 actions
Trigger
Approval DecidedTriggers when an approval request is approved or rejected.
Trigger
New Approval RequestTriggers when a new approval request is created in your organization.
Action
Add CommentAdd a comment to an existing approval request.
Action
Find Approval RequestFind a specific approval request by its ID.
Action
Find ApprovalsSearch for approval requests with filters.
Action
Request ApprovalCreate an approval request for a person to approve or reject. The request is created immediately and starts out pending; watch the Approval Decided trigger for the outcome.
Action
Delete profileDelete a browser profile.
Action
Delete workspaceDelete a workspace.
Action
Get profileGet the details of a specific browser profile.
Action
Get workspaceGet the details of a specific workspace.
Action
List workspace filesList files stored in a workspace.
Action
Update profileUpdate a browser profile.
Action
Upload workspace filesUpload files into a workspace.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.