Activities overview
How activities and activity packages work in VeloPhex, which packs are supported and how they reach Studio and Robots.
An activity is one step in a workflow: read a cell, click a button, add a queue item. An activity package (or pack) is the NuGet package that ships a group of related activities. Every activity you use in Studio comes from a package. Studio itself ships no activities; with no package installed, the toolbox holds only the workflow language's built-in nodes (Sequence, Flowchart, State Machine, If, Assign, Try Catch and the other control-flow nodes).
Which packages ship#
VeloPhex activity packages fall into four groups.
Core packs. Signed by VeloPhex and supported:
| Package | What it covers |
|---|---|
VeloPhex.System.Activities |
Logging, files and folders, compression, data tables, collections, text and regular expressions, dates, dialogs, processes, environment, clipboard and PowerShell |
VeloPhex.UIAutomation.Activities |
Desktop applications and web browsers: find, click, type, read, navigate, extract tables, OCR text |
Velophex.Excel.Activities |
Workbooks, sheets, cells, ranges and CSV files, without Microsoft Excel installed |
VeloPhex.Orchestrator.Activities |
Assets and credentials, queues, jobs and storage buckets, plus the Action Hub and Data Hub activities |
Every new project gets VeloPhex.System.Activities and VeloPhex.Orchestrator.Activities.
The Core profile. The Studio and Robot installers carry the core packs in their offline feed, together with VeloPhex.Testing.Activities (verification and test data activities for test projects) and Velophex.Sap.Activities (SAP GUI Scripting, and BAPI and RFC calls). VeloPhex.UIAutomation.Core is a supporting library that UI Automation depends on. It contains no activities and is installed as a dependency. The Core profile is the supported set.
Connector packs. Packs that talk to another system, such as Web API, Mail, PDF, Database, Microsoft 365, Salesforce, ServiceNow, Slack or Microsoft Teams. They are published to the activities feed, but they are not in the installers' offline feed and not part of the supported Core profile.
Stub packs. Packs whose activities are not implemented yet. They are not shipped.
See the activity catalog for the full list of packages and activities.
How packages reach your project#
- Studio installs packages from its own offline feed, the
feedfolder next to Studio (%LOCALAPPDATA%\Programs\Velophex\Studio\feedfor a per-user install,%ProgramFiles%\Velophex\Studio\feedper machine). A new project getsVeloPhex.System.ActivitiesandVeloPhex.Orchestrator.Activitiesautomatically. Add UI Automation, Excel and others from the Package Manager. See Manage packages. - The project records each direct package in
project.jsonand pins the whole resolved closure, with content hashes, inproject.lock.json. A project never floats to a different version between restores. - The Robot carries the same Core profile packs in its own offline feed (
%ProgramFiles%\VeloPhex\Robot\feed) and restores what a job needs from there. It also restores from one additional package source, your tenant's package feed on the Orchestrator by default.
Because both Studio and the Robot have the Core profile packs offline, a machine with no internet access can build and run automations that use them.
Scopes#
Activities that work with a live resource, such as a browser session or an open workbook, are grouped in a scope: Use Application/Browser, Use Excel File. The scope opens the resource, the activities inside it use it, and the scope always releases it at the end, whether the body succeeded, failed or was canceled. Use Application/Browser opens either kind of target. An activity that needs a scope and is placed outside one is reported as a design-time error.
Capabilities#
Each package declares the capabilities its activities need: FileSystem, Network, Browser, Process, Credentials or UiAutomation. Studio shows them when you install a package, and warns explicitly when an unsigned package asks for UiAutomation or Credentials. Each activity also declares a risk level (None, Low, Medium or High); an activity that declares none is treated as unknown, not harmless.
Capabilities are a consent signal
Capabilities tell you what a package intends to do. They are not a sandbox. Activities run in the workflow executor process with that process's rights, and a package can do anything its code does. Install only packages you trust, and use signing to control where packages come from.
Trust and signing#
A package with a VeloPhex id (VeloPhex.* or Velophex.*) must carry the VeloPhex signature; one that does not is refused. Packages you build yourself may be signed with your organization's certificate, or installed from a package source you mark as trusted in Studio. See Signing packages.
Orchestrator activities and local runs#
The Orchestrator activities call the Orchestrator's runtime API. On a Robot they use the job's token. In a run from Studio they work as a design-time run when you are signed in to the Orchestrator and a workspace is selected; they then act as you. See Run and debug workflows. The Action Hub and Data Hub activities also need that product turned on for your tenant.
Next steps#
- Activity catalog
- Signing packages
- Build your own activities: Activity SDK
Which packages ship
How packages reach your project
Scopes
Capabilities
Trust and signing
Orchestrator activities and local runs
Next steps