Configure workflow triggers and steps
Workflow triggers define when a workflow starts, and steps define what the workflow does. This article covers how to configure triggers, build step sequences, and monitor workflow execution.
Audience: Sales managers and administrators who build and maintain workflow automation in AI Lead Manager.
On this page
- Before you begin
- Configure a trigger
- Filter audience on the trigger node
- Workflow node types
- Add an action step
- Add an AI node or API node
- Add a condition (switch) step
- Add a delay step
- Add an end node
- Delete a step
- Connect steps
- Configure goal conditions
- Monitor workflow execution
- Considerations
- Tips
- Troubleshooting
Before you begin
Permission: Edit (under All Leads) β Required to configure workflow triggers and steps.
- Create a workflow first. See Create and publish workflows.
- Notification templates must exist before you can configure Send Email or Send SMS action steps. See Create notification templates.
- Guests must have provided the appropriate consent before SMS messages are delivered. Ensure your organization's consent settings are configured before adding Send SMS steps.
Steps
Configure a trigger
Navigate to Lead Management > AI Lead Manager > Workflows.
Open the workflow in the workflow editor.
Select the trigger node at the start of the workflow canvas.
Select the trigger type:
Trigger When it fires Lead Created A new lead is added to the system from any source. Stage Changed A lead's pipeline stage is updated. Last Contacted Date Updated New communication activity is recorded on the lead. Stale Leads A lead has remained in a non-Won/Lost stage without any activity for a configured period. Won and Lost stages are excluded from stale monitoring; any activity on the lead resets the stale timer. For Stage Changed, select which lead stage(s) trigger the workflow using the Stage selector.
For Stale Leads, configure the Inactive period β enter the minimum number of days of inactivity required to fire the trigger, and optionally a maximum (use the Between condition to define a range). Select the lead stage(s) to monitor.
Optionally, add trigger conditions to narrow which leads activate the workflow. For example:
- Trigger only when the lead source is "Facebook."
- Trigger only when the lead stage changes to "Qualified."
Select Save.
Example β Stale lead re-engagement workflow: Set the trigger to Stale Leads and configure the age range to fire after 14 days of inactivity. Connect it to a Send Email action that sends a re-engagement message, followed by a Create Lead Task action that assigns a follow-up call to the lead owner.
Filter audience on the trigger node
Use the audience filter to restrict which leads activate the workflow based on lead attributes. You can combine up to three conditions using AND or OR logic.
Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
Select the trigger node on the workflow canvas.
Enable the audience filter toggle.
Choose a filter attribute:
Attribute Type Operators Lead Stage Multi-select in, not in Lead Source Multi-select in, not in Lead Type Multi-select in, not in Lead Priority Multi-select in, not in Gender Single-select equals, not equals Select the operator and the value(s).
To add another condition (up to 3), select Add Condition and choose AND (all conditions must match) or OR (any condition can match).
Select Save.
Example: To target only high-priority leads from Facebook, add two conditions: Lead Source in "Facebook" AND Lead Priority in "High".
Important: Audience filters apply to leads at the moment the trigger fires. Workflows do not retroactively process leads that already exist in the system before the workflow is published.
Workflow node types
The workflow editor provides 15 node types organized into four categories:
| Category | Node Type | Description |
|---|---|---|
| Triggers | Lead Created | Fires when a new lead is added from any source. |
| Triggers | Stage Changed | Fires when a lead's pipeline stage is updated. |
| Triggers | Last Contacted Date Updated | Fires when new communication activity is recorded. |
| Triggers | Stale Leads | Fires when a lead has been inactive in a non-Won/Lost stage for a configured period. |
| Actions | Send Email | Sends an email using a notification template. |
| Actions | Send SMS | Sends an SMS using a notification template. |
| Actions | Create Note | Adds a note to the lead's activity timeline. |
| Actions | Create Task | Creates a follow-up task on the lead. |
| Actions | Update Stage | Updates the lead's pipeline stage. |
| Actions | Assign To | Assigns the lead to a specific team member (specific employee or Round Robin). |
| Actions | AI Node | Runs an AI-driven action (advanced β see Add an AI node or API node). |
| Actions | API Node | Makes an external HTTP request (advanced β see Add an AI node or API node). |
| Logic | Condition | Evaluates conditions and routes to different branches. |
| Control | Delay | Pauses the workflow for a specified duration. |
| Control | End | Terminates workflow execution on a branch. |
Add an action step
Action steps execute operations on or related to the lead.
Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
On the workflow canvas, select the + connector between nodes and choose an action node type.
Configure the action. The available actions include:
Action What it does Send Email Sends an email to the lead using a notification template. Choose from Basic (system-provided), Themes (pre-designed), or Custom (user-created) templates. Send SMS Sends an SMS message to the lead using a notification template. The system validates SMS consent before sending. Create Note Adds a note to the lead's activity timeline. Create Task Creates a follow-up task on the lead (see task field details below). Update Stage Updates the lead's pipeline stage from within the workflow. Assign To Assigns the lead to a team member β select a specific employee or enable Round Robin to distribute leads evenly across your team. Configure the step parameters (template selection, note content, field values, and so on).
Select Save.
Create Task field details
When configuring a Create Task step, the following fields are available:
| Field | Description |
|---|---|
| Task type | Select the type of task (for example, Follow-up Call, Send Proposal). Task types are configured in Lead Settings. |
| Task description | Enter a description of what needs to be done (supports multi-line text). |
| Due date | Set the date when the task is due. |
| Due time | Set the time when the task is due. |
| Assign to | Select the team member responsible for completing the task. |
| Priority | Set the task priority level. |
Add an AI node or API node
The canvas also offers advanced AI Node and API Node step types β the AI Node runs AI-driven actions within the workflow, and the API Node makes requests to external systems for custom integrations. These are advanced configurations set up with help from your Zenoti administrator or technical team, and their detailed setup is beyond the scope of this article.
Add a condition (switch) step
Condition steps evaluate expressions and route the workflow to different branches.
Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
On the workflow canvas, select the + connector and choose Condition.
Select the condition type:
Condition Type Evaluates Lead Score The lead's computed score value. Course Completion Whether the lead has completed a specific course. Enrollment Status The lead's enrollment status. Custom Field A custom field value on the lead. Define the comparison (for example, "If lead score is greater than 80, go to Branch A; otherwise, go to Branch B").
Connect each branch to its next step.
Select Save.
Add a delay step
Delay steps pause the workflow for a specified duration.
- Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
- On the workflow canvas, select the + connector and choose Delay.
- Enter a value in the Duration field and select a Unit (minutes, hours, or days).
- The workflow pauses at this step and resumes automatically after the delay expires.
- Select Save.
Note: The maximum delay duration is 1 year (365 days). If a longer pause is required, chain multiple delay steps.
Add an end node
End nodes terminate the workflow execution at a specific branch point.
- Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
- On the workflow canvas, select the + connector and choose End.
- The end node has no output ports β no further steps execute after it on that branch.
- Use end nodes to terminate specific branches in conditional workflows.
Important: Every branch in a workflow must terminate with either an end node or a step with no outgoing connection. Using end nodes explicitly makes the workflow structure easier to read and audit.
Delete a step
- Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
- Select the menu on the step you want to remove.
- Select Delete.
- A dialog appears: "After deleting the Step N node, would you like to connect to the next node or remove all its child events?" Choose one of two options:
- Connect to [next step name] β Removes the selected step and connects the preceding step directly to the next step in the sequence.
- Remove all β Removes the selected step and all downstream steps connected to it.
- Select your choice and confirm.
Important: Choosing Remove all permanently deletes all downstream steps in the branch. Review the branch carefully before selecting this option.
Connect steps
- Each step has a "next step" connection. Select the output connector and drag it to the next step.
- For condition steps, connect each branch to its target step.
- Use end nodes to explicitly terminate branches, or leave the last step without a connection β the workflow completes after executing it.
Configure goal conditions
Goals define conditions that end the workflow early with a "Goal Achieved" status.
- Navigate to Lead Management > AI Lead Manager > Workflows and open the workflow in the editor.
- Select Goals in the workflow editor.
- Define the goal condition (for example, "Lead stage equals Won").
- Select Save. When the goal condition is met during execution, the workflow instance stops immediately β remaining steps are skipped.
Monitor workflow execution
After a workflow is published, you can monitor its execution from the workflow detail page.
Navigate to Lead Management > AI Lead Manager > Workflows.
Open the workflow detail page.
Select the Instances tab to see all workflow instances.
Each instance shows:
Field Description Lead The lead that triggered the workflow. Status Running, Completed, Failed, Goal Achieved, or Paused. Started At When the workflow instance started. Completed At When the instance finished (if applicable). Select an instance to see the step-by-step execution detail. The canvas visualization colors each step by its status: completed steps appear green, failed steps appear red, and scheduled (delayed) steps appear yellow.
Each step detail shows its status, execution time, and result.
Considerations
Keep the following in mind when configuring workflow triggers and steps:
- Workflows do not apply retroactively. A workflow only processes leads that trigger its start event after the workflow is published. Leads already in the system are not affected.
- Versioning. When you edit a published workflow, a new version is created. Workflow instances that are already running continue to completion on the version they started β they do not switch to the new version mid-execution.
- Pause vs. delete. Pausing a workflow prevents new instances from starting, but existing instances continue to run to completion. Deleting a workflow stops all future execution; review active instances before deleting.
- Send Email and Send SMS dependencies. These action steps require a notification template to be selected. Ensure the required templates exist before building the workflow. SMS steps also require that the lead has provided consent.
- Workflow execution is asynchronous. Steps are processed in the background. There may be a short delay between when a trigger fires and when the first step executes.
- End nodes terminate their branch only. In a conditional workflow, placing an end node on one branch does not stop other branches from continuing. Each branch must be terminated explicitly.
- Audience filter limit. A trigger's audience filter supports a maximum of 3 conditions, combined with either AND or OR logic. Nested condition groups are not supported.
- Goal Achieved short-circuit. When a goal condition is met at any point during execution, the workflow instance immediately stops and is marked Goal Achieved β all remaining steps on all branches are skipped.
Tips
- Start simple, then add branches. Build a linear workflow first to verify each step works as expected, then introduce condition nodes to create branches.
- Use the Stale Leads trigger for re-engagement. Configure the stale period to match your organization's follow-up cadence β for example, 7 days for high-priority leads and 21 days for low-priority leads. Pair it with a Send Email action and a Create Task action to ensure every stale lead gets a personal follow-up.
- Use Round Robin assignment to balance workload. When configuring an Assign To step, select Round Robin to distribute incoming leads evenly across your team rather than assigning all leads to a single owner.
- Use audience filters to avoid over-triggering. If a workflow is designed for a specific lead type or source, add an audience filter on the trigger node rather than relying on condition steps inside the workflow. This prevents unnecessary instances from being created for ineligible leads.
- Terminate every branch explicitly. Add an end node to each branch of a conditional workflow so the execution path is unambiguous and straightforward to audit.
- Monitor failed instances promptly. Check the Instances tab regularly and investigate any instances with a Failed status. Common causes include missing notification templates and leads without valid contact details.
Troubleshooting
A workflow is not triggering for new leads.
- Confirm the workflow is in Active (published) status. Draft workflows do not execute.
- Check whether an audience filter is configured on the trigger node. If the filter is too restrictive, no leads will match. Temporarily disable the audience filter to test.
- Verify that the trigger type matches the event β for example, a Lead Created trigger will not fire when a lead's stage changes.
An email or SMS step is not sending messages.
- Confirm a notification template is selected on the step. If no template exists, create one first. See Create notification templates.
- For SMS steps, verify that the lead has provided the required consent. The system does not send SMS messages to leads without valid consent.
- Check the workflow instance step detail for a failure reason.
A delay step is not resuming.
- Delay steps resume automatically after the configured duration. If a step appears stuck, check the workflow instance status in the Instances tab. A status of Paused indicates the delay is still running.
- If the delay has clearly elapsed and the step has not resumed, contact your Zenoti administrator.
A condition step is always routing to the same branch.
- Review the condition field, operator, and value configured on the condition node. Confirm that the lead data you expect to evaluate is actually being set at the time the condition runs (for example, a lead score may not be computed yet at the moment of creation).
- Use a Get Lead Details action step immediately before the condition step to ensure the workflow is evaluating the most current lead data.
Workflow instances show a Goal Achieved status unexpectedly.
- Review the goal condition configured in the Goals section of the workflow editor. If the goal condition is too broad (for example, "Lead stage is not New"), it may match leads earlier than intended.
- Narrow the goal condition or remove it if you want all workflow steps to execute regardless of lead state.