crm-integration-stinger

name

crm-integration-stinger

description

CRM connectivity specialist for HubSpot, Salesforce, Pipedrive, Attio, Folk, Close, and Copper -- bi-directional sync design, the contact-vs-lead-vs-account taxonomy, merge/dedupe, and the native-vs-Zapier-vs-Merge.dev architecture trade-off. Use when the user says "integrate with HubSpot", "bi-directional CRM sync", "CRM field mapping", "Merge.dev or native API?", "dedup contacts in our CRM", "lead enrichment strategy", "sync conflict resolution", "Salesforce Lead vs Contact", "Attio API production-ready?", or "audit our CRM sync code". Do NOT use for cold email sequence design (cold-outreach-worker-bee), product database schema (db-worker-bee), sync implementation code (python-worker-bee), or frontend CRM widgets (react-worker-bee).

crm-integration-stinger

CRM connectivity playbook for crm-integration-worker-bee. Synthesized from 10 source notes covering Merge.dev pricing analysis, HubSpot/Salesforce/Attio official API docs, bi-directional sync architecture patterns, deduplication strategy, and lead enrichment tool comparisons. Research window: November 2025 -- May 2026.

See research/research-summary.md for key findings and open questions. The six-guide structure maps directly to the six major decision surfaces the worker-bee faces.

---

When this stinger applies

Load when any of the following are true:

• The user needs to connect their product to HubSpot, Salesforce, Pipedrive, Attio, Folk, Close, or Copper.
• The user is deciding between native API integration, Merge.dev/Unified.to, or no-code automation (Zapier, Make).
• The user is designing a bi-directional sync and has not yet defined a conflict resolution policy.
• The user is asking about the difference between Salesforce Leads vs Contacts, HubSpot's lack of a Lead object, or Attio's dynamic attributes.
• The user has duplicate contacts/accounts in their CRM and needs a dedup strategy.
• The user is adding lead enrichment (Clearbit/Breeze, Apollo, Clay) to their CRM write flow.
• The user wants a code audit of existing CRM sync code.