Workflows
Workflow lifecycle
Manage draft, active, paused, and archived workflows, including duplicate and delete actions.
Automation buildersAdministratorsBeginnerAvailable
What this guide covers
- Workflow status controls whether new trigger events can start the saved graph.
- Prerequisites: Permission to edit the Agent Project.
- Result: The Workflows list and canvas show the intended status.
- Limit: The current UI does not expose a full visual version history or rollback interface.
What this is and when to use it
Workflow status controls whether new trigger events can start the saved graph.
| Use it when | Expected outcome |
|---|---|
You need to activate, pause, duplicate, archive, or remove a workflow. | The Workflows list and canvas show the intended status. |
Before you begin
- Permission to edit the Agent Project.
- A valid graph before activation.
Prerequisites
Permission to edit the Agent Project. A valid graph before activation.
Complete the task
- Build and save as draft.
- Test and activate when ready.
- Pause before making risky operational changes.
- Use Duplicate to create a separate copy for experimentation.
- Delete only after checking active executions and dependencies.
Confirm it worked
- The Workflows list and canvas show the intended status.
Common problems
| Symptom | What to check |
|---|---|
Activation is rejected | Resolve validation failures. |
Paused workflow still has an old execution | Pausing prevents new starts; inspect already-started work separately. |
Current limitations
The current UI does not expose a full visual version history or rollback interface.
Product boundary
The current UI does not expose a full visual version history or rollback interface.
Where to go next
Related documentation
Save, activate, pause, and change workflowsMove a validated workflow into Active status and make controlled operational changes.Test a workflowRun a saved workflow with test contact and trigger data while preventing message, database, and external side effects.Workflow failures and debuggingTrace trigger matching, validation, branch decisions, node failures, variables, integrations, and usage.