agentsclimarketplace
Sign in

Cross crm opportunity sync

Skill zapier/gtm-cheat-codes/skills/sales-revops/cross-crm-opportunity-sync

Coordinate opportunities and customer records across multiple CRMs while preserving attribution, visibility, commissions, and governance.From its SKILL.md

Install
npx -y skills add zapier/gtm-cheat-codes --skill cross-crm-opportunity-sync

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.8 KB, 537 tokens by cl100k_base, as published. Nobody here has run it

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

  1. Detect a new opportunity or approved stage-change event in a connected CRM.
  2. Match the account against a master customer record or matching rules.
  3. Determine whether the deal touches another CRM, business unit, product line, or customer relationship.
  4. Mirror or link the opportunity in the relevant CRM with approved fields only.
  5. Surface cross-CRM context to the rep through an internal note, briefing, or team notification.
  6. Write an audit trail for every cross-CRM write.
  7. 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.
  • Do not sync owner changes by default.
  • Do not auto-promote low-confidence matches.
  • Do not touch production without sandbox review and designated approval.
  • Always write an audit row for cross-CRM writes.

Inspired By

This skill is generalized from When operators get the keys to the integration stack, a customer story with Voltt founder William Ascough. The reference implementation runs across multiple CRMs at a global multi-product business with operator-built workflows governed through a sandbox-to-production model.

What ships with it: 5 files

6.9 KB alongside SKILL.md

Gives 0 of the 12 instructions most sales audience skills give in 537 tokens

Counted across 401 of the 401 authors here whose files we hold, read 2026-08-07

  • Read product marketing context before asking questionsin 21 of 401, across 11 files
  • Acknowledge competitor strengths honestlyin 18 of 401, across 7 files
  • Start every page with a summaryin 15 of 401, across 4 files
  • Use a single, low-friction call to actionin 15 of 401, across 7 files
  • Create a single source of truth for each competitorin 14 of 401, across 3 files
  • Make each follow-up email add new valuein 11 of 401, across 5 files
  • Cut any sentence that does not drive a replyin 10 of 401, across 4 files
  • Tie personalization directly to the problemin 10 of 401, across 4 files
  • Write paragraph comparisons for each dimensionin 9 of 401, across 3 files
  • Link between related competitor pagesin 9 of 401, across 3 files
  • Keep subject lines short and lowercasein 9 of 401, across 3 files
  • Define ideal customer profile from top customersin 9 of 401, across 3 files

Said here and by no other author read

  • detect new opportunity or stage-change events
  • match accounts against a master customer record
  • determine if the deal touches another CRM
  • mirror opportunities with approved fields only
  • surface cross-CRM context to the rep
  • write an audit trail for every cross-CRM write

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.