crm-sync

Featured

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.

AI & Automation 835 stars 137 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
97
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /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 "$...

Details

Author
indranilbanerjee
Repository
indranilbanerjee/digital-marketing-pro
Created
7 months ago
Last Updated
2 weeks ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

crm-sync

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.

0 Updated 1 months ago
teachskillofskills-ai
AI & Automation Listed

crm-sync

Use whenever a play needs live account truth — reading and reconciling CRM objects, properties, and associations. Spans every lifecycle stage. Runs on the Growth (Verbiflow) MCP.

1 Updated 2 days ago
bowtiefunnel
AI & Automation Listed

crm-export-auditor

Audit a CRM CSV export for the data faults that make every report built on it wrong: exact and near-duplicate accounts and contacts, close dates already in the past on open deals, deals with no activity in the last N days, blank required fields by stage, single-threaded deals carrying one contact, records with no owner or a departed one, stage and amount combinations that contradict each other, and currency, date and country formats that drift between rows. Returns a fix list ordered by how much each fault distorts a reported number, with the record IDs to correct and which fixes are safe to apply in bulk. Use when a pipeline number is disputed, when a migration or a dedupe is being planned, or when nobody has checked the export the forecast is built on.

1 Updated 2 weeks ago
imtiazrayhan