ZenotiHelp

Create and publish workflows

ZTZenoti Docs Team Updated June 26, 2026 3 min readGuide

Workflows automate repetitive sales actions. Create a workflow to define what happens when a lead event occurs — such as sending a welcome email when a new lead is created, or creating a follow-up task when a lead's stage changes.

Before you begin

Permission: Edit (under All Leads) -- Required to create and manage workflows.

Steps

Create a workflow

  1. Navigate to Lead Management > AI Lead Manager > Workflows.

  2. Select Create Workflow.

  3. Enter the workflow details:

    Field Description
    Name A descriptive name for the workflow (for example, "New Lead Welcome Email", "Follow-up Reminder After 24 Hours").
    Description An optional description of what this workflow does.
    Trigger The event that starts this workflow. See Configure workflow triggers and steps.
  4. Select Create. The workflow is created in Draft status.

Build the workflow

  1. On the workflow canvas, add steps to define the sequence of actions.
  2. Connect steps by defining which step follows each one.
  3. Configure each step's action and parameters. See Configure workflow triggers and steps for details on step types.
  4. Optionally, enable the Filter audience toggle on the trigger to restrict which leads activate this workflow (filter by stage, source, type, priority, or gender with up to 3 conditions using AND/OR logic). See Configure workflow triggers and steps for details.
  5. Optionally, define goal conditions that stop the workflow early when met.
  6. Use End nodes to explicitly terminate specific workflow branches where needed.
  7. Select Save to save your changes.

Publish the workflow

  1. Review the workflow steps and configuration.
  2. Select Save, then select Publish to change the status from Draft to Active. Only published workflows execute automatically.
  3. The workflow begins processing matching lead events immediately.

Manage workflow status

Action Result
Publish The workflow starts processing. New lead events that match the trigger create workflow instances.
Pause No new instances are created. Existing running instances continue to completion.
Resume The paused workflow starts accepting new trigger events again.
Delete The workflow is removed. Running instances are not affected.

Rename a workflow

  1. On the workflow detail page, select the workflow name.
  2. Enter the new name.
  3. Select Save.

Workflow versioning

When you edit an active workflow and save changes, a new version is created. The new version becomes the active version, and the previous version is retained for reference. Existing running instances continue using the version that was active when they started.

Considerations

  • A workflow only fires for leads that match its trigger event AND its audience filter (if one is configured). Activating a workflow does not retroactively process leads that already exist.
  • Each edit to an active workflow creates a new version. Running instances continue on the version they started with; only new trigger events use the latest version.
  • Pausing a workflow stops new instances from being created but does not interrupt instances that are already running. Use Delete to remove the workflow entirely.
  • A workflow with a Send Email or Send SMS step requires a notification template configured for the matching channel. Steps fail if the referenced template has been deleted or disabled.
  • Send Email and Send SMS steps respect lead consent. If a lead has not opted in (or has opted out), the step is skipped and recorded as a failure on the instance.
  • Workflows execute asynchronously through Kafka queues. Expect a short delay (seconds to a minute) between the trigger event and the first step running. Time Delay nodes are scheduled exactly; they do not poll.
  • An End node has no output ports. Once execution reaches an End node on a branch, that branch is finished; other branches in the same workflow continue independently.
  • Audience filters support a maximum of 3 conditions combined with AND or OR. Filters cannot be nested.
  • Goal conditions evaluate during execution. When met, the instance is marked Goal Achieved and stops -- subsequent steps on that instance do not run.
Was this article helpful?
Your feedback helps us improve our documentation.