Build on a visual canvas
Add and connect nodes, configure their inputs, and arrange the flow around the process. Undo changes as you work and inspect the settings of each step.
Workflow Builder
Turn a process into a workflow.
Build workflows visually with triggers, connected systems, and AI steps. Test your changes, publish a version, and follow each execution in VictorHub.
Support ticket enrichmentExample
Step 3 of 4
Give the agent the ticket context and instructions to produce a useful summary.
Select a step to explore this example.
Make every step explicit.
A business process often crosses several systems. Bring its triggers, decisions, and actions onto one canvas so you can see how information moves and what happens next.
Start from an event or a schedule
Use a webhook to respond to an incoming request, or a schedule to run recurring work. Test a workflow from the builder while you develop it.
Route and transform your data
Use conditions, branches, and loops to choose what happens next. Map values with expressions and use code when a process needs custom logic.
Put AI inside the process
Add AI steps to interpret, summarise, or work with incoming information. Configure a model and connect tools to an agent when it needs to take action.
Connect the systems you use
Combine integration actions and HTTP requests to read information and send results back. Configure each step with the credentials its system requires.
Inspect what actually happened
Follow execution history and inspect the inputs, outputs, and errors of individual steps. Use that record to find where a process needs attention.
From draft to production
Save your work. Publish when it’s ready.
The canvas holds your draft. Production runs the version you publish. You can keep editing while the published workflow continues to run.
- 01
Build and test
Run the draft and inspect the result. Tests use the configured connections, so use test accounts or data for actions that change external systems.
- 02
Validate and publish
Publishing checks the workflow for structural and configuration errors before registering its triggers.
- 03
Review and revise
Inspect executions, improve the draft, and publish the next version. Version history lets you return to an earlier version when needed.
A few practical questions.
Do I need to write code?
You can build with visual nodes, integration actions, and expressions. Code nodes are available for custom logic that goes beyond the configured steps.
Does saving a change update the live workflow?
No. Saving updates the draft. Production continues to use the published version until you deliberately publish a change.
Can a workflow use other workflows?
Yes. Sub-workflows let you reuse a process inside another workflow. An AI agent in a workflow can also use a configured sub-workflow as a tool.
Can I investigate a failed run?
Yes. Execution history records the run and its steps, including outputs and errors. Retry settings and error workflows let you define how failures should be handled.
Bring a process you want to automate.
Tell us which systems are involved and what the result should look like. We can walk through how to build it in VictorHub.
Agent Identity
An agent belongs to a company and has a purpose you define. Its instructions, connected credentials, and selected tools shape how it responds and which actions it can take.