Lindy helps users create AI assistants for business tasks. It is useful for repeatable work around communication and operations, especially when a team…
Lindy
Explore features, practical uses and pricing below.
Lindy is an AI teammate that works with connected business applications, email, calendars and meetings. You can ask it for a project brief, a draft reply or a report, then turn recurring work into a routine. Its shared Slack experience sits alongside personal account connections, so the information and actions available depend on the conversation and connected accounts.
The meeting library stores recordings, transcripts and summaries from supported Google Meet, Zoom and Microsoft Teams calls. Folders can collect related calls and be private, shared with selected people or visible to a team. Asking across a customer folder can help identify unresolved implementation questions without opening every transcript separately.
The email-drafting routine saves proposed replies in the connected inbox’s drafts folder for review, editing and sending. Tone instructions and situations to skip help define its scope. Meeting preparation, inbox labels and scheduling are separate capabilities; installing the team app does not connect everybody’s personal mailbox or calendar.
Memory exposes the files Lindy uses, with personal, team and system scopes and version history. You can correct durable context rather than repeating the same instruction in every request. Team files are visible across the workspace, while editing rights differ from personal files.
Skills describe reusable procedures, such as the sections and source requirements for an account handoff. A routine supplies the trigger, task instructions and destination. Scheduled or event-triggered routines can therefore apply a procedure repeatedly. Administrators manage workspace routines; individuals can manage personal ones.
Lindy suits professionals handling frequent correspondence and teams that coordinate through shared conversations. A customer-success lead could connect the relevant accounts, place onboarding meetings in a restricted folder and teach a handoff skill containing agreed scope, outstanding questions and next steps. After a call, request a draft from that folder, check the meeting references and review any proposed CRM update.
For a recurring Monday report, specify the reporting period, source accounts and delivery channel. The documented dry run uses real reads while suppressing writes and sends, giving you a way to inspect the proposed result before activating delivery. Check the final connection separately because a dry run does not execute that write.
A transcript can misstate a name or miss a qualification, and memory can preserve outdated process information. Keep uncertainty visible when a source never assigned an owner or agreed a deadline. Connected-account permissions and action approvals determine which operations can run; they do not establish that a generated decision is appropriate.
Hosted artifacts have a further boundary: their default access is the signed-in workspace, rather than only the creator. Public publishing opens the page to anyone with the link. Check the contents and audience before sharing a dashboard assembled from internal information.
The pricing page offers introductory credits, paid team usage and enterprise arrangements. Credits measure work and are pooled across the team; heavier reports and builds consume differently from short lookups. Compare active users, recurring task volume and required controls when evaluating access. Confirm the current account terms instead of assuming every listed capability has identical limits.
Start with the official website and setup guide to check the connections needed for your process.