API Endpoint to Load a Snapshot onto a Sub-Account — Enable Trigger Link & Workflow Automation
E
Enoch Leffingwell
The Problem:
As an agency owner and course creator, I teach my clients how to use GoHighLevel through structured courses. Each course module walks the client through a specific feature set — but there is currently no way to pair a focused snapshot with a course lesson and let the client load only that snapshot when they are ready to use it.
The only option today is to load a large, all-inclusive snapshot upfront — which overwhelms clients with funnels, workflows, and features they haven't learned yet and don't need. There is also no way to push a targeted snapshot to an existing client's sub-account at the right moment in their learning journey without doing it manually from the agency dashboard, one account at a time.
The Ask:
Allow agency owners to associate a specific, scoped snapshot with a course or course lesson, and give clients the ability to load that snapshot into their own sub-account directly — either by clicking a button inside the course or by clicking a trigger link delivered at the right step in the curriculum.
Additionally, allow the agency to push a targeted snapshot to one or many existing sub-accounts via the API or a workflow action — so that as clients progress through a course, the right tools are waiting for them when they need them.
How it would work:
The agency creates small, focused snapshots scoped to a single feature set (e.g., a "Reputation Management" snapshot, a "Appointment Funnel" snapshot, a "Email Nurture" snapshot)
Each snapshot is paired with the corresponding course module where it is taught
When the student reaches that lesson, a "Load This Snapshot" button or trigger link is available — the student clicks it and the snapshot loads into their sub-account automatically
The agency can also push the snapshot to specific sub-accounts via API or workflow, targeting clients enrolled in a particular course or carrying a specific tag
Example Use Case:
A business coach sells a $10,000 coaching program that teaches health educators how to use GHL. The course has 8 modules. Rather than dumping every funnel, workflow, and automation into the client's account on day one, the coach pairs a small snapshot with each module. When the client reaches Module 3 — "Setting Up Your Appointment Funnel" — they click a button inside the lesson and only the appointment-related snapshot loads into their account. Clean, focused, and timed perfectly to where they are in the curriculum.
Why this matters:
Loading a full snapshot on a brand-new client creates confusion, bloat, and support tickets. Clients feel overwhelmed when they see dozens of workflows and funnels they haven't been taught yet. A modular, course-paired snapshot approach means clients only see what they're ready to use — which improves adoption, reduces churn, and allows the agency to support clients at scale without manually managing each sub-account.
This is especially critical for coaches and educators who sell GHL-based programs to existing clients who already have active sub-accounts — the current snapshot system is designed for new account setup, not for progressive, curriculum-guided feature rollout.
Requested additions:
Ability to attach a snapshot to a course lesson in the Courses section, with a client-facing "Load Snapshot" button or trigger link
A Workflow Action — "Load Snapshot onto Sub-Account" — that can target existing sub-accounts by tag, enrollment, or custom field
API endpoint: POST /v1/locations/{locationId}/snapshots/load with snapshotId and selective restore options (load only specific components, not overwrite existing data)
Snapshot scoping / selective load — so only the relevant components (e.g., one workflow, one funnel) are loaded rather than the full account template
Log In