ZenotiHelp

Workflow automation

ZTZenoti Docs Team Updated November 3, 2026 12 min readGuide

Automate lead nurturing and follow-up activities using customizable workflows that trigger on lead events and execute multi-step action sequences.


On this page


Audience: Sales managers and administrators who build and manage lead automation workflows.

Before you begin

Permission: Edit (under All Leads) β€” Required to create and manage workflows.

Steps

Access workflow management

  1. Navigate to Lead Management > AI Lead Manager > Workflows.
  2. The workflow list displays all existing workflows with their current status: Draft, Active, Paused, or Inactive.

Create a new workflow

  1. Select Create Workflow (or From Scratch if you want to start with an empty canvas, or From Template to use a pre-built starting point).
  2. In the Basic workflow info step, configure the following settings:
    • Workflow name β€” Enter a descriptive name for the workflow (maximum 256 characters). For example, "New Lead Welcome Email" or "Follow-up Reminder After 24 Hours".
    • Description β€” Provide details about the workflow's purpose.
  3. In the Center activation step, select the centers where this workflow will run. Select Select centers to choose specific centers, or select all centers.
  4. Select Save as Draft to create the workflow in Draft status, or continue to the canvas to add steps immediately.

Tip: You can also use From Template when creating a workflow to start with a pre-built canvas structure.

Configure the trigger

Each workflow requires exactly one trigger node. The trigger defines the event that starts the workflow.

  1. Select the trigger node on the canvas.

  2. Set the Trigger type:

    Trigger Description
    Lead Created Fires when a new lead enters the system from any source.
    Lead Stage Changed Fires when a lead moves between pipeline stages. Configure the specific stage(s) to watch.
    Last Contacted Date Updated Fires when new communication activity is recorded on the lead.
    Stale Leads Fires when a lead has remained in selected stages without any activity for a configured inactive period. Configure the stage(s) to monitor and the inactive period (minimum days, maximum days, or a specific value). Won and Lost stages are excluded from stale monitoring. Any activity resets the inactivity timer.
  3. For Lead Stage Changed, select the specific stage(s) in Stage that should trigger the workflow.

  4. For Stale Leads, configure the Inactive period condition (equals, greater than or equals, or between) and the number of days, then select the lead stage(s) to monitor.

  5. Select Save.

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.

  1. Select the trigger node on the workflow canvas.

  2. Enable the Filter audience toggle.

  3. 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
  4. Select the operator and the value(s).

  5. To add another condition (up to 3), select Add Condition and choose AND (all conditions must match) or OR (any condition can match).

  6. Select Save.

Example: To target only high-priority leads from Facebook, add two conditions: Lead Source in "Facebook" AND Lead Priority in "High".

Build workflow steps

The workflow builder uses a node-based canvas. Each step displays a "Step N:" prefix on the canvas for identification.

  1. Select the + connector between nodes to add a new step.

  2. A panel shows the available node categories. Select a node type:

    Category Node types available
    Triggers Lead Created, Lead Stage Changed, Last Contacted Date Updated, Stale Leads
    Actions Send Email, Send SMS, Create Lead Note, Create Lead Task, Update Stage, Assign To, AI Node, API Node
    Logic Branch condition
    Control Time Delay, End
  3. Configure the step details in the side panel:

    • Step Name β€” Enter a descriptive name for this step.
    • Action β€” Select the specific action to perform (see step action details below).
    • Parameters β€” Configure action-specific settings.
  4. Connect steps by dragging from one step's output connector to the next step's input.

  5. For Condition steps, define the conditions that determine which branch the workflow follows.

  6. For Time Delay steps, specify the Duration and Unit (minutes, hours, or days) before the next step executes.

  7. Add an End node at the end of each branch to explicitly terminate workflow execution.

Step action details

Send Email

Sends an automated email to the lead using a notification template. Choose the template from one of three tabs:

Tab Description
Basic System-provided templates with standard layouts.
Themes Pre-designed themed templates for common scenarios.
Custom Templates you have created using the notification template editor.

When editing an existing Send Email step, a Current tab shows the template currently assigned to the step.

Note: Send Email steps validate email consent before sending. If the lead or guest has not opted in to receive marketing emails, the step is skipped and recorded as a failed send.

Send SMS

Sends an automated text message to the lead using a notification template. The system validates SMS consent before sending. SMS will be sent to the lead's primary phone number.

Create Lead Note

Adds a note to the lead's activity timeline. Enter the note content in the Note field in the configuration panel.

Create Lead Task

Creates a follow-up task on the lead. Configure the following fields:

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.
Due date Set when the task is due (Immediate, 1 Day, 2 Days, or Custom).
Due time Set the time when the task is due.
Assign to Select the team member responsible for completing the task. Supports Specific employee, Round Robin, or the lead's owner.
Priority Set the task priority level.

You can also choose to notify the assignee when the task is created by enabling Notify the assignee and configuring an SMS or email message.

Update Stage

Updates the lead's pipeline stage from within the workflow. Select the target stage from the Stage dropdown.

Assign To

Reassigns the lead to a specific employee or distributes leads across a team using round-robin rotation. Supports the following assignment modes:

Mode Description
Specific employee Always assigns to the same agent.
Round Robin Distributes leads evenly across a selected pool of agents. Requires a minimum of 2 agents.
Lead owner Assigns to whoever currently owns the lead.
Keep unassigned Leads remain unassigned until an employee claims them.

Note: R-AILM-PAL2-04 β€” Update Stage and Assign To are distinct action nodes. Do not combine them or use "Update Lead" as a node name.

AI Node and API Node

The workflow canvas also includes advanced AI Node and API Node step types for AI-driven actions and custom external integrations. These are intended for advanced configurations set up with help from your Zenoti administrator or technical team; their detailed setup is beyond the scope of this article.

Delete a step

  1. Select the menu on the step you want to remove.
  2. Select Delete.
  3. 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.
  4. 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.

Set workflow goals

  1. Select Goal Definitions to specify success criteria for the workflow.
  2. Define what constitutes goal achievement β€” for example, "Lead stage equals Won" or "Appointment booked".
  3. Select Save. When a goal condition is met during execution, the workflow instance stops automatically and shows Goal Achieved status.

Publish the workflow

  1. Review all workflow steps and connections on the canvas.
  2. If the canvas has validation issues, select Fix Issues to review and resolve them before proceeding. You can also select Publish Anyway if the issues are non-blocking warnings.
  3. Select Publish to change the workflow status from Draft to Active. Only published workflows execute automatically.
  4. The workflow immediately begins processing new trigger events.

Note: If you are publishing changes to an existing active workflow, the button label is Publish Changes. Instances already in progress continue on the previous version; new instances use the updated version.

Monitor workflow execution

  1. From the workflow list, select an active workflow to view its performance.

  2. Select the Instances tab to see individual workflow executions. Each row in the list represents one Workflow instance β€” a single lead's journey through the workflow.

  3. The canvas visualization colors steps by execution status for the selected instance.

  4. Filter instances using the Active, Past, or All tabs.

    Status Description
    Running Currently processing steps.
    Completed Finished all steps successfully.
    Failed Encountered an error during execution.
    Goal Achieved Stopped early because the goal condition was met.
    Paused Temporarily suspended (waiting for a time delay or manual pause).
    Terminated Permanently stopped β€” cannot be resumed.
  5. Select any instance to see step-by-step execution details. Each step shows its status, execution time, and result.

  6. To view step-level communication statistics (triggered, processed, delivered, failed counts) for Send Email or Send SMS nodes, select View Statistics on the relevant step.

Manage workflow versions

When you edit an active workflow and save changes, a new version is created automatically. The previous version continues running for existing instances. New trigger events use the latest published version. Select Versions from the workflow actions menu to see the version history.

Pause or resume workflows

  • To temporarily stop a workflow, select Pause from the workflow actions menu. In the confirmation dialog, review that instances already in progress will continue to completion, and no new instances will be triggered while paused. Confirm by selecting Pause.
  • Select Resume to reactivate a paused workflow. New instances start being triggered again using the latest published version.
  • To permanently stop a workflow, select Delete from the workflow actions menu. All running instances are terminated and the workflow cannot be resumed after deletion.

Zapier integration

Zapier is a workflow automation platform that connects AI Lead Manager with hundreds of third-party applications. Use Zapier to automatically create leads when events occur in external platforms.

Prerequisites

  • An active Zenoti API and Webhooks subscription (contact your CSM to enable).
  • A valid Zapier subscription (Premium plan required for some features like Facebook Lead Ads).
  • Credentials for both Zenoti and the third-party applications you want to connect.

Supported lead sources via Zapier

Zapier supports creating leads from the following platforms:

  • Meta (Facebook Lead Ads)
  • Google Ads
  • Typeform
  • Jotform
  • Webflow
  • Wix
  • Yelp
  • Calendly
  • Webhooks by Zapier (custom sources)

Note: Zapier supports the Create Lead action only. Updating or deleting existing leads via Zapier is not supported.

Create a Zap to capture leads

The typical Zap structure for lead creation is: Trigger (external platform event) β†’ Formatter (optional data transformation) β†’ Zenoti: Create Lead.

  1. Log in to Zapier and select Create Zap.

  2. Set up the trigger:

    • Select the source platform (for example, Facebook Lead Ads).
    • Select the trigger event (for example, "New Lead").
    • Connect your account for the source platform.
    • Configure trigger settings (select the page, form, or campaign).
    • Test the trigger to verify it finds a recent lead.
  3. Set up the action:

    • Search for and select Zenoti.
    • Select the Create Opportunity action.
    • Connect your Zenoti account (select Live environment, enter your account name from your Zenoti URL).
    • Map the required fields:
    Field Requirement
    Email or Phone At least one is required.
    Center ID Required β€” select the center where the lead is created.
    Country Required for phone number validation.
    First Name / Last Name Recommended for lead identification.
    Employee Optional β€” assign the lead to a team member for follow-up.
    • Optionally select Create Zenoti Guest if it doesn't exist yet to auto-create a guest record.
  4. Test the action and select Publish Zap.

Review and troubleshoot failed Zaps

  1. In Zapier, navigate to Task History to review all Zap executions.
  2. Failed tasks show the failure reason. Common reasons include:
    • Missing required fields (email or phone, Center ID, country).
    • Invalid Center ID.
    • Duplicate lead detection.
  3. Fix the configuration issue and re-run the failed task from Task History.

Tips

  • Use templates to get started faster. When creating a workflow, select From Template to start from a pre-built canvas with common trigger and action combinations already configured.
  • Test with a small audience first. Use the audience filter on the trigger node to limit the workflow to a specific lead source, type, or stage before enabling it for all leads.
  • Rename workflow nodes for clarity. Give each step a descriptive name (for example, "Send Welcome Email - Day 1") so the canvas is easier to read and maintain, especially in complex workflows.
  • Create notification templates before building the workflow. Send Email and Send SMS steps require an existing template. Having templates ready avoids incomplete workflow configurations.
  • Review the Stale Leads trigger settings carefully. The inactivity timer resets on any activity (stage change, outbound email, outbound SMS). Configure the inactive period to match your team's expected follow-up cadence.

Troubleshooting

  • Workflow is Active but no instances are being created. Verify that the trigger conditions are set correctly and that leads are actually meeting the trigger criteria. Check whether an audience filter is excluding all leads. Confirm that the workflow is applied to the correct centers.
  • Send Email or Send SMS step shows Failed for an instance. The lead or linked guest may not have opted in to receive marketing messages, or may be missing a valid email address or phone number. Review the step's execution result in the instance detail view and update the lead's contact information or consent status as needed.
  • Workflow shows Draft status after saving. Select Publish on the canvas to activate the workflow. Saving a workflow creates or updates the draft β€” it does not publish automatically.
  • A step is skipped in the execution history. Switch (Condition) steps route execution to a branch based on evaluated conditions. If the lead's data did not match any branch condition and no default (else) branch was configured, execution ends silently at that step. Add an else branch or an End node to handle unmatched conditions.
  • The Publish button is not available. The canvas may have unresolved validation errors. Select Fix Issues to view the list of problems. Common issues include a missing End node on a branch, an unconnected step, or a Send Email step with no template selected.

Considerations

  • Workflows do not retroactively process leads that existed before the workflow was published. Only events that occur after the workflow becomes Active trigger new instances.
  • Each workflow instance runs on the version that was active when the instance started. Editing and republishing a workflow creates a new version β€” in-progress instances complete on the version they started.
  • Pausing a workflow stops new instances from being created, but existing running instances continue to completion. Deleting a workflow terminates all running instances immediately and cannot be undone.
  • Send Email and Send SMS steps require both a valid notification template and lead or guest consent. Ensure consent is captured via a lead capture form before relying on these steps.
  • Workflow execution is asynchronous. After a trigger event fires, there may be a brief delay before the first step executes.
  • The End node has zero output ports β€” no further steps execute after it. Include an End node at the terminal point of every branch to explicitly mark where execution stops.
  • The audience filter on a trigger supports up to three conditions with AND or OR logic. Conditions cannot be nested.
  • When a goal condition is met mid-workflow, the instance status changes to Goal Achieved and no further steps execute, even if additional steps remain in the sequence.
Was this article helpful?
Your feedback helps us improve our documentation.