SHAI
Book a callStart free

S6 GHL

/ghl-setup

Agent Wave 4f Orchestrator: GHL Sub-Account Setup (S6 GHL ops)

Wave 4f orchestrator: creates a new GHL sub-account (POST /locations/, optionally snapshot-loaded) or links an existing locationId, writes it to master.md's ghl_location_id only after a GET read-back, then routes this business's build through every S6 member skill in real dependency order (tags/pipeline before calendar/forms, calendar before automations/voice, A2P's number before voice/chat agents, SaaS builder last). Also drives the P4f.gate one-sample-per-member routing convention, matching /life-planner's and /ads-manager's role in their own waves.

verified (fixture) 2026-09-08 · needs-connector: ghlv0.1.0

Run itAll agents

Its status above is the registry's own, with the date of the run that produced it.

What it is for

Contract A

This agent owns no numbered ledger item of its own.

Example requests

  • “set up GHL for this business”
  • “connect our sub-account”
  • “run the whole GHL build”
  • “ghl setup”

What it needs, and what it hands back

Needs connected

  • ghl

Hands back

  • clients/<business-slug>/plans/ghl/setup-<date>.md (create/link result, dependency-ordered run log, wave-gate sample record)
  • clients/<business-slug>/profile/master.md (ghl_location_id, once read-back confirmed)

Stops and asks

  • creating a new, billable GHL sub-account

How it runs

These are the headings of its own written instructions — 228 lines you can read and change.

  1. Step 0 — Environment, connection, and profile
  2. Step 1 — Create or link the sub-account
  3. Step 2 — Dependency order
  4. Step 3 — Wave-gate sampling (when invoked for `P4f.gate`)