OpenClaw · Skill
GoHighLevel
You have access to the Hylo GHL knowledge API. Use it when the user asks about GoHighLevel (GHL / HighLevel / Go High Level) workflows, API endpoints, UI navigation, or automation planning.
Install
Start with the primary install command. Alternate entrypoints are included below for ClawHub and OpenClaw CLI users.
Primary command
clawhub install dasonshi/hylo-ghlClawHub installer
npx clawhub@latest install dasonshi/hylo-ghlOpenClaw CLI
openclaw skills install dasonshi/hylo-ghlDirect OpenClaw install
openclaw install dasonshi/hylo-ghlWhat this skill does
You have access to the Hylo GHL knowledge API. Use it when the user asks about GoHighLevel (GHL / HighLevel / Go High Level) workflows, API endpoints, UI navigation, or automation planning.
Why it matters
Live API lookups against 494 schemas mean answers reflect current GHL structure, not outdated documentation or guesswork.
Typical use cases
- Planning a lead nurture workflow in GoHighLevel
- Looking up the correct API endpoint for contact or opportunity updates
- Finding the right trigger for a form submission automation
- Navigating to a specific feature inside the GHL dashboard
- Validating a trigger-action sequence before deploying it
Source instructions
You have access to the Hylo GHL knowledge API. Use it when the user asks about GoHighLevel (GHL / HighLevel / Go High Level) workflows, API endpoints, UI navigation, or automation planning.
Setup
If $HYLO_API_KEY is not set or any call returns 401: -> "You need a Hylo API key. Sign up at hylo.pro (7-day free trial)."
If 403: -> "Your trial has expired. Subscribe at hylo.pro/dashboard." If 404: -> "I couldn't find that resource. Try a broader search term." If 429: -> "Rate limit reached. Try again tomorrow or upgrade at hylo.pro/dashboard."
API (bash + curl)
Base: https://api.hylo.pro/v1
Auth: -H "Authorization: Bearer $HYLO_API_KEY"
| Need | Endpoint |
|---|---|
| Search actions | GET /actions?q=KEYWORD |
| Search triggers | GET /triggers?q=KEYWORD |
| Search API schemas | GET /schemas?q=KEYWORD |
| Full schema detail | GET /schemas/{name} |
| GHL UI navigation | GET /navigate/{feature} |
| Full UI protocol | GET /protocols/{feature} |
| Plan a workflow | POST /templates/workflow -d '{"objective":"..."}' |
| Validate workflow | POST /validate -d '{"trigger":"...","actions":[...]}' |
For category/feature lists: cat {baseDir}/reference/endpoints.md
Rules
- ALWAYS call the API -- don't guess about GHL. Your knowledge may be outdated.
- Summarize JSON responses naturally -- never dump raw output.
- For workflow planning: call /templates/workflow FIRST, then /schemas for details.