| name | sales-syncgtm |
| description | SyncGTM (syncgtm.com) platform help — AI-native GTM data engine that unifies buying signals (job changes, funding, hiring, LinkedIn posts, web-traffic, custom AI signals), waterfall enrichment (verified emails/mobiles, 40+ providers), AI lead scoring (0–100 vs ICP), AI research agents, and a no-code Workflow Builder. Developer surface: an MCP server (api.syncgtm.com/mcp, OAuth browser sign-in, free-plan — works with Claude Code/Cursor to enrich, find emails/phones, read signals), a REST API (api.syncgtm.com, API key), webhooks, and 40+ integrations (HubSpot/Salesforce/Slack/Attio). Use when connecting the MCP server to an AI agent, enriching contacts via the API, acting on buyer signals, scoring leads vs an ICP, building a signal→enrich→outreach workflow, or choosing SyncGTM vs Clay/Trigify. Do NOT use for intent-data strategy across tools (use /sales-intent), prospect-list building (use /sales-prospect-list), or enrichment strategy across vendors (use /sales-enrich). |
| argument-hint | [describe what you need help with in SyncGTM] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","intent","gtm","platform"] |
| github | https://github.com/syncgtm |
SyncGTM Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Use the MCP server from an AI agent (Claude Code, Cursor) to enrich / read signals
- B) Enrich people/companies or find verified emails/phones via the REST API
- C) Monitor + act on buying signals (job changes, funding, LinkedIn, web traffic)
- D) Score leads 0–100 against your ICP, or build a signal→enrich→outreach workflow
- E) Push results into a CRM/Slack (40+ integrations) or react via webhooks
- F) Decide SyncGTM vs Clay / Trigify / Common Room / Koala, or pick a plan
-
AI agent or app? Agent → MCP server (token-free OAuth). Code/automation → REST API + webhooks. No-code → native integrations + Workflow Builder.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Intent-data / buyer-signal strategy across tools (which signals, how to act) | /sales-intent {question} |
| Building a prospect list across tools | /sales-prospect-list {question} |
| Contact enrichment strategy across vendors | /sales-enrich {question} |
| Outbound sequence/cadence strategy for the outreach step | /sales-cadence {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-intent which buying signals predict pipeline for PLG SaaS".
Step 3 — SyncGTM platform reference
Read references/platform-guide.md for the full reference — the signal/enrichment/scoring/workflow model (what's MCP vs REST vs UI), the credit/plan model, the data model, and quick-start recipes (connect the MCP server; enrich via API; trigger a workflow on a signal).
Read references/syncgtm-api-reference.md for the integration surface — the MCP server (https://api.syncgtm.com/mcp, , free-plan access; tools to enrich, find verified emails/phones, pull LinkedIn, read signals), the (base , API key), , the catalog, and the 40+ native integrations.
