Granola API and Integrations: Slack, HubSpot, Zapier Setup

Granola connects to Slack on every plan, the free Basic plan included, and to Notion, HubSpot, Attio, Affinity and Zapier from the Business plan. The public API and webhooks also start at Business. Granola Business costs $14 per user per month, billed monthly.^[1] Enterprise, from $35 per user per month, adds the Audit API, the Legal Holds API and admin control over API scopes. Every native connector sends notes out of Granola into the other tool. Nothing flows back. Our verdict: Basic covers Slack-only teams, and Business is the real entry point for integrations.

What each Granola plan connects to

The plan is set per workspace. Granola bills every active member of a paid workspace at the same plan, admins included, so one person who needs the CRM push lifts the whole team to Business; our Granola pricing guide covers the seat rules. By our arithmetic, five people on Business cost $70 a month, or $840 a year, and ten people cost $140 a month, all billed monthly. Granola sells no annual Business plan. AI clients such as Claude and ChatGPT connect through MCP instead, which works on every plan and has its own guide: Granola MCP setup.

Stage one: Slack and Notion, where the team reads

Slack is the only integration on Basic, and it has a catch. The Granola account must be a Google Workspace or Microsoft 365 sign-in; personal Gmail and Outlook.com accounts cannot connect it. Granola posts a link plus a summary, and only to channels. A private channel needs the Granola app added to it, your access to the channel and the same email address in both apps. A folder can auto-post every new note to a chosen channel, but only notes added after you switch the rule on. Earlier notes stay where they are unless you share them by hand.

Notion needs Business and works more narrowly than most buyers expect. You send notes one at a time from each note's share menu, and only after the note has been enhanced. There is no automatic or bulk sync. Every note lands in the single database Granola creates when you connect; you cannot pick your own page or database. Granola's columns cannot be renamed or removed, although you can add your own. iPhone users share to Notion from the Mac or Windows app. For automatic delivery, Granola points to Zapier: a folder trigger with Notion as the action app.

Stage two: HubSpot, Attio and Affinity for the CRM

All three CRM connectors need Business and match meeting attendees to CRM records by email address. HubSpot and Attio create no contact when no match exists, so the CRM has to hold the person first. Folder auto-sharing works for both, again only for notes added after you enable it. That suits a deals folder pattern: put external calls in one folder, switch on auto-sharing once, and every later note reaches the right record without a click. Notes sitting in the folder before that moment need sharing one by one.

HubSpot asks the most of your setup. The Granola side needs a Google Workspace or Microsoft 365 account, and authorizing the app takes HubSpot Super Admin rights or App Marketplace access. Each note becomes a Meeting by default, or a Note if you prefer, linked to contacts, companies or deals. Custom objects and custom field mapping are not supported natively. Zapier fills that gap. Attio connects through a web sign-in and adds the note to the person or company record you choose, across the standard objects People, Companies and Deals. Custom objects go through Zapier.

Affinity works differently. Each person creates an Affinity API key, which Affinity shows only once, and connects with the same email in both tools. Granola suggests matching People and Company records from attendee emails, then only adds new notes; it never edits or deletes CRM data. For Salesforce, Granola's integration pages route it through Zapier on paid plans, and its pricing page lists advanced integrations such as Salesforce on Enterprise. On Business, plan around Zapier. Our Granola for sales teams guide covers the CRM workflow in depth.

Stage three: Zapier for everything else

Zapier is the bridge to the rest of the stack, and Zapier connects it to thousands of other apps. On the Granola side it needs a paid plan and the desktop app. Two triggers exist. Note Added to Granola Folder fires for new notes only, and Note Shared to Zapier fires when you send a note by hand. Each Zap carries the title, creator, attendees, calendar event, your private notes, the summary in Markdown, the full transcript and a share link.^[2] Granola routes Linear, Jira, Asana and Salesforce through this path.

Building a folder Zap requires the Collaborator or Owner role on that folder. If you belong to several Granola workspaces, pick the right one when you connect the newer Zapier version, or notes from the wrong team start flowing. Zapier bills its own plan separately. Count it in your cost. The payload also changes your privacy picture. The full transcript travels with every Zap, so anyone who can read the destination, a project board or a shared sheet, can read the whole meeting. Send the summary field only when the destination is widely shared.

Stage four: the API and webhooks for your own pipeline

The public API sits at public-api.granola.ai and authenticates with a bearer key. On Business and Enterprise, any member can create personal keys with a Personal notes scope, a Public notes scope or both; admins create workspace keys.^[3] Workspace keys belong to the workspace, never expire and read only public notes plus spaces with API access switched on. Private notes come back only to the owner's own key. Endpoints list and fetch notes, return transcripts, list folders and spaces, and search titles and shared summaries. The API returns only notes that already have a summary and transcript.

Requests are capped per user or per workspace, depending on the key's scope, at a burst of 25 in five seconds and a sustained 5 per second, or 300 a minute; beyond that you get a 429 error. Every key in the workspace, audit keys included, draws on one pool. List pages hold up to 30 notes. A backfill of 3,000 notes therefore needs 100 list calls plus 3,000 fetches, about 10 minutes at full speed by our arithmetic. Transcript pages return 1 to 100 items, and search cursors expire after 15 minutes. There is no sandbox.

Granola suggests testing on a few notes in a dedicated folder instead. Revoking a key is permanent, so rotate by creating the new key first. Speaker labels come through as me and them on desktop transcripts, and an admin can switch off transcript access over the API entirely. Check that setting before you build a pipeline that depends on transcripts.

Webhooks tell your system when to call the API. Three events exist: note.generated for the first AI summary, note.edited for a changed summary and note.access_granted when a note is shared. Granola advises subscribing to both generated and access_granted to discover notes. Payloads carry no note content, so the receiver fetches each note with an API key.^[4] Endpoints must be public HTTPS URLs, can be limited to up to 100 folders, and sign deliveries with a secret shown only once. Your receiver has 15 seconds.

Failure handling deserves a runbook. Granola retries timeouts, 408, 429 and 5xx responses with exponential backoff for four days; redirects and other 4xx codes fail at once. After four days it disables the endpoint and emails its creator or the workspace admins. Events missed while an endpoint is paused or disabled are never delivered later. A scheduled job that lists recent notes and compares them with what your receiver stored closes that gap at little cost against the rate limit.

Enterprise: Audit, Legal Holds and admin scopes

Enterprise starts from $35 per user per month, which by our arithmetic is $21 more per user a month than Business, or $252 a year. It adds governance on top of the same API. Admins choose which scopes members may use for API keys and webhooks: personal, public, both or neither. The Audit API, keyed by a workspace admin in Settings under Connectors, reads only the audit log: sign-ins, note and transcript views, sharing, membership changes, API use, exports, billing events and integration connections. It serves the last year of events, 30 per page, from up to five active keys.

Two blind spots matter. Views by people who open a share link without signing in are never logged, and audit keys share the workspace rate pool, so pace any backfill. For retention beyond a year, pull events into your own system on a schedule. The Legal Holds API, also Enterprise, uses its own admin-created key that can only manage holds. A hold preserves the notes, transcripts and attachments of up to 100 named custodians per request, or of the whole workspace, and custodians see no change in the product. Releasing a hold is final. A reopened matter needs a new one.

The bottom line

Granola's integration story is short and honest. Slack-only teams can stay on Basic. Anyone who wants a CRM connector, Zapier or the API pays Business for every member of the workspace, so decide at the workspace level, not per person. The CRM connectors suit teams whose contacts already live in HubSpot, Attio or Affinity; Notion users accept one fixed database. Developers get a documented API with clear limits, webhooks without content and no sandbox. Compliance teams need Enterprise for audit trails and legal holds.