Home/HighLevel/Features/Workflows/HighLevel ticket automation: building and applying workflows

Workflows and Automation

HighLevel ticket automation: building and applying workflows

In short

Ticket workflow automation lets you use Workflows to assign tickets, change fields, send replies, add internal notes and notify team members. Each workflow runs on the ticket that triggered it, so actions affect only that specific request. You can also manually enroll tickets or use SLA based triggers.

AreaWorkflows · Ticketing
Used forIT support firm, Ecommerce store, Healthcare clinic
Setup steps16 steps in 3 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Support managers need to route new requests automatically to the correct agents, ensuring each ticket follows the right process.
  • Customer success teams use ticket actions to send standard replies and log internal notes without leaving the platform.
  • Operations leaders rely on SLA based triggers to alert staff before service targets are missed.

02Ticket automations, explained

The feature lives inside the Automation area of HighLevel. From Settings > Automation you can create, edit and publish workflows that start when a ticket is created, updated, a customer replies, or an SLA warning or breach occurs. Each workflow receives the ticket that caused the enrollment, so actions such as updating fields or sending replies act only on that ticket.

Workflow actions specific to tickets include creating a new ticket, finding an existing one, updating properties, assigning owners, adding internal notes, and sending email replies. Triggers and actions are selected from the action picker and can be filtered by ticket properties like priority, category, status, or assignee. Conditions and custom value pickers let you branch logic and insert ticket data into messages.

You can also enroll an existing ticket manually. From a ticket’s detail view or the ticket list page you can add the ticket to any published workflow, which then processes the ticket using the same actions and conditions as an automatically triggered workflow.

03How businesses use ticket automations

  • IT support firm. When a new support request arrives, the firm creates a workflow with the Ticket Created trigger filtered by category. The workflow automatically assigns the ticket to the appropriate specialist and sends an acknowledgment reply using the ticket's email thread.
  • Ecommerce store. The store sets up an SLA Breached trigger to monitor order related tickets. If the SLA is missed, the workflow sends a notification to the manager with the ticket ID, priority and a link, allowing quick escalation.
  • Healthcare clinic. Clinicians use the Add internal note to ticket action inside a workflow that runs on Ticket Updated. When a patient updates their appointment request, the workflow records a team only note with the new details while leaving the patient unaware.

04Before you start

  • Create any needed SLA policies and configure their warning behavior before using SLA triggers.
  • Publish the workflow you intend to enroll tickets into; only published workflows appear in the Add to workflow picker.

05How to set up and use ticket automations in HighLevel

Create a ticket workflow

  1. Navigate to Settings > Automation and select Create workflow.
  2. Enter a descriptive name for the workflow that reflects its purpose.
  3. Choose the ticket trigger that matches the scenario and set any filter criteria.
  4. Pick a ticket action, notification or condition from the action picker and add it to the canvas.
  5. Fill out the action fields and use the custom value picker to pull values from the ticket or contact.
  6. Examine the branch logic and confirm the correct ticket and contact contexts are used.
  7. Save the draft, run a test with a sample ticket, and review the execution history for expected results.
  8. When the test behaves as intended, publish the workflow.

Add an existing ticket to a workflow from a ticket

  1. Open the ticket you want to enroll.
  2. Click Ticket actions in the top panel.
  3. Choose Add to workflow.
  4. Search for the published workflow you wish to use and select it.
  5. Confirm the selection and click Add.

Add existing tickets to a workflow from the list page

  1. Mark the desired tickets with their checkboxes and click Add to workflow on the bulk toolbar.
  2. Check the count of selected tickets and the workflows you chose, then confirm the operation.
  3. Note that each ticket provides its own context; review the workflow’s re entry settings and execution records for customers with multiple tickets.

06What it looks like in HighLevel

07Settings that matter

  • Ticket Created. Starts a workflow when a new ticket is opened; filters can narrow it by priority, category, status, assignee or name.
  • Ticket Updated. Triggers a workflow when a ticket changes; you can specify change conditions such as a field becoming a certain value.
  • Customer Replied with Ticket as the reply channel. Runs a workflow when a customer adds a reply to a ticket, using the ticket channel and optional ticket filters.
  • SLA Warning. Initiates a workflow as a service target approaches its deadline; must align with a configured SLA policy.
  • SLA Breached. Activates a workflow when an SLA target is missed; filters can target specific policies.
  • Create ticket. Creates a new ticket with defined fields and associates it with a contact.
  • Find ticket. Searches for a ticket using conditions and provides separate paths for found and not found results.
  • Update ticket. Modifies properties on the ticket that is currently in context.
  • Assign ticket. Routes the ticket to selected users based on the action’s assignment options.
  • Add internal note to ticket. Adds a team only note to the ticket without sending an email to the customer.
  • Send email reply to ticket. Sends a reply that appears in the ticket’s email thread and is visible to the customer.

08Things to know before you rely on it

  • Ticket Updated triggers generated by actions inside a workflow are suppressed to prevent infinite loops; do not rely on repeated updates as a substitute for explicit workflow logic.
  • Only workflows that are published appear in the Add to workflow enrollment picker.

09If something goes wrong

  • A workflow is missing from Add to workflow. Confirm that the workflow is published and belongs to the intended subaccount.
  • A ticket event does not start the workflow. Check the publication state, trigger filters, event type, and enrollment/re entry settings.
  • An action affects an unexpected ticket. Review the triggering ticket and verify whether a Find ticket action changed the context.
  • Create ticket is skipped. Ensure the enrollment includes the required contact and examine execution log details.
  • A reply is not sent. Verify the email integration, ticket context, recipient, required action inputs, and execution result.
  • An SLA notification is missing. Check the SLA policy, target, warning or breach event, and the configured notification action.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Ticket automations are a small convenience that can become a real shift for teams that juggle many support requests.

Get More InformationOpens on HighLevelPublished November 11, 2026 · Updated November 17, 2026

Common questions

Common questions about ticket automations.

Do I need a separate ticketing automation engine?

No. Ticketing automation is built into HighLevel Workflows.

Can I start a workflow for an existing ticket?

Yes. Use the Add to workflow option from the ticket view or from the ticket list page.

Can one customer's tickets be handled differently?

Yes. Each ticket’s properties and enrollment context allow separate routing and handling.

Does an internal note action email the customer?

No. Internal notes stay team only; use the Send email reply to ticket action for customer facing messages.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.