Lindy Meeting Notes: How to Set Up Its AI Note Taker

Lindy (often searched as Lindy AI) takes meeting notes by joining your Google Meet, Zoom or Microsoft Teams calls as a visible, named participant, then recording, transcribing and capturing decisions, notes and action items in a searchable meeting library ^[1]. Setting it up comes down to four choices: which calls it joins, where each recap lands, who can see each folder, and what should happen once the call ends. The one hard requirement is a connected Google Calendar or Outlook calendar. Lindy's usage docs rate meeting recaps and notes as a Low credit cost, so notes are one of the lighter jobs in the plan. Our read: it pays off for teams that want each call to turn into work.

Before Lindy joins a call: calendar, seat and credits

Lindy finds your meetings through the calendar, so recording only starts once a Google Calendar or Outlook calendar is connected. Meeting recording is one of Lindy's built-in routines, next to meeting prep and meeting scheduling, and each one is switched on or off per connected account. That matters if you connect a work and a personal calendar. You can record client calls on one and leave the other alone. In a team, the usual order runs like this: an admin adds Lindy to Slack, each teammate links with one tap, then everyone connects their own email and calendar.

Every person who uses Lindy is a billed seat, whether they sign up, join the workspace or @mention Lindy in Slack for the first time. Lindy's pricing page starts at $29.99 per user a month for 3,000 credits; on some visits the same page opens at $49.99 per user a month for 5,000 credits instead. For a five-person team, by our arithmetic, the bill comes to $149.95 a month with 15,000 pooled credits on the lower opening, or $249.95 a month with 25,000 credits on the higher one. A new account starts with $50 in credits, no card, valid for 7 days.

Credits come out of one shared workspace pool. Lindy's usage docs put meeting recaps and notes in the Low band and meeting prep in the Very low band ^[2]. Notes themselves stay cheap. Follow-up chats do not. Lindy's docs say every message in a thread re-reads everything above it, so long threads cost more credits with each turn. Monthly credits reset each cycle without rolling over, and when the pool runs dry Lindy pauses its work until the reset or a top-up rather than billing overage.

Deciding which calls Lindy sits in on

The recording settings give you three scopes: all meetings, internal meetings only, or external meetings only. Lindy joins as a named participant that everyone on the call can see, attendees are told it is present, and you pick the display name it shows. A sales team usually wants external calls, where the CRM follow-up lives. A product team might want internal standups instead. Pick the scope before the first busy week, because a recorder that joins every call also files every call.

Visibility is not the same as consent. Lindy's Terms put the duty on the user to follow any law that requires notice to, or consent from, the people being recorded ^[3]. That duty stays with you. In practice, a team that records clients should decide how it tells them, whether through a line in the calendar invite or a word at the start of the call, and keep doing it the same way every time.

Where each recap lands after the call

Recording settings also decide where the recap goes and whether participants get it by email. Lindy's meetings page says its notes support 80+ languages and that the meeting agent can post notes to Slack. The recap is a custom summary rather than a fixed template. Each recap carries the action items Lindy captured, and the full recording and transcript stay in the library behind it for anyone who needs the exact wording.

Privacy follows the meeting, not the channel. Meetings stay private unless someone shares them, and personal context stays out of shared Slack channels. So a recap from your one-on-one with a client does not surface in a team channel because a colleague asked a broad question there. Emailing the recap to every participant is a separate switch. Leave it off for sensitive calls and turn it on where attendees expect a written summary, such as a weekly status meeting.

Building a shared meeting library with folders

The library is where notes become team memory. Folders can be shared with only you, specific people or your entire team, and one meeting can sit in more than one folder ^[1]. Shared Team Meetings folders arrived in August 2026. You set a rule for each folder, and Lindy suggests matching meetings by title, participants and content. By default, a suggested meeting joins the folder only after you approve it, which keeps an off-topic call out of a client folder.

A simple structure works well: one folder per client or account, one for internal planning, and one private folder for calls you do not want to share. Because a meeting can live in several folders, a renewal call can sit in both the client folder and a sales pipeline folder. Read each suggestion before you approve it. A wrong call in a shared folder is visible to everyone who can open that folder.

Asking questions across past meetings

Once calls are filed, you can ask questions of one meeting or across a whole shared folder, and Lindy answers only from meetings you have access to. It can recall what someone said, the action items and the commitments made. You can also ask about past meetings by text, through iMessage or SMS, without opening the web app. That makes the library useful in the minutes before a call, when you want to know what was promised last time.

Where you ask matters. The full toolset, including meeting reads, works in your DMs with Lindy and in your own threads. In shared Slack channels Lindy works from web search, image generation, public Slack search and Notion. Research you ask for in a channel is visible to the whole channel, while the same request in a DM stays private. Ask about client meetings privately. Then share the answer on purpose.

Turning the call into follow-up work

This is the real payoff. Notes alone are not. Follow-up actions run after a call through your connected tools: updating a HubSpot deal, sending a Slack DM of action items or creating a Notion page. Lindy's meetings page adds updating the CRM, drafting the follow-up email and scheduling the next meeting, and Lindy can remind you when a recipient does not reply. Routines can also fire on a meeting start or end, so a debrief can run without anyone asking.

By default, anything with outside impact, such as sending that email or updating a deal, waits for approval, and email drafts land in your drafts folder until you approve them. Once the drafts read right, recurring follow-ups can be switched to auto-send. Meeting prep closes the loop from the other side: before each call Lindy can send external attendees' job titles, companies and LinkedIn profiles plus summaries of past meetings with the same people. Booking that next call is covered in our scheduling assistant guide, and the CRM side in Lindy for sales teams.

Lindy's own comparison page says typical note takers stop at the notes, while Lindy also preps an agenda, drafts follow-ups, updates the CRM and schedules meetings. Clinics weighing Lindy as a scribe have a different gate: HIPAA-covered work needs the Enterprise plan with a signed BAA, covered in Lindy for healthcare.

Which teams should hand their calls to Lindy

Lindy earns its seat as a note taker when the call is the start of the work, not the end. Sales and account teams that update HubSpot, send a recap and book the next meeting after every client call get the most from it, because the notes, the library and the follow-up run in one place, with approvals by default. A team that only wants transcripts pays a per-user seat for capabilities it will not touch. Start with external calls, one client folder and follow-ups left on approval.