Wie übertragen Sie GoHighLevel-Snapshot-Updates, ohne Kundenanpassungen zu überschreiben?

Compare our GoHighLevel client sub-account against our master snapshot before we push an update:
1. List all workflows, funnels, and custom values in the target sub-account and compare them against our master agency snapshot.
2. Flag any active workflow that has been edited locally inside the client sub-account and recommend renaming it with a "[Custom]" prefix before pushing.
3. Generate an additive-only push checklist that excludes existing Custom Values and live client funnels.

# 1. MCP Tool Call (ghl-agency-mcp)
{
  "tool": "snapshots_diff_subaccount",
  "arguments": {
    "snapshot_id": "<MASTER_SNAPSHOT_ID>",
    "location_id": "<YOUR_LOCATION_ID>",
    "protect_custom_prefix": "[Custom]"
  }
}

# 2. Or run via ghl-agency Rust CLI
ghl-agency snapshots diff --snapshot-id <MASTER_SNAPSHOT_ID> --location-id <YOUR_LOCATION_ID>

Official GHL MCP vs. ghl-tools: HighLevel’s official hosted MCP (services.leadconnectorhq.com/mcp) covers public v2 CRM records (contacts, opportunities, appointments, conversations). ghl-tools MCP complements it with workflow graph inspection & recipes, funnel/form builders, DNS/BIMI checks, and ghl-crm doctor audits.