Workflows script how AIUNIFY Chat reacts to defined visitor messages instead of relying on a normal generated Agent response for every turn.
The deployed interface describes Workflows as a way to script common responses and hand a visitor to a human on specific keywords.
An Active Workflow is evaluated before the normal LLM response path.
When a Workflow matches the visitor turn, the Workflow can handle that interaction with its configured steps rather than continuing through the ordinary AI answer process.
Select Workflows from the workspace navigation.
The Workflows table provides search, status scope, sorting, configurable columns, and a New workflow action.
The interface uses three primary statuses:
Only an Active Workflow is intended to fire for visitor traffic.
Draft is appropriate while a Workflow is still being built or reviewed.
A Draft Workflow remains stored but does not run for live visitor messages.
Active means the Workflow is eligible to run when its trigger conditions match.
Activate only after the trigger and all required steps have been reviewed.
Disabled keeps the Workflow configuration available without allowing it to fire.
This is useful when temporarily suspending an existing flow without deleting it.
The Workflows table can display:
Use Search workflows... to find a Workflow by name or applicable search terms.
The scope control supports:
The Workflows list provides sorting choices including:
Select the Workflow Name or its Settings action to open the Workflow Canvas.
The Canvas is the visual editing surface for the Workflow's trigger and connected steps.
The delete action asks:
Delete "[name]"? This cannot be undone.
Use deletion only when the Workflow should be permanently removed. Use Disabled instead when you may need the flow again later.
Because a matching Active Workflow can take precedence over the normal Agent reply, test the Workflow before activating it. Broad trigger keywords can unintentionally intercept visitor questions that should have been answered by the Agent normally.