To connect Granola to Claude, open Claude’s connector settings, search for Granola, sign in to the Granola account holding your notes and enable it for the conversation. Ask Claude to retrieve the exact meeting, extract evidenced decisions and actions, and draft separate customer emails and internal tasks. Check every commitment, owner and deadline before sending.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowGranola already has its own Follow-up emails feature. Use Claude when you need a different layer of reasoning: comparing several meetings, applying a business-specific message template or turning discussion into an internal action list alongside the customer reply. For a simple single-meeting recap, first check whether Granola’s existing workflow is sufficient.
Which meeting should Claude use for a follow-up email?
Claude should use the one specific meeting the follow-up is about, identified by title, date and participants, because two calls about the same job can hold different prices and next actions.
A follow-up should describe a particular discussion, not everything Claude can find about a customer. Begin with the meeting title, date and relevant participants, then ask for the source note. Confirm it is the right conversation. Two calls about the same job can contain different prices, assumptions and next actions.
Granola’s connector uses MCP, Model Context Protocol, to let an assistant work with accessible meeting information. Its documentation lists searching notes, retrieving notes, finding decisions and extracting action items. These are useful inputs to drafting, but they do not make every sentence in an enhanced summary an agreed commitment. Keep the distinction between evidence and proposed wording visible.
Make the desired output concrete. A removals firm may need one customer email confirming outstanding inventory questions, plus a staff list covering vehicle checks and packing estimates. Combining these into one recap could disclose internal staffing concerns. Ask for separate audiences from the start and tell Claude which information belongs only in the staff version.
Decide whether earlier meetings are needed. For a routine appointment recap, one note may be enough. For a changed service requirement, retrieve the earlier discussion as well and ask Claude to identify what changed. Do not request the customer’s entire meeting history unless the task actually needs it. A smaller evidence set is easier for the sender to verify.
How do you connect Granola to Claude and check the active workspace?
Connect Granola by opening Claude’s connector settings, selecting the official Granola connection, authenticating, enabling it for the conversation and then confirming which account is active.
- Open Claude’s connector settings and search for Granola.
- Select the official connection and complete Granola authentication.
- Sign in to the Granola account containing the intended meeting notes.
- Enable the connector for the conversation.
- Ask “Which Granola account am I signed in with?”, which Granola says returns the connected email and active workspace.
- Retrieve one harmless known note and compare its title and content with Granola.
Granola’s current setup instructions describe connecting through Claude’s settings, while Claude’s general connector guidance uses Customize > Connectors. If the entry point differs in your interface, use the connector-management area rather than creating an unrelated custom connection. On Claude Team or Enterprise, arrange the necessary organisation enablement with the owner first.
Granola says MCP operates as an individual user in the active workspace. It does not combine notes across workspaces, and notes originating in a different workspace are excluded even if sharing makes them visible elsewhere. If a meeting seems missing, inspect the connected account and workspace before assuming the notes have disappeared. When the account is right but the workspace is wrong, switch it in the Granola app or ask Claude to switch; Granola notes that a switch made through the connector also changes the active workspace in the app and in any other AI tool connected to your account.
Its Basic (Free) plan exposes accessible personal and public notes from the last 30 days. Transcript tools and tools that change notes or folders require a paid plan. Business provides accessible personal and public notes, while Enterprise administrators determine note scopes. Check these boundaries before asking for a comparison across several months or promising transcript-level verification.
Paid Granola connections can also change notes and folders. Granola’s documentation lists tools that create and rename folders, add notes to or remove them from folders, add text to a meeting’s private notes and regenerate a summary; which ones appear depends on your plan and assistant, so check the list on Granola’s page under Customize > Connectors. Adding a note to a folder makes it visible to everyone with access to that folder, which is a disclosure decision rather than tidying. For a follow-up drafting pilot, set those tools to Blocked under Tool permissions. On Enterprise, an admin can make the connection read-only for the whole workspace by turning off Organise notes, Edit notes and Send feedback in Granola’s MCP access settings.
Allocate an illustrative 25 minutes to connect, verify the workspace and test one note. If the test fails, record the symptom precisely: wrong account, right account but wrong workspace, unavailable note or missing transcript access. Repeatedly asking for a better email will not fix a retrieval problem. Keep the manual note-to-draft route available while access is corrected.
How should you tell people their meeting information will be used?
Tell people how their meeting is recorded and used before collecting notes, follow your business’s consent requirements and give participants a way to object.
Before collecting or using meeting information, explain the note-taking process and follow the business’s consent requirements. Give participants a way to object and agree an alternative where necessary. Ask the appropriate adviser about legal obligations if the discussion includes sensitive material. Do not assume that a technically accessible note is appropriate to reuse for every purpose.
Suggested meeting wording: “We use AI-assisted notes to help record decisions and prepare follow-ups. We may use those notes in our approved assistant to draft the message and action list, and a person checks them before sharing. Please tell us if you prefer a different approach.”
That wording is a starting point for your policy, not a statement that it satisfies every consent rule. Adapt it to what the business actually does. If you only use manually written notes for a meeting, say that. If the notes will be shared beyond the attendees, establish the intended audience rather than implying the material stays with the sender.
For an illustrative tutoring-centre meeting, a family explains a sensitive personal circumstance while discussing lesson arrangements. The external follow-up needs the agreed scheduling action, not a detailed retelling of the circumstance. Remove unnecessary personal detail from the drafting input or output according to your policy. Ask for human handling when the context requires judgement the routine template cannot supply.
Reconcile a removals job across two conversations
In a fictional planning exercise, a removals firm first discusses 40 boxes and later receives an update to 55. The revised discussion also adds packing help for two fragile items. The customer has not yet confirmed access arrangements. The owner wants a follow-up that reflects the latest information without treating the change as an accepted new quotation.
Retrieve both specific meetings and request a change table. The older note is context; it is not the current instruction where the newer note clearly replaces it. Ask Claude to cite the relevant note for each changed fact and mark uncertainties. Do not let it average the two box counts or select the lower figure because it makes the message simpler.
| Illustrative item | Earlier note | Later note | Follow-up treatment |
|---|---|---|---|
| Box estimate | 40 | 55 | Use 55 as the latest estimate |
| Fragile items | No packing request recorded | Two items need packing help | Confirm details before pricing |
| Access | Unconfirmed | Still unconfirmed | Ask customer for missing information |
| Revised price | Original quotation exists | No replacement price agreed | Do not invent an accepted total |
The operational difference is 15 additional boxes, a 37.5% increase over the earlier 40-box estimate. That arithmetic helps the owner see why the change matters. It does not prove the price should rise by 37.5%; pricing may depend on labour, access and other agreed factors. Keep the calculation out of the customer email unless it serves a clear purpose.
Use only the two Granola meetings I identify.
Extract: confirmed decisions, changed facts, unresolved questions.
For each item include the meeting source and supporting wording.
Do not turn possibilities into promises.
Then draft:
1. A customer email with confirmed points and questions.
2. An internal action list: task, owner, due date, evidence.
Mark absent owners or dates as unconfirmed.
Do not send email, create tasks or edit notes.
An illustrative customer draft reads: “Hello [first name], thank you for the updated inventory. We have noted your current estimate of 55 boxes and the request for packing help with two fragile items. Please confirm the access details so we can review the arrangements and any quotation changes. [your name].” The sender should check the actual note and quotation before using it.
The internal list contains a different message: estimator to review the box increase, operations lead to assess packing requirements and account owner to obtain access information. No deadline was agreed in the source, so each date remains unconfirmed. If the owner chooses internal deadlines afterwards, label them as management assignments rather than decisions made in the meeting.
If you want help fitting meeting notes into how your business actually runs, I offer one-to-one AI consultations for small businesses.
How do you turn meeting notes into a task with an owner?
A good task has a verb, an output, an accountable owner and a timing decision, and where the meeting names no owner you should ask for a decision rather than guess.
A task needs a verb, an output, an accountable owner and a timing decision. “Access” is a topic, not a task. “Account owner to obtain the customer’s access details before the quotation review” gives the team something to do. Where the meeting does not supply an owner, ask for a decision instead of guessing from job titles.
Ownership is where drafts most often overreach. In a bookshop’s supplier call, the note says, “Could someone check the display measurements?” Claude assigns the task to the bookseller who spoke most often. That is not evidence of responsibility. The corrected row is “Check display measurements; owner unassigned; timing unconfirmed”. The manager can then assign the job deliberately.
Dates overreach in the same way. During a landscaping estimate, a speaker says, “We could start after the materials arrive.” An illustrative bad output gives a definite start day. The correct output preserves the dependency: “Proposed start follows material availability; date not agreed.” The owner can ask the supplier about delivery before making a customer commitment.
Do not claim the Granola connector creates tasks in an unrelated task manager. A task list in chat is a prepared artefact. Writing those tasks into another application requires that application’s connection and a separate permission decision. For a small pilot, copying accepted rows manually may be the clearest handover.
When you need that later step, the meeting-notes-to-task workflow explores the wider handover. First test whether the extracted actions match the meeting. Automating inaccurate owners and dates would only distribute the errors faster.
Assign a stable reference to each accepted action in your working list, such as MOVE-07. This is your convention, not a Granola feature claim. Include the source meeting beside it. When the same issue returns next week, the sender can distinguish an existing task from a new request and avoid creating duplicate work.
How should a customer follow-up email be structured?
A customer follow-up email should state its purpose, the confirmed points, the customer’s action and the business’s action, and leave out transcript detail that supports none of them.
Use a short customer-email structure: purpose, confirmed points, customer action and business action. Keep background only where it helps the recipient understand the request. A transcript can contain many interesting details that do not belong in a follow-up. Ask Claude to remove material that does not support a decision or action.
Hello [first name],
Thank you for discussing [specific purpose].
Confirmed: [only evidenced decisions].
Please send or confirm: [one clear customer action].
We will: [approved business action, with confirmed timing only].
Still open: [uncertainties that affect the work].
[your name]
Options are not bookings. A tutoring centre discusses four possible lesson slots but agrees none. An unsuitable draft says, “Your weekly slot is now booked.” A useful draft says, “Please tell us which of the four discussed options you prefer; we will confirm availability before booking.” Review the calendar or booking record separately before promising a place.
Enquiries are not orders either. A bookshop asks a supplier about ordering 20 copies but receives no price confirmation. Claude turns the discussion into “We confirm our order for 20 copies”. Change it to an enquiry for a quotation if that reflects the discussion. The difference between exploring an order and placing one is a business decision, not merely a tone choice.
Internal remarks need filtering out. The removals team records an internal concern that an additional vehicle may be needed. The customer follow-up should request the missing inventory information or explain an approved change. It should not disclose speculative internal staffing comments. Review both the source audience and the intended recipient before retaining a sentence.
The manual transcript-to-follow-up tutorial is useful when a connector cannot retrieve the right notes or you want to supply a tightly selected extract. Keep the same evidence discipline whichever route you use: no source, no claimed agreement.
Can Claude send the follow-up email through Gmail?
Only if you connect Gmail separately, because Granola’s connection gives Claude no Gmail access; then set Gmail’s send, reply and forward tools to Needs approval or Blocked, and pick Manual mode so each message waits for you.
The Granola connection supplies meeting context; it does not itself give Claude access to Gmail. If you want email actions, connect and assess Gmail separately. Anthropic’s Workspace documentation says Gmail can send, reply and forward, asking for approval by default outside Auto mode. Auto is the catch. It is becoming the starting mode on Pro, Max, Ultra and Team plans, and in it a send tool marked Needs approval can go out with no prompt at all if the automated review sees nothing risky. For follow-ups, set Gmail’s send, reply and forward tools to Needs approval or Blocked, pick Manual in the chat’s mode selector, and approve each message with Allow once.
Start with the message in chat and copy the accepted text into the chosen email thread yourself. That keeps recipient selection and sending visible during the first trial. If you later enable Gmail actions, inspect the exact available draft or send operation and its permissions. Do not assume every request to “draft” stays inside the conversation.
Use the Google connector safety tutorial before adding mailbox access. Check the To and CC fields, existing thread, quoted material and attachment choices separately from the body. A correct recap addressed to the wrong customer is still a failed handover.
Granola’s own Follow-up emails feature drafts from the transcript, calendar and past Gmail threads, and it is narrower than it first looks. It needs a paid plan or active trial, Google sign-in and Gmail connected with read and send access; Outlook is not supported yet. A draft appears only when the meeting had at least one external guest and no more than ten people, and Granola stays quiet when Slack is the active channel, a colleague owns the follow-up or a blocker comes before any next step. Drafts stay on the home screen for three days, and edits to them are saved on your device only.
| Situation | Granola’s own follow-up | Claude with the Granola connector |
|---|---|---|
| One external meeting, Gmail, paid plan | Usually enough on its own | Adds little beyond your template |
| Internal meeting with no external guest | No draft is generated | Can turn the note into an internal action list |
| Outlook mailbox | Not supported yet | Drafts text you paste into Outlook yourself |
| Several meetings about one job | Drafts from one meeting plus past Gmail threads | Compares the notes and flags what changed |
| Basic (Free) Granola plan | Not available | Works with notes from the last 30 days |
Choose Claude for the cross-meeting comparison and customised action analysis you actually need, rather than connecting another assistant without a clear reason.
Make one person responsible for sending. If Granola has already suggested a follow-up and Claude has prepared another, choose one approved version and check whether anybody has replied since the meeting. A later customer answer may make the original follow-up obsolete. Read the current thread immediately before sending an older draft.
How do you test a Granola follow-up workflow before relying on it?
Test the workflow with a pilot on six authorised meetings, manually verifying every claimed decision and counting wrong owners, invented deadlines and missing changes.
Run a pilot on six authorised meetings and manually verify every claimed decision. Count wrong owners, invented deadlines, missing changes and unnecessary disclosures. Include an intentionally ambiguous note in the sample. A reliable process should expose uncertainty rather than produce a polished answer to every incomplete record.
Set an illustrative pass standard of no invented commitments and all externally stated facts traceable to an accepted source. This is an owner-designed standard, not a vendor accuracy guarantee. Record correction time separately from drafting time. If most messages need substantial reconstruction, improve note-taking or narrow the drafting task before expanding the connection.
For a simple cost exercise, assume six manual follow-ups take ten minutes each, including the task list: 60 minutes. Suppose the pilot takes three minutes to retrieve and draft each meeting plus five minutes to review: 48 minutes. The difference is 12 minutes. At an illustrative $25 hourly internal rate, that is $5 of staff time before subscriptions, setup and any additional tools.
A different result may still justify the process if it catches changes between meetings that staff previously missed, but record that outcome honestly. Do not count an avoided mistake as a monetary saving unless there is a defensible basis. Keep the business case tied to observed review effort, accepted outputs and operational usefulness.
Resolve missing notes without rebuilding the whole connection
If a note cannot be found, check account, active workspace, note sharing and plan history limits in that order. On Basic, a meeting outside the last 30 days is a documented scope issue. Do not describe it as an absent customer decision. Use the original source manually if policy permits, or change the comparison to accessible meetings.
If the note is available but the evidence is unclear, inspect the original note and any transcript access your plan permits. A note summary that omits a deadline does not prove no deadline was discussed. Mark the item unresolved, ask the relevant participant and record the correction. Keep that clarification distinguishable from the original meeting evidence.
Before handing the workflow to a colleague, give them an accepted example with its source notes and one rejected draft. Ask them to identify the incorrect commitment and produce the corrected email and task list. The handover is ready when another sender can reproduce the checks, including deciding that no email should be sent.
Retain a short correction log for the pilot. Record the source phrase, the misleading draft and the accepted replacement. For instance, “discuss packing options” becoming “packing included” is a scope error, while a duplicated task is a tracking error. Different error types need different changes to the instructions. Review the log after the six-meeting sample and update the relevant prompt or human check before using it again.
If you log the pilot's corrections in a spreadsheet, The Complete Excel Course with AI Integration on Coding Liquids covers the spreadsheet side.
Decisions before expanding meeting follow-ups
Should every meeting produce a customer email?
No. Decide whether a message will help the recipient act or confirm an important decision. An internal planning discussion may need only an action list, while a customer meeting with no agreed next step may need a clarification. Avoid sending a polished recap merely because a draft is easy to generate.
Who should approve a follow-up when several staff attended?
One accountable sender. Choose that person before drafting. Other attendees can check statements about their work, but one person should resolve corrections and approve the message. Keep the accepted draft identifiable so separate colleagues do not send competing summaries or repeat a request the customer has already answered.
Can a follow-up email replace the approved quotation?
No, not unless your business deliberately approves that role. Treat the follow-up as a record of discussion. Changes to price, scope or contractual obligations need the normal commercial review. Link to the accepted quotation where appropriate and ask a qualified adviser about legal questions rather than relying on an AI recap.
How do I connect Granola to Claude?
Open Claude’s connector settings, search for Granola, select the official connection and complete Granola authentication, then enable the connector for the conversation. Ask “Which Granola account am I signed in with?” to confirm the connected email and active workspace, and retrieve one harmless known note to compare with Granola.
Does Claude send the follow-up email itself?
Not through the Granola connection, which supplies meeting context only and gives Claude no Gmail access. If you want email actions, connect Gmail separately, set its send, reply and forward tools to Needs approval or Blocked, choose Manual mode in the chat, because Auto mode can send without a prompt, and approve each message yourself.
Further reads
- Asana AI Teammates: Prepare Meetings and Chase Follow-Up Tasks — Set up one Asana AI Teammate to brief a weekly meeting and chase the follow-ups, with a request budget a six-person team can afford.
- Which Claude Connectors Should a Small Business Switch On? — Nine Claude connectors by job (email, calendar, files, accounts, CRM, payments, jobs, meetings, contracts), with what each sees and changes.
Browse all AI-for-business tutorials
Sources: Granola Docs, Granola MCP and Follow-up emails; Claude Marketplace, Granola; Claude Help Center, Use connectors to extend Claude's capabilities, Use Google Workspace connectors, and Get started with Claude Cowork; Claude Docs, Get started with connectors. Verified 18 November 2026.
