Workflow Builder and Automation Engine in HighLevel

Everything in HighLevel that happens automatically, happens because a workflow is running. This is the engine behind all of it.

Reading time: approximately 10 minutes.

What Is the HighLevel Workflow Builder?

The Workflow Builder is HighLevel’s automation engine. Every automated action that happens in the platform – a follow-up text after a form submission, a reminder email before an appointment, a pipeline stage update when a payment is received – is powered by a workflow running in the background.

A workflow is a sequence of tasks that executes automatically when a defined event occurs. You build it once.

It runs without manual intervention every time the trigger conditions are met.

HighLevel workflows replaced the legacy Campaigns and Triggers tabs in April 2024. Those features are deprecated and no longer available.

All automation now lives in the Workflow Builder.

The builder is accessible at Automation > Workflows in any HighLevel sub-account. Every plan includes it with full access to standard triggers and actions.

Workflow Triggers: What Starts a Workflow

A trigger is the event that enrolls a contact into a workflow. When the trigger condition is met, HighLevel adds the contact to the workflow and begins executing actions in sequence.

HighLevel has over 60 triggers organized into categories. Multiple triggers can be added to the same workflow, each bringing contacts in from a different entry point.

Every trigger supports filters – conditions that must also be true for the trigger to enroll a contact. A filter converts a broad trigger into a precise one.

The Call Status trigger fires on all calls by default. A filter for Status equals Missed Call converts it to a missed-call-only trigger, leaving all other call types unaffected.

Filters are not optional. Without them, most triggers are too broad to be useful.

Workflow Actions: What the Workflow Does

Actions are the tasks the workflow performs after the trigger fires. They execute in the order they appear on the canvas, top to bottom.

HighLevel has over 70 actions organized into categories.

Every action is named individually. The name you give an action appears on the canvas and replaces the generic action type label in Execution Logs.

Descriptive names make troubleshooting significantly faster on any workflow longer than five or six steps.

Flow Control: If/Else, Goal, Wait, and Split Test

Flow control actions determine how contacts move through a workflow, when they advance, and which path they take. These four are the ones that separate basic workflows from genuinely useful automations.

Wait

The Wait action pauses a contact at a specific point for a set duration before advancing to the next action. Set the wait in minutes, hours, or days.

You can also set it to wait until a specific date or until a condition becomes true.

Every time-based sequence – a 7-day email nurture, a 30-day onboarding sequence, a same-day appointment reminder – is built with Wait actions between communication steps. Contacts stay in the workflow during the wait period and advance automatically when the timer expires.

If/Else

The If/Else action creates a conditional branch. Set a condition – for example, Tag Contains: Hot Lead.

Contacts who meet it follow the Yes branch. Contacts who do not follow the No branch.

Conditions can test contact fields, tags, custom values, pipeline stage, appointment status, previous action results, and many other data points. Stack multiple If/Else actions to create multi-segment routing within a single workflow, rather than building a separate workflow for each contact type.

Goal

The Goal action watches for a specific event during a contact’s time in the workflow. When that event occurs – even if the contact has not reached the Goal step yet – the contact is advanced directly to the Goal step and continues from there.

A common use: a lead enters a nurture sequence. Halfway through the sequence, they book an appointment.

A Goal action watching for Appointment Status: Booked pulls them forward to the post-booking confirmation sequence, skipping the remaining nurture messages. The contact gets the right communication at the right time without manual intervention.

Split Test

The Split Test action divides contacts between two or more branches so you can compare different messages, sequences, or paths. Set the split percentage for each branch.

Review Stats Mode on the canvas to compare performance across branches. Use this to test subject lines, message timing, SMS versus email, or entirely different follow-up sequences.

Workflow Settings

The Settings tab inside every workflow controls how the workflow handles contacts and communication timing. These settings apply to the entire workflow, not individual actions.

Stop on Response is the setting most commonly missed on new workflows. Without it, a workflow will continue sending automated messages even after a team member is actively engaged in a live conversation with the contact.

Execution Logs and Enrollment History

Execution Logs and Enrollment History are the diagnostic tools for understanding exactly what happened to every contact that entered a workflow.

Execution Logs

Click the Execution Logs tab inside any workflow to see a per-contact, per-action record of every execution. Each row shows the contact name, the action name, the timestamp, and the status – fired, skipped, or errored.

Errors are highlighted for immediate visibility.

Click View Details on any row to open the full execution details for that contact and action. Click Go to Action inside the details view to jump directly to that action in the workflow builder, with the configuration panel open and ready to fix.

Enrollment History

The Enrollment History tab shows why each contact entered and exited the workflow. Exit statuses include Workflow Completed (contact reached the end naturally), Removed by Workflow Action (a Remove From Workflow action fired), and Removed by External Workflow Action (a different workflow removed the contact).

Click Highlight Contact Path on any enrollment to open the workflow canvas with the exact path that contact took visually marked. This is the fastest way to understand a complex execution – you see which branches fired and which were skipped for that specific contact without reading every log entry.

What You Can Automate With It

• Lead follow-up sequences – automatically send a series of SMS and email messages to a new lead the moment they submit a form, with Wait actions pacing messages over 7 to 14 days and Stop on Response ending the sequence when they reply
• Appointment confirmation and reminders – trigger on Appointment Status: Booked to send a confirmation immediately, then use Wait actions to send reminders 24 hours and 1 hour before the appointment, automatically personalized with the appointment time via custom values
• Pipeline automation – update opportunity stages, apply tags, and send internal notifications automatically when contacts move through the sales pipeline, removing the manual CRM updates that slow down sales teams
• Post-purchase onboarding – trigger on Payment Received to enroll buyers in a structured onboarding sequence delivering setup instructions, check-ins, and milestone communications over the first 30 to 90 days
• Re-engagement campaigns – use a Stale Opportunity trigger or a scheduled tag to enroll dormant contacts in a re-engagement sequence that attempts to revive a conversation before the contact is marked as lost
• Review requests – automatically send a review request to contacts 24 to 48 hours after a completed appointment or service delivery, using the Review Request action to drive Google and Facebook reviews without manual follow-up
• Internal team notifications – fire an Internal Notification action when a high-value lead fills a form, a contract is signed, or a payment above a threshold is received, ensuring the right team member is alerted immediately
• B2B account-level automation – use Company-Based Workflows to trigger on Company Created or Company Changed events, updating company fields and syncing data to associated contacts for B2B onboarding and account management

Key Definitions

Use Cases by Industry

Home Services (HVAC, Plumbing, Roofing)

A roofing company captures leads from a web form on their site. The moment the form is submitted, a workflow fires: an immediate SMS says a team member will call within minutes, an Internal Notification alerts the nearest sales rep, and a Call action auto-dials the rep and connects them to the lead when answered.

If the rep does not answer, a voicemail drop goes to the lead explaining what to expect next. A Wait action holds for 30 minutes, then a follow-up SMS fires.

Stop on Response means the sequence stops the moment the lead texts back.

Outcome: Every new lead receives a response in minutes. No lead falls through because someone forgot to follow up.

The sales rep’s phone rings the moment a hot lead comes in.

Dental and Medical Practices

A dental practice books appointments through their HighLevel calendar. When Appointment Status: Booked fires, a workflow sends an immediate confirmation email with the appointment details and a link to intake forms.

A Wait action holds until 24 hours before the appointment, then sends an SMS reminder. Another Wait holds until 2 hours before, then sends a second SMS.

If the appointment status changes to No Show, a separate If/Else branch fires a no-show re-booking sequence. If it changes to Completed, a Wait action holds 48 hours, then sends a review request via the Review Request action.

Outcome: No-show rates drop because patients receive timely reminders. Review count grows because every completed appointment triggers a review request automatically.

Real Estate

A real estate agent runs Facebook ads that feed leads into HighLevel via a form. The Contact Created trigger fires and enrolls the lead in a 14-day nurture sequence.

The sequence uses an If/Else to split contacts by whether they have a tag indicating they own a home or are renting, sending different content to each segment.

A Goal action watching for Appointment Status: Booked pulls any lead who books a call straight to the pre-consultation sequence, skipping the remaining nurture emails. The Create Opportunity action fires on enrollment to add the lead to the Active Leads pipeline stage.

Outcome: Every lead enters a personalized follow-up sequence immediately. Leads who take action are promoted forward without waiting for the nurture to finish.

The pipeline stays current without manual CRM updates.

Marketing Agencies

An agency uses HighLevel for client onboarding. When a contract is signed (Documents and Contracts trigger with Status: Signed filter), a workflow fires: a welcome email goes to the client, an Internal Notification alerts the account manager, a task is created for the kick-off call, and the opportunity stage updates from Proposal Sent to Active Client.

A 30-day onboarding drip sequence delivers setup guides, check-ins, and milestone messages using Wait actions. A Custom Webhook Premium action fires on day one to create the client project in their project management tool.

Outcome: Onboarding is consistent across every new client. Nothing is forgotten.

The account manager’s to-do list updates automatically and the client receives a professional experience from the first signature forward.

Coaches and Course Creators

An online coach sells a 12-week program. When Payment Received fires, a workflow enrolls the buyer in the post-purchase onboarding sequence: welcome email, login instructions, and a community invite on day one.

A series of Wait actions and emails deliver weekly content prompts, check-ins, and motivational messages throughout the program.

An If/Else midway through the sequence checks whether the buyer has the “Week 6 Complete” tag. Those who do receive an advanced content email.

Those who do not receive a re-engagement nudge encouraging them to catch up.

Outcome: Every buyer gets the same structured onboarding experience regardless of when they purchased. Engagement is tracked via tags and the workflow responds differently to active and inactive students without manual monitoring.

Who Is This For?

How to Build a Workflow in HighLevel

Step 1: Open the Workflow Builder

Go to Automation in the left navigation, then select Workflows. Click Create Workflow in the top-right corner.

Choose Start from Scratch for a custom build, select a Recipe to use a pre-built template, or click Build Using AI to generate a workflow from a plain-language description.

Step 2: Add a Trigger

Click Add New Trigger. Browse or search the trigger panel.

Select the trigger that matches your entry event. Give it a descriptive name in the Workflow Trigger Name field – this name appears in Execution Logs.

Multiple triggers can be added to the same workflow for multiple entry points.

Step 3: Add Trigger Filters

Click Add Filters on the trigger. Set the conditions that must be true for the trigger to enroll a contact.

Filters narrow a broad trigger into a precise one. A missed-call follow-up workflow needs the Call Status trigger filtered to Missed Call, not all calls.

Save the trigger after configuring filters.

Step 4: Add Actions

Click the + icon below the trigger. Select the first action from the panel.

Configure it completely – for a Send SMS action, write the message and confirm the sender number. Give the action a descriptive name.

Continue adding actions in sequence. The canvas builds top to bottom in the Standard Builder, or freeform in the Advanced Builder.

Step 5: Add Wait Steps for Timing

Between communication actions, click + and add a Wait action. Set the duration.

For a 3-day follow-up email, add a Wait of 3 Days between the first and second email actions. Contacts pause at Wait steps and advance automatically when the duration expires.

Step 6: Add If/Else for Branching

Click + and add an If/Else action. Set the condition – a tag, a field value, a pipeline stage.

The canvas splits into a Yes branch and a No branch. Add the appropriate actions to each branch.

Stack multiple If/Else actions for multi-segment routing.

Step 7: Configure Workflow Settings

Click the Settings tab inside the workflow. Enable Stop on Response for all lead follow-up workflows.

Enable Allow Re-entry if contacts may enter more than once. Set a Time Window to restrict SMS and calls to business hours.

Confirm the Timezone setting.

Step 8: Test Before Publishing

Click Test Workflow in the top-right corner. Select a test contact.

Review the Execution Logs after the test to confirm every action fired as expected. For the most accurate test, publish and trigger the workflow with a real test contact rather than reusing the same contact repeatedly, as repeated tests with the same contact can produce unexpected results.

Step 9: Publish and Monitor

Click Publish to make the workflow live. Monitor Execution Logs for the first cohort of real contacts.

Use Highlight Contact Path to visually verify that contacts are following the intended branches. Use Go to Action to fix any action generating errors without leaving the execution details view.

How It Connects to the Rest of HighLevel

• Advanced Workflow Builder – the freeform canvas mode of the Workflow Builder, adding Trigger Go-To connections, Delinked Nodes, Disable Nodes, and a full set of canvas organization tools for complex multi-trigger and multi-branch automations
• Workflow Version History – records every saved state of a workflow in the builder. Restore any past version as a new draft without affecting the live published workflow. Browse up to 10 versions or 30 days of history per workflow.
• Tag-Based Automation – the Contact Tag trigger and Add/Remove Tag actions are among the most used in HighLevel. Tags applied by one workflow can trigger other workflows, creating a modular automation architecture where workflows pass contacts between sequences based on behavior
• Appointment Reminders – appointment reminder workflows are one of the most common use cases for the Workflow Builder, using the Appointment Status trigger with Wait actions and Send Email/SMS actions to deliver timed confirmation and reminder sequences
• Multi-Channel Campaigns – all multi-channel automation sequences including SMS, email, voicemail, calls, Facebook Messenger, Instagram DM, and WhatsApp are built and managed inside the Workflow Builder using the communication actions available in each channel’s category

Common Questions

To Wrap It Up

The Workflow Builder is where HighLevel’s value is actually realized. The CRM, the calendars, the conversations inbox, the pipeline – they all feed data into workflows and receive updates back from them.

Without workflows running, most of the platform is manual.

The core structure is straightforward: a trigger enrolls a contact, actions execute in sequence. Everything else – If/Else, Goal, Wait, Split Test, Settings, Premium Features – is about making that basic structure more precise, more responsive, and more powerful.

Getting Workflow Settings right from the start – especially Stop on Response and Time Window – prevents the most common problems agencies and businesses run into when going live with automation.

1. Start with one workflow that solves one clear problem – new lead follow-up is the highest-impact first build for most businesses – before trying to automate everything at once
2. Name every trigger and action descriptively before saving – generic names make Execution Logs nearly useless for troubleshooting
3. Enable Stop on Response on every lead follow-up workflow from day one – it is the setting most frequently missed and most frequently responsible for automation-damaging customer relationships
4. Use Trigger Filters on every trigger – an unfiltered trigger enrolls far more contacts than intended and creates noise in both execution logs and contact records
5. Test with a real contact on a published workflow at least once before sending real leads through – the Test Workflow button has limitations that a live test reveals

A workflow built correctly runs quietly in the background and makes you look like you have a full team behind every touchpoint – even when it is just you.