Workflow template ยท GoHighLevel

Test a GoHighLevel workflow before activation

Use this worksheet before activating a lead-follow-up workflow. It helps you check the trigger, actions and stop conditions with contacts you control. It is a manual test plan, not an importable snapshot, and it does not send messages.

  • 2 min read
  • 8 sections
  • Updated October 9, 2026
On this page

Compatibility

Manual GoHighLevel test plan. Not an importable snapshot or workflow JSON. Use a test sub-account and controlled contacts.

How to use it

  1. Download the worksheet and record the workflow name, owner, current configuration and expected actions.
  2. Keep the candidate unpublished. Use a test sub-account where possible and only destinations you control.
  3. Run each relevant case, inspect execution history and record expected versus observed results without customer data.
  4. Get approval before activation. Keep the prior configuration and review queued actions if you need to roll back.

Example

What you get

A reviewable test record with matching, excluded, repeated, suppressed and failed cases.

Limits

  • Your HighLevel account features, phone setup and regional requirements affect the actual workflow.
  • This checklist does not establish legal permission to contact someone.
  • Disabling a workflow cannot recall messages already sent.

Download

The file is our own work, under the MIT license. Download ghl-workflow-test-plan.md.

# GoHighLevel workflow test plan

Workflow name:
Owner:
Account and version/date:
Trigger and filters:
Expected actions:
Allowed test contacts:
Stop condition:

## Before activation
- Duplicate or export the current configuration where supported.
- Keep the candidate workflow unpublished while checking conditions.
- Confirm communication consent and suppression rules.
- Use your own controlled test contact and phone/email destination.

## Test cases
1. Matching trigger: expected action happens once.
2. Non-matching trigger: no action happens.
3. Repeated trigger: no unintended duplicate message.
4. Opt-out or suppression: no outbound communication.
5. Missing field: safe fallback or an explicit stop.
6. Failure: inspect execution history and record the error.

## Evidence and release
Record time, anonymized test case, expected result and observed result.
Do not publish until the owner approves the results.
Rollback: disable the candidate and restore the recorded prior configuration. Check for actions already queued; disabling does not undo a sent message.

Status

Version 1.0.0, updated 2026-10-09. Review status: reviewed. Original instructions reviewed and file structure validated locally. Client installation and account-specific execution are not certified.

Sources

Build it with people who already did.

Join the free community: weekly live calls, a start here course and builders in your language.

Join free on Skool