Integration
Connect OKrunit to Byteplant Phone Validator
When something happens in OKrunit, your agent does the next thing in Byteplant Phone Validator. 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 Byteplant Phone Validator 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 Byteplant Phone Validator
Triggers and actions 2 triggers ยท 6 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
Bulk Validate Phone NumbersUpload a CSV file (up to 100K phone numbers) for asynchronous bulk validation. POST https://api.phone-validator.net/api/v2/bulk-verify with Content-Type: text/csv and the CSV as the raw request body. Params: APIKey (required), TaskName, CountryCode, Locale, Mode (express|extensive), NotifyEmail, NotifyURL (optional). Response: {status: SUCC|FAIL, info: <task id if SUCC>}. Completion is announced via email and/or an HTTP GET to NotifyURL with a taskid query param; the vendor docs do not expose a separate poll/result-fetch endpoint.
Action
Validate Phone NumberValidate a phone number.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.