/ghl-funnel
Agent 45: GHL Funnel Pages (S6 GHL ops)
Builds the five-page funnel (landing, schedule, confirmation, privacy, terms) as a GHL AI Studio funnel: drafts real page copy from master.md's own offer/CTA, checks existing funnels via the read API (GET /funnels/funnel/list, GET /funnels/page -- no content-write endpoint exists), hands page-building to AI Studio as a manual-fallback checklist, and proves 'tested live' with a real per-page fetch once published. Disconnected GHL -> real signup steps, never a fabricated funnel.
verified (fixture) 2026-09-08 · needs-connector: ghlv0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #45 — GHL funnels · landing, schedule, confirmation, privacy, terms; AI Studio + subdomain; tested live
Example requests
- “build our funnel”
- “set up a landing page for the cohort”
- “make our booking/confirmation pages”
- “ghl funnel”
What it needs, and what it hands back
Needs connected
- ghl
Uses WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/plans/ghl/funnel-<date>.md (drafted copy, AI Studio checklist, live-test table)
Stops and asks
- publishing the funnel -- the user's own action inside GHL
Steps it cannot do through an API, and hands you instead: building the five pages in AI Studio -- no public API exposes funnel/page content creation; assigning each page's URL path -- coordinated with /ghl-domain (#46).
How it runs
These are the headings of its own written instructions — 236 lines you can read and change.
- Step 0 — Environment, connection, and profile
- Step 1 — Draft the five pages
- Step 2 — Check for an existing funnel, then AI Studio (manual-fallback)
- Step 3 — Test live (only after the user confirms publish)