Coordinate opportunities and customer records across multiple CRMs while preserving attribution, visibility, commissions, and governance.
SkillScore88Maintained
Automatic
◆Sales & GTM pack
Last verified 8/21/2026
What it changes
Passed 21 of 24 test cases with the skill, and 14 of 24 without it.
Without skill58%
With skill88%
Checks it passed that the model alone missed
blocks automated syncing of owner changes by default
attaches a synced_from origin marker on records updated across CRMs
places revenue-touching field updates behind mandatory approval gates
and 7 more in the full report
7 fixed14 passed either way3 still failing0 broke
Pass-rate lift
+29 pp
Tokens
-9%
Agent turns
0%
Response time
-28%
Model gemini-3.6-flashMeasured 8/21/2026v121 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
I need an enterprise workflow design for multi-CRM opportunity synchronization between our primary and secondary CRMs. When an opportunity reaches a major milestone, resolve the account against our central customer record, create the connected deal on the destination CRM, send a notification to the account manager, and log an audit entry for the cross-system action.
What was checked, without and with the skill
Checked
Without skill
With skill
defines a canonical stage taxonomy map to align milestone names across CRMs
Missed
Passed
specifies explicit currency translation and foreign exchange rules before syncing deal values
Missed
Passed
implements an audit trail logging step for every cross-system transaction
Passed
Passed
case-03 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md47 linessingle file
Cross-CRM Opportunity Sync
Use this skill when a company runs multiple CRMs and needs one deal, account, or customer relationship to stay understandable across systems.
Workflow
Detect a new opportunity or approved stage-change event in a connected CRM.
Match the account against a master customer record or matching rules.
Determine whether the deal touches another CRM, business unit, product line, or customer relationship.
Mirror or link the opportunity in the relevant CRM with approved fields only.
Surface cross-CRM context to the rep through an internal note, briefing, or team notification.
Write an audit trail for every cross-CRM write.
Route low-confidence matches, old conflicts, and revenue-sensitive updates for human review.
Zapier MCP And SDK Role
Use Zapier MCP to read and write approved CRM fields, call an LLM for matching and enrichment, look up a master customer record, and route rep notifications.
Use Zapier SDK for developer-led implementations that need durable workflow execution, retries, logs, schedules, sandbox-to-production promotion, and audit trails.
Keep production writes, fuzzy matches, revenue-touching workflows, and customer-data workflows approval-gated.
Master Customer Record Patterns
Canonical CRM: one CRM is the source of truth and other CRMs sync from it.
Warehouse-driven: a warehouse creates a shared customer ID that all CRMs reference.
Match-on-the-fly: the agent uses email domain and company-name matching with confidence scoring and human review.
Known Gotchas
Sync loops require a synced_from marker.
Historic duplicates require a separate one-time cleanup pass before go-live.
Bulk migration can hit CRM rate limits.
Field types differ across CRMs and need translation maps.
Stage names drift across CRMs and need a canonical taxonomy.
Currency and FX rules must be explicit before syncing pipeline or revenue values.
Guardrails
Do not sync raw text notes between CRMs without explicit approval.
Do not sync intermediate stage changes by default.
Find approved customer proof for campaigns, pages, decks, emails, and sales conversations. Use when a team needs relevant case studies, quotes, stats, slides, logos, or peer examples.