Cross Crm Opportunity Sync

Organization

zapier

cross-crm-opportunity-sync

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

Overview

Publisher	zapier
Repository	`gtm-cheat-codes`
Skill name	`cross-crm-opportunity-sync`
Stars	349
Forks	21
Bundled files	4
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by zapier on GitHub. Read the source before you install it.

Installation

Install the Cross Crm Opportunity Sync AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/zapier/gtm-cheat-codes/tree/main/skills/sales-revops/cross-crm-opportunity-sync
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/zapier/gtm-cheat-codes/tree/main/skills/sales-revops/cross-crm-opportunity-sync

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git /tmp/gtm-cheat-codes
mkdir -p .claude/skills
cp -r /tmp/gtm-cheat-codes/skills/sales-revops/cross-crm-opportunity-sync .claude/skills/cross-crm-opportunity-sync

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cross Crm Opportunity Sync in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cross Crm Opportunity Sync on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cross Crm Opportunity Sync is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.
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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cross Crm Opportunity Sync AI skill do?

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

Why use Cross Crm Opportunity Sync on TypingMind?

Because you install it once and use it with any model. Cross Crm Opportunity Sync is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cross Crm Opportunity Sync in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zapier/gtm-cheat-codes/tree/main/skills/sales-revops/cross-crm-opportunity-sync. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cross Crm Opportunity Sync?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cross Crm Opportunity Sync?

As many as you like. As long as a model supports skills, you can use Cross Crm Opportunity Sync with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cross Crm Opportunity Sync AI skill free?

Yes. It is published on GitHub by zapier under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Version Bump

thedotmack

CommunityPopular

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging,…

Agent Builder

Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or…

Changelog Generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns…

Agent Authentication

Agent skill for authentication - invoke with $agent-authentication

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Cross-CRM Opportunity Sync

Workflow

Zapier MCP And SDK Role

Master Customer Record Patterns

Known Gotchas

Guardrails

Inspired By

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now