Connect Granola to Centralize

Connect Granola to Centralize so your AI meeting notes automatically flow into your account activity, engagement heat map, and relationship data.

Contents

• Before you start

• Connect Granola

• Import history

• How Granola data appears in Centralize

• A note on transcript attribution

• Troubleshooting

• Need help?

Before you start

• Admin or Owner only. This is an organization-level integration — the same permission tier as Outreach and Salesforce. Only admins and owners can connect Granola on behalf of the workspace.

• Granola Business plan required. API access is only available on Granola's Business plan. You'll need a Granola API key to complete setup — check your Granola account settings or reach out to your Granola admin.

Connect Granola

1. Navigate to Integrations in the left sidebar.

2. Find the Granola card and click Connect.

3. Paste in your Granola API key.

4. Click Save. The integration status will update to Connected.

Once connected, Centralize will begin ingesting Granola meeting notes. New calls will appear as they sync from Granola.

Import history

Connecting Granola doesn't just capture future meetings — it also pulls in your past ones. This matters because relationship data is only as good as the history behind it. Without past calls, your heat map, engagement scores, and activity bars would start from zero, even if you've been meeting with accounts for months.

When you connect Granola, Centralize automatically imports all meeting notes from the past 12 months. You don't need to do anything to trigger this — it happens as part of the initial sync.

What to expect:

• Historical calls appear automatically — meetings from up to one year back will be ingested and attributed to the correct accounts and contacts.

• Activity data is backfilled — heat map engagement, org chart tinting, and activity bars will reflect your historical Granola meetings, not just new ones going forward.

• Allow time for the initial sync — depending on how many past calls you have, the import may take a few minutes to complete.

How Granola data appears in Centralize

Granola calls are treated the same as Gong and Fireflies and will trigger an activity recompute across your accounts.

A note on transcript attribution

Known limitation: Granola's API does not provide per-speaker identity in transcripts.

Unlike other call recorders like Gong or Fathom, Granola only distinguishes between the note-taker's microphone ("me") and all other audio captured by the system ("the other side"). This is a constraint of Granola's API.

What this means in practice:

• 1:1 calls — Centralize can reliably infer that "the other side" is the customer and attribute transcript content accordingly.

• Multi-party calls — If teammates and customers are both on the call, their voices are lumped together in the system audio bucket. Centralize cannot reliably separate who said what.

What still works correctly:

• The touchpoint is attributed to the right account and participants (via calendar attendees and emails).

• Heat map engagement, org chart tinting, and activity bars all reflect the call accurately.

• Transcript content is attributed at a rep-vs-account level rather than a person-by-person level.

If accurate per-contact transcript attribution is important for your workflow, Gong or Fireflies will provide more granular data.

Troubleshooting

Need help?

Reach out to support@usecentralize.com.