Anis Mahmud Anik

How to test a GoHighLevel workflow before it goes live

A workflow diagram with a test contact moving along a highlighted path.

Short answer

Click Test Workflow in the builder, pick a test contact and run the test, then read the result in Execution Logs and Enrollment History. HighLevel says the test is not 100 percent reliable, so also run a published, live test with a contact you control. A draft workflow never acts for real.

What is the safest way to test a workflow?

Use test contacts that you control. Give them your own email address and phone number, label them clearly, and never use a real prospect. HighLevel’s builder guide does not say whether a test run sends real messages, so assume it does.

Draft and published are different states. A draft workflow does not trigger or take actions for real. Publishing is what makes it live. Save is not publish.

How do you run a test in the builder?

  1. Open the workflow.
  2. Click Test Workflow in the top right.
  3. Select a contact.
  4. Click Run Test.

HighLevel warns that this test “isn’t 100% perfect, especially if you reuse the same contact for multiple tests”, and recommends publishing and testing live when you need certainty. Treat the button as a quick check and the live run as proof. Use a fresh test contact each time.

Where do you read the result?

Go to Automations, Workflows, open the workflow, then Execution Logs. You will see each action a contact went through, with the time and its timezone.

  • Execution Logs show every action. A failed action is highlighted, and View Details opens the row. You can filter by action and by date, up to 30 days at a time.
  • Enrollment History shows each enrollment and how it ended: Workflow Completed, Removed by Workflow Action, or Removed by External Workflow Action.
  • Highlight Contact Path opens the builder and marks the route a contact took, including skipped nodes and errors.
  • Go To Action opens the failing action so you can fix it.
  • Trigger Stats show attempted, matched and unmatched contacts, with a reason for each unmatch, see why a workflow is not triggering.

What should a test prove?

Four things: the right event started it, the contact took the intended path, each action produced the right result, and the workflow stopped when it should. One clean run proves only the happy path.

How do you test the trigger?

Create the exact event once and confirm one entry in the log. Then create a nearby event that should not start the workflow. A form trigger filtered to one form should ignore a different form. Repeat the event once to see whether a second run is intended.

How do you test branches?

Build a matrix. Include a record for every branch, one that matches none, and one with missing data. For a score with three bands, test below the first band, on each boundary, inside the middle and above the top. Check the end state, not just the message: tags, owner, stage and fields.

How do you test waits and stop conditions?

Waits are where workflows drift. HighLevel notes that if you edit a Wait action while a contact is already waiting, that contact finishes the existing wait first. Changes to actions after the wait apply when the contact reaches them. Contacts in a wait also stay at their step when you resume a draft.

Ask of each wait:

  • If the contact books during the wait, should the workflow stop?
  • If they reply or opt out, what ends?
  • If the deal is won or lost, should it exit?
  • Does the next message respect business hours?

Goal events let a contact skip ahead, so test one that should fire and one that should not.

What should the pre-launch checklist say?

  1. The trigger is specific and tested.
  2. Every branch passed once.
  3. Missing values have an outcome.
  4. Messages reach only the people you intend.
  5. Waits and stops behave when records change.
  6. A repeat trigger does not duplicate actions.
  7. Updates hit the right contact or opportunity.
  8. Someone owns monitoring, and knows how to unpublish.

Frequently asked questions

Is testing the first action enough?

No. The first action can pass while a later condition fails.

Can I test with a real contact?

Avoid it. A live contact can receive a message or have records changed.

Do I need to publish to test properly?

For certainty, yes. HighLevel recommends a live test with a contact you control, because the Test Workflow button is not fully reliable.

If you want your automations tested and documented before launch, see the services page or book a free 30-minute call. For pipeline design, read pipelines vs workflows.

Sources: HighLevel Help: Workflow builder walkthrough; HighLevel Help: Execution Logs and Enrollment History. Checked against the Help Center on 29 October 2026.

Want this set up for you?

30 minutes, a clear next step.

Anis Mahmud Anik

HighLevel Certified Admin. I set up and automate GoHighLevel for founders and owners.