The Workflow Builder is a visual automation tool. You draw what should happen — something starts it, conditions are checked, actions run — and ActiveManage carries it out against your records.
Find it at Architect Panel → Automation → Workflow Builder.
The parts of a workflow
- A workflow has a name, the datastore it acts on, what starts it, and a status of active, disabled or draft.
- Nodes are the steps, dragged onto the canvas from the palette.
- Connections join them. A condition has two outgoing connections — one for true, one for false.
- A run is one execution against one record, recorded step by step so you can see exactly what happened.
When to use it, and when not to
Reach for a workflow when the logic has branches, delays or several steps — that is what a diagram expresses well. For a single unconditional action when a record is saved, a table rule is simpler and easier for the next person to follow.
Read the node reference first
Three node types — e-mail, approval and webhook — do not yet perform their real action. That is much better known at the design stage than after you have built something around them. See Workflow Node Types.
Worked Examples
- Service desk: on a high-priority case, set an SLA due date, notify the on-call team and escalate if untouched after two hours.
- Sales: when a quotation is accepted, create the order, link it back to the quotation and start the fulfilment checklist.
- HR: on a new starter record, create the onboarding sub-tasks and set the probation review date.