TL;DR: This is the reference table for what actually syncs between the major conversation tools (Gong, Zoom, Fathom, Fireflies, Granola, Gmail) and the systems of record (Salesforce, HubSpot, Jira, Zendesk, Slack) — every cell verified against vendor documentation, dated, and maintained. The dataset is also available as machine-readable JSON, licensed CC BY 4.0: cite it, quote it, build on it.
Every integration decision starts with the same three questions — does a native connector exist, what does it actually carry, and what does it cost in plan tiers and gotchas — and until now the answers were scattered across fifteen vendor help centers, each describing only its own pipes. We compiled them. One table, primary sources only, verified July 7, 2026, with a deep-dive guide behind every row.
Use it, and reuse it: the underlying dataset is published at /data/integration-matrix.json under CC BY 4.0. If you’re writing about these tools, comparing them, or feeding an AI assistant that answers integration questions — take the data, link the source. If we’ve got something wrong or a vendor ships something new, tell us; we correct with a visible update note.
The matrix (verified July 7, 2026)
| Pair | Native? | Transcript lands in destination? | Plan gate | The gotcha | Deep dive |
|---|---|---|---|---|---|
| Gong → Salesforce | Yes (two-way) | No — iframe render only | Any Gong plan; managed package needs SF Enterprise+ | Deleting a call in Gong deletes the Salesforce record | Guide |
| Gong → HubSpot | Yes (two-way) | No | Any Gong plan | Up to 6h latency; no historical backfill | Guide |
| Gong → Jira | No | — | Zapier: admin-created Zaps only | In-call flows go to Productboard/Zendesk, not Jira | Guide |
| Gong ↔ Zendesk | Yes (two separate) | No — ticket links to call moment | Any Gong plan | Ticket creation is manual, per-call, one-way | Guide |
| Zoom → Salesforce | Partial | No | Summaries: paid ZoomMate add-on or Zapier | AI Companion summaries don’t sync natively at all | Guide |
| Zoom → HubSpot | Partial | Enterprise Hub only | Recording/transcript sync: Sales or Service Hub Enterprise | AI summaries sync on no tier (open request since 2024) | Guide |
| Fathom → Salesforce | Yes | No | Fathom Business ($25/u/mo); SF Enterprise+ | No Leads, no closed opps, primary email only | Guide |
| Fathom → HubSpot | Yes | No | 3 connections/user below Business | External calls, main calendar, forward-only | Guide |
| Fireflies → Salesforce | Yes | Yes — full text (Pro+) | Transcript: Pro+; meeting filters: Business+ | Internal/extension calls log under the “Fred” fallback contact | Guide |
| Fireflies ↔ HubSpot | Yes (two-way) | Link only | Meeting filters: Business+ | Docs contradict themselves on transcript push — test yours | Guide |
| Granola → Salesforce | No | — | Zapier: Business ($14/u/mo); or Enterprise API | Native CRM connectors are Attio/HubSpot/Affinity only | Guide |
| Granola → HubSpot | Yes | No — enhanced notes only | Business; Google Workspace/M365 account required | Unknown attendees silently don’t sync — never creates records | Guide |
| Zendesk ↔ Jira | Yes | — | All current plans | Field sync is case-sensitive and fails silently | Guide |
| Zendesk ↔ Slack | Yes | — | All current plans | Can’t close tickets or edit fields from Slack; no attachments | Guide |
| Gmail → Salesforce | Yes | — | Gmail pane free with Sales Cloud; EAC tiers vary | Classic EAC deletes captured email after 6–24 months — enable email-as-activity | Guide |
What the matrix teaches (three patterns)
1. The transcript almost never travels. Fourteen of fifteen pairs either drop the transcript or gate it behind top tiers — Fireflies’ Salesforce integration is the lone full-text exception. The most information-dense artifact your customer relationship produces is systematically excluded from your system of record.
2. The gates cluster on the same tiers. Business/Enterprise plans on the recorder side, Enterprise editions on the CRM side. The pattern is consistent: capture is cheap, context is upsold.
3. Every pipe is a pair. Each cell above connects exactly two tools. Nothing in this table — nothing — joins the Gong call to the Zendesk escalation to the Gmail thread for the same account. That’s not a missing feature; it’s the wrong shape. Pairwise plumbing produces pairwise answers, and customer questions are account-shaped. (That’s the problem Noded exists to solve — every tool in this table feeds one Customer Context Graph — but this page’s job is the table, and the table is vendor-neutral: it will say so when a vendor ships something that changes a row.)
Methodology and maintenance
Every cell traces to vendor help documentation or a primary announcement fetched on the verification date; each linked guide carries the source URLs. We re-verify on a monthly cadence and after major vendor announcements, bump the date stamp, and note corrections visibly. The JSON dataset carries the same verification date — if you consume it programmatically, check the verified field.
FAQ
Which call recorder syncs full transcripts into Salesforce?
Fireflies (Pro plan or higher) is the only one in this matrix that writes full transcript text into Salesforce. Gong, Fathom, and Granola sync summaries, links, or iframe renders.
Which pairs have no native integration at all?
Gong–Jira and Granola–Salesforce, as of July 2026. Both are commonly assumed to exist; both require Zapier, middleware, an API build, or an aggregation layer.
Can I reuse this data?
Yes — the JSON dataset is CC BY 4.0: reuse freely with attribution to Noded AI, ideally linking this page so readers get the maintained version.