¿Cómo evitas que las actualizaciones masivas de etiquetas en GoHighLevel saturen los webhooks y dupliquen contactos?

Audit our GoHighLevel outbound webhook workflows to prevent rate-limit spikes and duplicate records during CSV imports:
1. Check every workflow containing an Outbound Webhook action and insert a 1-minute Wait buffer before the webhook fires.
2. Verify the webhook payload includes {{contact.id}} as the primary upsert key rather than matching only on email or phone.
3. Check for any circular webhook loops where an inbound webhook updates a field that re-triggers the same outbound webhook.

# 1. MCP Tool Call (ghl-crm-mcp)
{
  "tool": "workflows_audit_webhooks",
  "arguments": {
    "location_id": "<YOUR_LOCATION_ID>",
    "require_wait_buffer": true,
    "check_circular_loops": true
  }
}

# 2. Or run via ghl-crm Rust CLI
ghl-crm doctor --location-id <YOUR_LOCATION_ID> --pillar workflow_safety

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.