Workflows — the Visual editor and the new set rules (CRM)

A workflow still has one trigger (when it runs) and one target module. What is new is how its conditions and actions are organized: in sets, checked one after the other from top to bottom.

A set has its own conditions and its own actions. When the conditions match the record, the actions run. Every set that matches runs, unless "Stop after the first matching set" is on.

An if / else-if row: a set (the "if") followed by one or more alternatives (the else-ifs). Only the first alternative whose conditions match runs; the rest of that row is skipped.

An else (optional) The last alternative of a row, without conditions. It runs only when none of the earlier alternatives match. A row with an else is complete: nothing can be added after it, but an else-if can still be inserted before it.

Two editors: The Standard editor lists the sets; the Visual editor draws the same sets on a canvas. Both save the same workflow — switch at any time.

New workflow opens a new workflow in the editor chosen in Workflows settings. The small arrow next to it lets you start in the other editor once; the current default is tagged Default. Opening an existing workflow (its row, or View / Edit in its menu) uses the same editor.

The list header: the workflow scope, Workflows settings and the New workflow button with its arrow.

The arrow offers both editors; the default one is tagged.

Default editor for new workflows — Standard or Visual. New customers start on Visual; existing customers keep Standard until an administrator changes it here. Below it, the existing auto-cancel rule for follow-up tasks is unchanged. Click Save; the New workflow button and the rows follow the choice at once.

The Workflows settings dialog with the default-editor choice on top.

Open a workflow. At the top, Standard | Visual switches between the two editors. Sets are listed under the trigger settings; each has a name, an Enabled switch, conditions (an ALL group and an ANY group), and actions.

The Standard editor: the switch at the top, the sets below the trigger settings.

Add Set offers New set (an independent set) and Else if (an alternative to the set above, starting as a copy of its conditions; the set above needs at least one condition).

An else-if is tagged "Else if" and its "if" is tagged "If". The switch on the tag detaches the else-if into an independent set; its conditions stay.

Move up / down changes the order. Moving an "if" past its else-if (or the reverse) asks first, because their roles swap. Deleting an "if" asks first: its first else-if becomes the "if" and keeps its own conditions and actions.

Save checks the rows: an else-if that is an exact copy of its "if", or an "if" without conditions, is flagged and the save stops until it is fixed. The last alternative of a row may have no conditions — that is the else.

Add Set: New set or Else if.

The canvas is one vertical line: the trigger card, a Sets summary card, then one row per set in the order they are checked, Add set, and End of workflow. Cards are numbered top to bottom. The right-hand rail holds the name, module, status, sequence, delay and notes.

The Visual editor page: the canvas on the left, the details rail on the right.

The full canvas of a workflow with an if/else-if row and a second set below it.

A set is drawn as an If · condition card followed by its Then · action cards and an Add step pill. The condition card shows the conditions in plain words (ALL / ANY) and carries the set's controls:

Click the card → the Conditions dialog (the standard condition builder, ALL and ANY groups, with "N in ALL · M in ANY" in the footer). Save conditions keeps them with the workflow.

The three dots → Edit conditions, Rename set, Disable / Enable set, Duplicate set, Clear conditions, Delete set. The grip at the left → drag the set onto another set to change the order. Dropping an else-if on its "if" swaps their roles (it asks first).

An action card: click it to edit the action; its three dots offer Edit, Turn off / Turn on, Delete.

The Sets card sums up the rows: how many, how they are checked.

The three-dot menu of a set’s condition card.

The Conditions dialog around the standard condition builder.

Add step on a set opens the step chooser:

Condition Edit this set's conditions.

Action: Pick an action type — the list is what this module offers (Send Mail, Send SMS, Create Task, Update Fields, Post API …); the action window opens.

Else if An alternative to the right of this set. Needs a condition on the "if". Else: the row's closing alternative without conditions. Needs a condition on the "if"; one per row.

On an else-if, the chooser offers Action, another else-if (inserted right after that else-if, before any else), and Else. On the else it offers Action only. Add step under the Sets card and Add set under the last row add a new independent set.

Add a step on an else-if.

Add a step on a set.

Add a step under the Sets card: a new set.

Action: the module’s action types.

If / else-if rows and the else

A row is highlighted as one group: the "if" on the line, its alternatives to the right, joined by otherwise (or else for the closing else), and Add else if / Add else at the end of the row. Once the row has an else, both are greyed out.

A saved if / else-if row: the alternatives sit to the right of the if.

A new workflow: an else-if added to the right of Set 1.

The same row with an else at the end: "Add else if" and "Add else" are greyed out.

Add step on the else: Action only. Add step on the else-if: another else-if can still go before the else.

Add set puts a new independent set as a row below the group.

Rules the editor enforces: an else-if needs a condition on its "if"; an else-if identical to its "if" cannot be saved; one else per row; nothing after the else; the first set of a workflow is never an else-if.

The action types are listed on the left by group (Communication, Records & data, Integrations); the chosen type's form appears on the right; Activate this step on save, and Save step stays in view for as long as the form is open. While the window is open, the other types are greyed out — cancel and add another step for a different type.

A new Update Fields action from the chooser: types on the left, the form on the right, the footer in view.

Editing a saved action: the same window, the type it was created with.

The trigger dialog: the standard trigger options.

The details rail: name, module, status, sequence, delay, notes.

Save changes (top right) saves the whole workflow from either editor. Conditions and actions edited in the dialogs are kept with the workflow until you save. Every change to a workflow — save, set added/duplicated/deleted, action saved / turned off / deleted, settings changed — is written to the audit log with who did it and what changed.

Else if / Else disabled: Give the "if" a condition first.

Add else if / Add else disabled. The row already ends with an else. Action types disabled: The action window keeps the type it opened with.

"Save the workflow before adding sets"

A brand-new workflow must be saved once before sets can be added from the canvas.

Something looks wrong? Contact Dazos Support through Help → Support Tickets.