Use the workflow editor
Navigate the visual canvas, configure nodes, manage branches, and work confidently with undo, redo, and saved changes.
Plan availability #
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Active workflows | 3 | 10 | 45 | Unlimited |
Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.
Read the canvas #
The trigger is your starting point. Nodes connect below it, with branch labels showing possible outcomes. Select a node to see its configuration in the inspector. The visible connections describe where execution goes next; their placement alone does not explain why a branch is chosen.
Use the available canvas navigation and zoom controls to keep the part you are editing in view. On a small screen, focus on one section at a time and read long fields in the inspector.
Add and configure a node #
Use the add control on a free branch. Search or browse the node picker, choose a node, and fill in the inspector fields. Use the variable picker to refer to existing outputs instead of typing guessed variable names.
Name important nodes so their outputs are recognizable later. After renaming, check any dependent references and validation messages before saving.
Undo and redo #
| Action | Windows / Linux | macOS |
|---|---|---|
| Undo an editor change | Ctrl Z | ⌘ Z |
| Redo an editor change | Ctrl Shift Z or Ctrl Y | ⌘ Shift Z |
The editor also provides undo and redo controls. These commands affect editor history; they cannot recall an email, undo a sent message, or reverse a database write performed by a workflow run.
Making a new edit after undoing starts a new history direction. Use Save when you are happy with the restored configuration. Treat history as part of the editing session, not as a permanent backup system.
Pause, copy, or change a step #
Node controls let you pause a node, copy its configuration, or change its type where offered. Read the confirmation before changing a node with outputs or branches used elsewhere.
- Pausing a node preserves its configuration but changes how new runs pass through it.
- Copying a node moves its configuration into a new instance; it is separate from copying an entire workflow.
- Custom node types package a reusable set of steps with a defined input contract.
Handle unsaved changes #
If you navigate away with unsaved changes, the editor can offer choices to save, leave, or stay. Check the save result before closing the page. If the application detects conflicting or invalid changes, resolve the message rather than assuming a save completed.
Check before activation #
Inspect all branches, required Properties, account selections, and any paused nodes. Confirm the trigger and Line assignment. Then use a controlled test and inspect the run in Workflow Activity.