crm-integration-wasp-drone — Claude Code subagent: setup guide
crm-integration-wasp-drone architects CRM pipelines, maps entity schemas, and designs sync logic. Connects your product to HubSpot, Salesforce, Attio, or Pipedrive without data loss.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat crm-integration-wasp-drone does
This subagent plans integrations between software products and external CRMs. It breaks down object differences across HubSpot, Salesforce, Pipedrive, Close, Copper, Folk, and Attio. Data models come first. The agent defines deduplication rules, field mappings, and conflict resolution policies before syncing begins.
Execution requires the paired crm-integration-stinger skill resolved through hooks/resolve-component.py. Financial trade-offs are flagged early in the planning stage. For instance, unified aggregation via Merge.dev on the Launch plan reaches around $1.17M annually for 500 clients across three CRMs.
Scope is strictly bounded by design and audit tasks. It leaves backend implementation code and compliance details to other dedicated drones.
What it helps with
- design two-way CRM sync workflows with explicit echo prevention
- map contact and lead schemas across Salesforce, HubSpot, and product databases
- set up deterministic and probabilistic deduplication strategies
- evaluate cost and latency trade-offs between native APIs and Merge.dev
- audit CRM connector implementations against API rate limits
Example prompts for the agent
- Design a bi-directional sync strategy for contacts between our platform and HubSpot.
- Compare trade-offs between building on native Salesforce APIs versus Merge.dev.
- Audit our Attio integration logic to verify webhook error handling.
How to install crm-integration-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/crm-integration-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/crm-integration-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/crm-integration-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about crm-integration-wasp-drone
How to install crm-integration-wasp-drone in Claude Code?
First run /plugin marketplace add legioncodeinc/vibe-coding-tools. Next, run /plugin install platform-and-release-tools@wasp-nest and reference .claude/agents/crm-integration-wasp-drone.md.
Which CRM platforms are covered?
The subagent supports HubSpot, Salesforce, Pipedrive, Attio, Folk, Close, and Copper, accounting for platform-specific taxonomies and picklist requirements.
Does this subagent write backend synchronization scripts?
No. It focuses on architecture blueprints, field mapping tables, and deduplication rules, delegating backend code generation to python-wasp-drone.