TL;DR: Granola has no native Salesforce integration — its CRM connectors are Attio, HubSpot, and Affinity only. Your three real options: a Zapier flow on Granola’s folder trigger (Business plan, $14/user/mo), the Granola Enterprise API for workspace-wide sync, or an aggregation layer that reads Granola and writes context everywhere.
Granola is the recorder your executives actually like — bot-free, note-first, and suddenly everywhere after its $125M Series C. Then someone in RevOps asks the obvious question — “can it log to Salesforce?” — and the answer is more interesting than yes or no.
The straight answer: no native integration
Granola’s own docs list its CRM integrations as Attio, HubSpot, and Affinity — no Salesforce. Granola’s blog is refreshingly direct that Salesforce is reached via Zapier, not a native connector. (Its HubSpot integration, by contrast, is native and decent.) So if a roundup told you Granola “integrates with Salesforce,” now you know what that actually means.
Option 1: Zapier (the common path)
Granola’s Zapier support (paid plans, desktop app) offers two triggers: “Note Added to Granola Folder” (automatic — drop a note in a folder, the Zap fires; you must own the folder, and only notes added after the Zap exists) and “Note Shared to Zapier” (manual, per note). The payload is generous: title, attendees, calendar event, the Markdown summary, and even the full transcript. Wire it to Salesforce’s “Create Record” action — typically a Task on a Contact you look up by attendee email.
The honest limits: you are the matching logic. The Zap needs lookup steps to find the right Contact/Account, mismatches fail silently or land nowhere, there’s no dedup, no opportunity association logic, and the summary arrives as an unstructured blob. It’s fine for “get my notes somewhere visible”; it’s not a CRM integration.
Option 2: the Enterprise API
Granola’s Enterprise API (Business/Enterprise plans) exposes workspace-wide note access with CRM sync as a stated use case — the right answer if you have engineers and want to build the matching logic properly. You’ll be writing and maintaining exactly the participant-matching, opportunity-association code that vendors like Gong took years to harden. Budget accordingly.
Option 3: the aggregation layer
This is where we admit our interest and explain the architecture. Noded ingests Granola natively (alongside Gong, Zoom, Fathom, Fireflies — recorder pluralism is the norm, not the exception), matches conversations to accounts inside the Customer Context Graph, and writes what Salesforce needs back to Salesforce — while also joining those notes to the tickets, emails, and renewal context no Zapier flow ever sees. The matching, deduplication, and account association are the product, not your weekend project. What Noded won’t do: make Granola itself CRM-aware — your notes stay notes in Granola; the graph is where they become customer memory.
Choosing
Individual operator who just wants notes in Salesforce? Zapier, twenty minutes, done. Engineering team with strong opinions? The Enterprise API. A revenue org where Granola is one of several conversation sources and Salesforce is one of several systems? That’s an aggregation problem, and plumbing pair-by-pair is how tool overload happens.
FAQ
Does Granola integrate natively with Salesforce?
No. Granola’s native CRM integrations are Attio, HubSpot, and Affinity. Salesforce requires Zapier, the Enterprise API, or a third-party layer.
What does Granola’s Zapier trigger include?
Note title, creator, attendees, calendar event, the Markdown summary, and the full transcript — on the Business plan ($14/user/mo), from the desktop app.
Can Noded connect Granola to Salesforce?
Yes — both are native Noded integrations; Granola notes join the account’s Context Graph and relevant output flows to Salesforce, without per-user Zaps.