← ClaudeAtlas

crm-synclisted

Sync marketing data to and from Salesforce, HubSpot, Zoho, or Pipedrive — contacts, deals, and campaign links with field mapping, deduplication, consent checks, batched execution behind a mandatory approval gate, and a rollback manifest. Produces a full sync report with per-record outcomes. Triggers on "/digital-marketing-pro:crm-sync", "push these contacts into HubSpot", "sync deals to Salesforce", "our CRM and marketing lists don't match", "set up a recurring CRM sync". Reads the brand profile and compliance rules; for scored lead imports use /digital-marketing-pro:lead-import instead.
teachskillofskills-ai/DigitalMarketingPro-techshu · ★ 0 · Data & Documents · score 73
Install: claude install-skill teachskillofskills-ai/DigitalMarketingPro-techshu
# /digital-marketing-pro:crm-sync ## Purpose Sync marketing data to and from the brand's connected CRM platform. Handles contact creation, deal updates, and campaign linking with automatic field mapping, deduplication, and compliance checks. Supports Salesforce, HubSpot, Zoho, and Pipedrive with bi-directional sync capabilities, ensuring marketing and sales teams operate from a single source of truth without manual data entry or import/export cycles. Designed for both one-time bulk syncs and recurring automated transfers, with full audit trails and rollback capabilities for enterprise-grade data governance. Use this command instead of manual CSV imports when you need deduplication, compliance validation, or audit logging. For lead-specific imports with scoring, use `/digital-marketing-pro:lead-import` instead. ## Execution gate (MANDATORY — cannot be skipped) 1. Present the full preview — recipients / spend / changes / compliance — as an **Execution Summary** before touching any live system. 2. The user must type `yes` (or an equivalent explicit approval). ANY other input — ambiguous, implied, partial, or absent approval — cancels the run. 3. Never proceed on ambiguous input. Never auto-retry a failed execution; a failure needs human review before any re-run. 4. Record the approval with `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action create-approval --data '{"risk_level":"<tier>","summary":"..."}'` **before** executing, then `python "$