THE RESULT YOU'RE WORKING TOWARD
Done means it works.
You can identify the first failing step and demonstrate a successful retest after the correction.
Practice project: Harbor Demo01 / GET READY
Before you start.
- Platform / editor
- HighLevel sub-account; feature availability varies by account
- Access & plan
- Authorized demo sub-account and relevant user permissions. Calendar, messaging and AI features may require additional plan access or usage charges. No purchase is part of these guides.
- Starting point
- Complete the previous lesson or use an equivalent prepared demo project.
Keep a note of the exact account, project and version you use. Work with demo data and record the expected result before making changes. Never place passwords, verification codes or private customer records in your evidence.
02 / LEARN THE TOOL
Open the official walkthrough.
Use the publisher's instructions and available screenshots to locate the current controls. Then return here for the SETLY exercise and its result checks. These links open on the publisher's website.
Source credit belongs to the named publisher. These are external references, not SETLY recordings or a claim of affiliation. Screen names and plan availability can change.
03 / PUT IT INTO PRACTICE
Your task, step by step.
Use one labelled demo record or project so you can find your work again. Finish each action before continuing; if the screen differs, consult the matching official source rather than guessing.
- 01
Step 1
Select one labelled test contact and record the trigger event and expected actions. Open the relevant workflow's history or execution view.
- 02
Step 2
Follow the contact through the actions in time order. Distinguish skipped, waiting, successful and failed steps.
- 03
Step 3
For the first unexpected step, inspect its inputs, condition and error detail. Correct that cause before modifying later steps.
- 04
Step 4
Retest with a fresh contact or deliberate re-entry and compare the new execution to the original. Keep both outcomes in the test notes.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If no execution exists, inspect entry conditions and activation first; debugging later actions cannot fix a missing trigger.
My screen is different from the guide
Check the product, editor, account role and selected project first. Open the credited official instructions for your version. Record the difference and pause any action whose effect you cannot verify.
The screen looks correct, but the result is missing
Inspect the saved record, published page or execution log that should prove the action. A preview, success message or draft is not always evidence that data was stored or a message was delivered. Retest with one unique demo value.
05 / PROVE THE RESULT
Check it before you call it done.
You can identify the first failing step and demonstrate a successful retest after the correction.
Keep useful evidence
Record the test date, project/version, expected result, observed result and a non-sensitive screenshot or record reference. Mark anything you did not test as untested. Your checkmarks do not certify an untested result.
Download the editable verification checklist ↓Guide status: original written practice exercise with credited external references. SETLY screen recording and independent learner reproduction are not yet complete.