VeloPhex Action Hub

When an automation reaches a decision it should not make alone, it raises a typed task. Someone claims it, fills in the form and picks an action, and the automation gets the decision as data and carries on.

People decide, robots carry on

An automation raises a task, a person decides, and the decision comes back as typed data.

Wait days without a robot

Continuations start a new job when the task is completed.

Part of one platform

Tasks belong to Orchestrator workspaces and use its roles. Flow Studio user tasks raise them too.

Robots that guess

Exceptions go to a person with the data they need.

Approvals in email

Typed forms, queues and a recorded outcome that cannot change.

Idle robots waiting

The job ends and a continuation picks up after the decision.

Duplicate tasks on retry

A correlation key returns the existing task instead of a second one.

Finance teams

Approve invoices over a limit before a robot posts them.

Operations reviewers

Check extracted data before it reaches a system of record.

Automation developers

Add a human decision to a workflow or a Python automation.

Action apps

Forms with request fields, response fields and action buttons, published as numbered versions.

Typed outcomes

The action a reviewer picks comes back to the automation as typed data.

Group queues and claiming

Queue tasks for a group. Any member claims a task, and only they can complete it.

Task inbox

Search, claim, comment on and complete tasks. Managers reassign, queue and cancel in bulk.

Workflow and Python support

Raise a task from a Studio workflow or a Python automation.

Continuations

Finish the automation in a new job when the task is completed, so no robot waits for days.

Workspace-scoped access

People see only tasks in workspaces they can see. Completed decisions cannot be changed.

VeloPhex Studio

The Windows IDE for building automations: a visual designer for sequences, flowcharts and state machines, C# expressions with IntelliSense, a live debugger, UI element capture, Git and publishing to Orchestrator.

VeloPhex Robot

The Windows agent that runs workflow and Python automations, next to a person or in the background. It connects to Orchestrator outbound only, proves its identity with its own key pair and verifies every package before it runs.

VeloPhex Orchestrator

The control plane for your automation estate: tenants and workspaces, jobs, queues with SLAs, triggers, encrypted assets and credentials, a package feed per tenant, Robot fleets and an append-only audit log. Run it on-premises, in the VeloPhex cloud or in a dedicated cloud managed by VeloPhex.

VeloPhex Python SDK

Write automations as typed Python functions. The SDK turns type hints into input and output schemas, gives your code assets, secrets, credentials and queues at run time, and packs it into the same package format as Studio workflows.

VeloPhex Launchpad

The automation pipeline in Orchestrator. People submit ideas, reviewers assess and score them, approvers decide, delivery teams build them, and Launchpad measures the benefit from the automation's own runs.

VeloPhex QA Hub

Quality management inside Orchestrator: releases, requirements, versioned test cases, test sets, executions on your Robots and defects, with coverage and reports in one project.

VeloPhex Flow Studio

Draw BPMN flows that combine robot tasks, people's tasks, timers and messages. A flow waits between steps for minutes or days without holding a robot, and every published version is pinned for the instances that run it.

VeloPhex Flow Monitor

See how many flow instances are running, which stopped at an incident and how each step performs against its target, then resolve incidents, retry in bulk or migrate instances to a newer version.

VeloPhex Agents

Build an agent from instructions, a model and the tools it may use: your processes and your vector stores. It runs as a job on your Robots, records every step and stops for a person's approval before a process tool call.

VeloPhex Data Hub

Keep business records such as invoices, vendors or claims in typed entities in a workspace. Workflows, Python automations, people and other systems all read and write them through one API.