GHL Browser Automation Skill

You interact with the GoHighLevel web application through Chrome to build, edit, and verify workflows. Since GHL does not expose workflow CRUD via its REST API, browser automation is the only way to create and modify workflows programmatically.

Primary Tool: Claude in Chrome

Use Claude in Chrome (/chrome) as the primary browser interaction method. This leverages the user's existing GHL login session — no separate authentication needed.

Why Claude in Chrome over other tools:

• Uses the user's existing authenticated session (no credential management)
• Can see and interact with the full GHL UI including the visual workflow builder
• Supports screenshot capture for verification
• No additional MCP server setup required

Fallback tools (if Claude in Chrome is unavailable):

• Chrome DevTools MCP — programmatic DOM access
• Browser MCP — Playwright-based automation
• Manual guidance — describe steps for user to execute

Core Capabilities

1. Navigation

Navigate the GHL single-page application (SPA) to reach any workflow-related section:

• Dashboard → Automation → Workflows (main workflow list)
• Workflow list → specific workflow (click to open builder)
• Workflow builder → trigger node, action nodes, settings panel
• Workflow stats → enrollment, active, completed counts

Always verify navigation succeeded by checking the URL or page content after each navigation step. GHL is a React SPA — URL changes happen via client-side routing, not full page loads.

2. Workflow Creation

Two approaches, chosen based on complexity:

AI Builder Approach (preferred for 5+ steps):

1. Navigate to Automation → Workflows
2. Click "Create Workflow"
3. Select "AI Workflow Builder" option (or "Start from Scratch" if AI Builder unavailable)
4. Paste the composed AI Builder prompt (from ghl-ai-builder skill)
5. Wait for AI to generate the workflow structure
6. Review generated structure against the design plan
7. Refine: fix triggers, adjust wait times, correct conditions, update message content
8. Save and optionally publish

Manual Approach (for simple workflows or when AI Builder fails):

1. Navigate to Automation → Workflows
2. Click "Create Workflow" → "Start from Scratch"
3. Name the workflow following naming convention
4. Add trigger: click trigger area → select trigger type → configure filters
5. Add actions one by one: click "+" → select action category → select specific action → configure parameters
6. Configure If/Else branches: add condition → set YES/NO paths → add actions to each branch
7. Configure Wait steps with exact durations
8. Save and optionally publish

3. Workflow Editing

Modify existing workflows:

1. Navigate to workflow list
2. Find and open the target workflow
3. Screenshot current state for reference
4. Make changes: add/remove/modify nodes, update parameters, change conditions
5. Screenshot updated state for verification
6. Save changes

4. Workflow Verification

After building or editing, verify the workflow:

1. Screenshot the full workflow canvas
2. Walk through each node and verify against the design plan
3. Check trigger type and filters
4. Check all action parameters (message content, wait durations, tag names)
5. Check If/Else conditions and both branch paths
6. Check workflow settings (name, allow reentry)
7. Check publish status (draft vs published)

Interaction Patterns

Click Targets in GHL

GHL uses React components with dynamic rendering. When clicking:

• Wait for elements to render before clicking — GHL panels often animate in
• Use visible text labels as click targets when possible (more reliable than CSS selectors)
• Dropdowns: Click the dropdown trigger, wait for options to render, then click the desired option
• Modals: After triggering a modal, wait for it to fully appear before interacting
• Side panels: Configuration panels slide in from the right — wait for the animation to complete

Form Filling

When filling GHL configuration forms:

• Text fields: Click the field, clear existing content, type new value
• Dropdowns/selects: Click to open, search or scroll for the option, click to select
• Toggle switches: Click to toggle — verify the state changed
• Rich text editors: Click into the editor area, use keyboard shortcuts for formatting if needed
• Merge fields: Type {{ to trigger the merge field picker, or type the full merge field path directly (e.g., {{contact.first_name}})

Screenshot Strategy

Take screenshots at these key moments:

1. After navigation — confirm you reached the right page
2. Before changes — capture the current state as a reference
3. After each major action — verify the action was applied (node added, field saved)
4. After completion — capture the final workflow for user review
5. On error — capture error messages, modals, or unexpected states

Allow 1-2 seconds after actions for UI transitions/animations to settle before capturing.

Error Recovery

Common errors and recovery strategies:

Error	Detection	Recovery
Session expired	Login page appears, "Session expired" message	Pause workflow. Ask user to log back in. Resume from last successful step.
Modal blocking	Unexpected modal or dialog appears	Screenshot the modal. Dismiss it (click X or Cancel). Retry the intended action.
Wrong workflow opened	Workflow name doesn't match target	Navigate back to workflow list. Search for correct workflow by name.
Element not found	Click target not visible on screen	Scroll the page. Check if a panel needs to be opened. Verify navigation is correct.
Save failed	Error toast or validation message	Screenshot the error. Check for missing required fields. Fix and retry save.
AI Builder timeout	Spinner persists beyond 30 seconds	Refresh the page. Try again with a shorter prompt. Fall back to manual building.
Unsaved changes warning	Browser prompt about leaving page	Accept if intentional. Cancel and save first if changes should be kept.

Session Management

• Do not attempt to log into GHL — rely on the user's existing session
• Check session validity at the start of any browser operation by navigating to the dashboard
• If session is expired, immediately stop and ask the user to log in
• Avoid rapid sequential navigation — allow pages to load fully between navigation actions
• Tab management: Work in a single tab. Do not open multiple GHL tabs (can cause session conflicts)

Workflow Builder Canvas Interaction

Understanding the Canvas

The GHL workflow builder is a visual canvas with:

• Trigger node at the top — the entry point
• Action nodes connected vertically in sequence
• If/Else nodes that split into YES (left/green) and NO (right/red) branches
• Wait nodes shown with a clock icon
• Connection lines between nodes showing flow direction
• "+" buttons between nodes for inserting new actions
• Settings icon (gear) for workflow-level settings (name, reentry, etc.)

Adding Nodes

To add a new action after an existing node:

1. Hover over the connection line below the node (or click the "+" button)
2. The action picker appears — organized by category
3. Select the category (e.g., "Communication", "Internal Tools")
4. Select the specific action (e.g., "Send SMS", "If/Else")
5. Configuration panel opens on the right — fill in parameters
6. Save/close the configuration panel

Configuring If/Else

If/Else nodes require:

1. Click the If/Else node to open configuration
2. Set the condition type (contact field, tag, activity, etc.)
3. Set the field, operator, and value
4. Name the condition descriptively
5. Close configuration
6. Add actions to the YES branch (click "+" on the left/green path)
7. Add actions to the NO branch (click "+" on the right/red path)
8. Ensure both branches end with an action or "End" node

Configuring Wait Steps

Wait nodes support three types:

1. Time Delay: Set duration (number + unit: minutes/hours/days)
2. Wait for Event: Select event type, set timeout duration
3. Wait Until Time: Set specific time of day, select days of week

Integration with Other Skills

With workflow-design Skill

The workflow-design skill produces a structured workflow plan. This skill translates that plan into browser actions:

1. Receive the workflow plan (trigger, actions, conditions, settings)
2. Determine build approach (AI Builder vs manual)
3. Execute the build via Chrome
4. Verify the result matches the plan

With ghl-ai-builder Skill

The ghl-ai-builder skill produces an optimized prompt. This skill handles:

1. Navigate to the AI Builder interface
2. Paste the composed prompt
3. Wait for generation
4. Review and identify gaps between the generated workflow and the design plan
5. Refine by manually adding/editing/removing nodes

Pre-Flight Checklist

Before starting any browser automation:

• User is logged into GHL in Chrome
• Correct GHL sub-account is selected
• Workflow design plan is approved by user
• AI Builder prompt is composed (if using AI approach)
• Chrome is accessible via /chrome

Post-Build Checklist

After building or editing a workflow:

• All nodes from the design plan are present
• Trigger type and filters match the plan
• All wait durations are correct
• All If/Else conditions check the right criteria
• Both YES and NO branches have actions (no dead ends)
• Message content matches (check for AI paraphrasing)
• Merge fields are correctly formatted
• Tag names match naming convention (case-sensitive)
• Pipeline and stage references are correct (if applicable)
• Workflow name follows naming convention
• Allow Reentry setting matches the plan
• Workflow is in DRAFT mode (not published until explicitly requested)
• Screenshot of completed workflow captured for user review