Guides

Granola and Fathom Pipedrive integration: how to connect them

By Tomi · Last updated

As of October 30, 2026, neither Granola nor Fathom has a native Pipedrive integration. Granola's built-in CRM sync covers HubSpot, Attio and Affinity on paid plans (plus Salesforce on Enterprise), and Fathom's covers HubSpot, Salesforce and Close. To get a meeting into Pipedrive, you have two options. A Zapier workflow can copy the summary into a note or activity. Or Claude can read the meeting through the Granola or Fathom connector and update Pipedrive through Pipedrive's official connector, one record at a time, after you approve. If you'd rather switch, tl;dv, Fireflies and Avoma integrate with Pipedrive natively, and Pipedrive's own Nova is free on every plan.

Checked against each vendor's docs on October 30, 2026. We haven't run the Claude workflow on our Pipedrive sandbox yet. What we couldn't verify.

Quick answer: which route to use

If you want Use
The meeting summary saved on the person or deal Zapier, with Granola or Fathom
Field updates, new people or changes on more than one record Claude with both connectors
A notetaker that syncs with Pipedrive out of the box tl;dv, Fireflies or Avoma, or Pipedrive's free Nova

What each notetaker writes to Pipedrive

Notetaker Native with Pipedrive? What it writes What it doesn't do
Granola No (native: HubSpot, Attio, Affinity; Salesforce on Enterprise) Through Zapier (paid plans): whatever note or activity you set up, when you share a note or add it to a folder No field updates, matching or new records unless you build each step
Fathom No (native: HubSpot, Salesforce, Close) Through Zapier: a note or activity when a recording, summary, transcript or action item is ready One fixed action per step you build, like Granola
tl;dv Yes, Pro plan and up A Meeting activity or note on the matched person or deal, and chosen note sections in Person or Deal fields Its page doesn't describe creating deals, moving stages or touching other deals
Fireflies Yes (plan not stated in its setup guide) A note (and a call activity by default) on the contact, lead or deal; can create contacts or leads for new participants Its setup guide doesn't describe field updates
Avoma Yes, through the Pipedrive Marketplace AI notes with action items on the contact, organization or deal; edits in Avoma update the same note Its field-mapping help covers only HubSpot and Salesforce
Gong No (native: Salesforce, HubSpot, Dynamics) Through a paid partner connector: call summaries as activities Costs at least $5,000 a year plus a setup fee
Otter No native integration found Only through Zapier or similar tools Everything beyond what you build
Nova Built into Pipedrive, free A debrief note on a linked record and suggested field updates you approve one by one No new records or tasks, one linked record per meeting (details)

Sources: Granola's integrations and Zapier articles and pricing; Fathom's help center integrations; tl;dv (updated September 14, 2026); Fireflies' setup guide; Avoma's announcement and field-mapping FAQ; Gong's CRM integrations (January 8, 2026) and the CRM Connect listing.

The native integrations attach the meeting to the record they matched, and some fill a few fields. None of them updates the other records the call mentions.

Granola Pipedrive integration: what works

Granola has three routes to other tools, and they depend on your plan (Granola plans):

  • Zapier works on paid plans (from Business, $14 per user a month), in the desktop apps.
  • The MCP server, which Claude and ChatGPT use, works on every plan. On the free Basic plan it only sees notes from the last 30 days, without transcripts or folders (Granola MCP).
  • The API needs Business or Enterprise.

Granola to Pipedrive with Zapier

  1. Pick the trigger. In Zapier, choose Granola and either Note Shared to Zapier (you send each note by hand from the note's sidebar) or Note Added to Granola Folder (every note you file in a "Pipedrive" folder, from the moment the Zap exists; you need to be a Collaborator or Owner of the folder).

  2. Find the record. Add Pipedrive Find Person by an attendee's email, then Find Deals for that person, so the note doesn't land on the wrong contact.

  3. Write the note. Add Create Note (or Create Activity) and map the Granola summary into the content, linked to the person and the deal you found.

  4. Test with one meeting and open the person in Pipedrive to check where the note landed.

A Zap with Find steps has more than two steps, which needs a paid Zapier plan. And Zapier won't notice that the call introduced a new person or moved the close date.

Fathom Pipedrive integration: what works

Fathom's plans are Free, Premium, Team, Business and Enterprise. Only Business lists "CRM field sync" (Fathom pricing), and that sync is for the CRMs Fathom supports, not Pipedrive. The same page marks Zapier and Make as limited on some plans. Fathom has a public API on all plans (developer FAQ), launched in October 2025, and an MCP server since April 2026 (changelog).

Fathom to Pipedrive with Zapier

  1. Pick the trigger. In Zapier, choose Fathom and New AI Summary. The other triggers are New Recording, New Transcript, New Action Item, New Highlight and New Download Video. You can limit them to your own meetings or include your team's.

  2. Find the person and the deal with Pipedrive's Find Person by attendee email, then Find Deals for that person.

  3. Create the note on the deal with the summary, and a Create Activity for each action item if you want follow-ups.

  4. Test with one real call. Decide in the Find Person step what happens when nobody matches: stop the Zap, or create the person.

Update Pipedrive after a meeting with Claude

This route can touch more than one record. Claude reads the meeting with the Granola or Fathom connector and writes with Pipedrive's.

  1. Connect Pipedrive. In Claude, go to Customize > Connectors, search for Pipedrive, click Connect and approve in Pipedrive with Allow and install. The full steps are in How to connect Pipedrive to Claude.

  2. Connect Granola or Fathom. Search for it in the same directory and sign in. If it isn't listed, add it as a custom connector with https://mcp.granola.ai/mcp or https://api.fathom.ai/mcp (Fathom MCP for Claude). On Claude Team or Enterprise, an Owner has to enable each connector first.

  3. Run the prompts below in order, in one chat.

Prompts you can copy

Prompt What it does
"Find my meeting with Northwind from today in Granola. List every person, company, deal, date, amount and commitment mentioned." Reads the meeting
"Search Pipedrive for each of them. Tell me which already exist, which don't, and which look like duplicates (same email or similar name). Don't change anything." Read only
"Write the changes you'd make as a numbered list: record, field, current value, new value. Include new people, the follow-up activity and a note on the deal." A plan, no writes
"Apply changes 1, 2, 4 and 6 only. After each one, give me the record ID and what Pipedrive returned. Stop if one fails." Writes, one record per call
"Read back the Northwind deal, its people and its activities, and check that every change is there." Read only

For Fathom, write "in Fathom". If Claude can't see the meeting, check that the connector is on in that chat. On Granola Basic, Claude only sees the last 30 days.

The limits of this workflow

  • One record at a time. Pipedrive's connector writes each change as a separate call, with no preview of the whole set. Five changes are at least five calls (all 51 tools).
  • No merge. If the search finds "Dana Ortiz" twice, Claude can tell you, but the connector can't merge them. You merge in Pipedrive, and Pipedrive says merges can't be undone (what a merge loses).
  • No undo. Every change appears in Pipedrive's change log, but nothing rolls it back. Pipedrive's Restore data brings back deleted items for 30 days and, according to Pipedrive, list-view bulk edits, but not merges or single edits (backup and restore). If Claude overwrites a value, you type the old one back.
  • Wrong matches. "Acme" and "Acme Ltd" look the same to a search. That's why the second prompt asks before writing.
  • Token cost. Every search and write counts against your Pipedrive plan's limits. How that adds up: Why Claude used up your Pipedrive API tokens.

What still takes manual work

A call often changes more than the deal it was about: a new stakeholder who wasn't invited, a person who turns out to exist twice, a related deal at the same company with a new close date. The native integrations write only to the record they matched, Nova to one linked record, and Claude reaches the others only if you ask, one call at a time. Nothing merges the duplicate, and nothing undoes what was written.

What we couldn't verify

  • Fathom's MCP tools. Fathom doesn't publish a tool list or say which plans include the MCP. Reading meetings is all this workflow needs from it.
  • Otter. We found no native Pipedrive integration in Otter's docs or the Pipedrive Marketplace.
  • Fireflies and Avoma plans. Fireflies lists CRM integrations on paid plans without naming Pipedrive. Avoma's Pipedrive post, from February 2025, names no plan.
  • How many tokens a Claude session like this spends on Pipedrive's side. Pipedrive doesn't publish the cost per connector action.
  • The Claude workflow end to end. We haven't run it on our sandbox yet.

Where Pipehand fits

Pipehand is planned to launch in April 2027 as a replacement for Pipedrive's connector that will work with any AI. It will do everything the official connector does, plus merging, bulk edits that show first how many records will change, approval for large changes and undo.

One of the first templates we plan to ship is "After every meeting, update everything it touched". Your AI will read the meeting in Granola, Fathom or tl;dv through their own connectors, then write through Pipehand to the deal, the new people, the duplicate, the organization, the related deals and tasks for teammates. You'll approve the changes first and be able to undo them later. Pipehand won't read your meetings itself or run its own AI model. Founding members are expected to get early access from January 2027.

If you want Pipedrive to update itself after every meeting, with approval first and undo later, join the waitlist on pipehand.com.

FAQ

Does Granola integrate with Pipedrive?

Not natively. As of October 30, 2026, Granola's CRM integrations are HubSpot, Attio and Affinity on paid plans, plus Salesforce on Enterprise. You can connect Granola to Pipedrive through Zapier on a paid plan, or have Claude read Granola and update Pipedrive through both connectors.

Does Fathom integrate with Pipedrive?

Not natively. Fathom's help center has CRM integration articles for HubSpot, Salesforce and Close only. Fathom can reach Pipedrive through Zapier or Make, or through its API and MCP server with an AI like Claude.

What is the best AI notetaker for Pipedrive?

If you want something built in, Nova is free on every Pipedrive plan. Among third-party notetakers, tl;dv, Fireflies and Avoma have native Pipedrive integrations that log notes on the matched record. If you already use Granola or Fathom, keep it and connect it with Zapier or Claude.

Can Claude update Pipedrive from my meeting notes?

Yes. Connect the Granola or Fathom connector and Pipedrive's official connector in Claude, ask Claude to list the planned changes, and approve them. It writes one record at a time and can't merge or undo.

How do I update Pipedrive automatically after a meeting?

With Granola or Fathom, a Zapier workflow can add the summary as a note or activity on the matched person or deal. To update fields, add new people or touch more than one deal, use Claude with both connectors and approve each change. Nova, built into Pipedrive, suggests field updates on one linked record.