Event triggers
Start from a defined change such as a payment, due date, record update, or supported external event.
Available with setupDevelopers / Automation
VirtusCloud automation work defines the trigger, decision, action, approval, retry, and human fallback as one operational process—not as an invisible chain of shortcuts.
Talk to our teamGeneral self-service automation is locked in the portal. Specific workflows can be assessed with support.
What changes for your team
Reduce repeat handoffs
Keep approvals explicit
Handle failures deliberately
Retain human control
Capabilities
Start from a defined change such as a payment, due date, record update, or supported external event.
Available with setupRun agreed periodic checks or operational tasks on a controlled schedule.
Available with setupApply documented business rules before the workflow changes data or notifies a user.
Available with setupPause higher-risk work for a person to review before execution.
Available with setupDefine what happens when an external service or action fails.
Available with setupA general customer-facing automation builder is not currently unlocked.
Planned — contact supportEnd-to-end workflow
Start with a measurable handoff rather than trying to automate an entire department.
Document conditions, approval needs, timeouts, and the human fallback.
Record the workflow state and surface failures instead of silently dropping work.
Measure completion, exceptions, and time saved before expanding scope.
Where it fits
Flag or notify the responsible user when an invoice reaches an agreed condition.
Route a record to the right reviewer before a higher-risk action.
Respond to a supported event and update the next operational system with traceable status.
Questions
No. The Automation item is currently locked and directs users to support for assessment.
Not by default. Approval gates and explicit fallback are part of the workflow design where risk requires them.
Continue exploring