Workflows automate repeatable business steps such as inbound inquiry follow-up, approval requests, notifications, and agent runs. Some workflows are shipped by Vertiqa or by a Pipeline Pack; admins can also use the workflow builder for supported workflow types.
What's on the page
- Workflow list — available workflow definitions, their status, and where they came from.
- Create workflow — start a supported workflow definition.
- Builder entry — open a workflow canvas for editing triggers, actions, validations, and publish review.
- Run history — inspect executions, node timelines, retry/cancel actions, and failure details.
How this differs from automations
- Automations are yours — you define the trigger and steps.
- Workflows are governed definitions — they can be shipped by a pack or built in the workflow builder, then published and observed through the workflow run surfaces.
Builder basics
The builder is Full-mode setup. It supports a canvas, add-node menu, configuration panel, validation panel, autosave, keyboard support, and a publish-review dialog. Mobile users can monitor workflows, but desktop is the intended authoring surface.
For a worked example, use Build a workflow for Inquiry Received.
Tips
- Read publish warnings carefully. Workflows can create approvals, notifications, tasks, and agent runs.
- Use run history when a workflow behaves unexpectedly. Node timelines show where execution stopped.
- Pack-installed workflows should stay aligned with the pack unless you intentionally replace the operating model.