Workflow automation overview
Workflow automation in AI Lead Manager lets you create automated sequences of actions that trigger when lead events occur. Instead of manually sending follow-up emails, creating tasks, or updating lead records, you can build workflows that handle these actions automatically.
How workflows work
A workflow consists of a trigger, a set of steps, and optional goal conditions. When the trigger event occurs — such as a new lead being created — the workflow engine evaluates the trigger conditions and, if they match, executes the steps in sequence.
Each workflow runs independently for each lead that matches the trigger conditions. You can have multiple active workflows running simultaneously, each handling different scenarios.
Triggers
Workflows start when a specific lead event occurs. AI Lead Manager supports four trigger types:
| Trigger | When it fires |
|---|---|
| Lead created | A new lead is added to the system from any source (manual, integration, form, expiry, or API). |
| Stage changed | A lead's pipeline stage changes. |
| Last contacted date updated | A lead's last contacted date is updated, indicating new communication activity. |
| Stale leads | A lead has remained in selected stages with no activity for a configured age range. Configure the stage list and the minimum/maximum stale age (in days) on the trigger node. |
Each trigger supports an audience filter that restricts which leads activate the workflow. You can add up to three conditions using AND or OR logic, filtering by lead stage, source, type, priority, or gender.
Node types
Workflows are built from 15 node types organized into four categories:
Trigger nodes (4 types)
Trigger nodes define what starts the workflow:
- Lead Created -- Fires when a new lead is added from any source.
- Stage Changed -- Fires when a lead's pipeline stage is updated.
- Last Contacted Date Updated -- Fires when new communication activity is recorded.
- Stale Leads -- Fires when a lead has been stale (no activity) for a specified age range in selected stages.
Action nodes (8 types)
Action nodes perform operations on or related to the lead:
- Send Email -- Send an email to the lead using a notification template with dynamic macros.
- Send SMS -- Send an SMS message to the lead using a notification template.
- Create Lead Note -- Add a note to the lead's activity timeline.
- Create Lead Task -- Create a follow-up task assigned to the lead owner.
- Update Stage -- Change the lead's pipeline stage when this step is reached.
- Assign To -- Reassign the lead to a specific employee or use round-robin assignment from a configured pool.
- AI Node -- Use artificial intelligence to select the optimal communication channel (Auto Channel Selector mode) or determine the best next action (Task Selection mode) based on engagement data.
- API Node -- Make an HTTP request to an external system with configurable method (GET, POST, PUT, DELETE, PATCH), headers, authentication (None, Bearer Token, Basic Auth, API Key), and body for custom integrations.
Logic nodes (1 type)
- Condition -- Evaluate expressions and route the workflow to different branches. Supported condition types: lead score, course completion, enrollment status, and custom field values.
Control nodes (2 types)
- Delay -- Pause the workflow for a specified duration before continuing.
- End -- Terminate workflow execution at a specific point. The End node has no output ports. Use End nodes to explicitly terminate workflow branches.
Notification templates
Workflow email and SMS steps use notification templates to define the message content. Templates support dynamic macros that are automatically replaced with lead-specific data when the message is sent.
Available template channels:
| Channel | Description |
|---|---|
| HTML email templates designed with a built-in visual editor, supporting subject line, body, and merge tags. | |
| SMS | Text message templates with macro support. |
| WhatsApp message templates. | |
| Push | Push notification templates. |
Templates support 15+ macros including lead name, email, phone, assigned employee, lead source, stage, type, priority, center name, and more. The macro catalog is extensible and does not require application updates to add new macros.
Workflow lifecycle
Workflows progress through four states:
| Status | Description |
|---|---|
| Draft | The workflow is being designed and is not yet active. Leads do not trigger it. |
| Active | The workflow is live. Matching lead events trigger new workflow instances. |
| Paused | The workflow is temporarily disabled. No new instances are created, but existing running instances continue to completion. |
| Inactive | The workflow is permanently disabled. |
Workflow instances
Each time a workflow triggers for a specific lead, a new workflow instance is created. The instance tracks:
- The lead that triggered it.
- The current execution state and step outputs.
- The status: Running, Completed, Failed, Goal Achieved, or Paused.
You can monitor workflow instances from the workflow detail view, where the canvas shows each step's execution status.
Workflow versioning
When you edit an active workflow and save changes, a new version is created. Existing running instances continue using the version that was active when they started. New trigger events use the latest version.
Goal conditions
Workflows can define goal conditions that are evaluated during execution. If a goal condition is met (for example, the lead reaches the Won stage), the workflow instance is marked as "Goal Achieved" and stops further execution.
Automation rules vs. workflows
AI Lead Manager provides two separate automation mechanisms:
| Feature | What it does |
|---|---|
| Automation rules | Simple if-then rules that automatically change a lead's stage when a Zenoti Core event occurs (service booked, membership purchased). Configured in Settings. |
| Workflows | Full multi-step automation with a visual canvas, 15 node types, conditional branching, delays, AI nodes, API nodes, and audience filters. |
Use automation rules for straightforward stage transitions. Use workflows for complex, multi-step automation with branching logic.