Lindy
Also known as: Lindies, Lindy Autopilot
Lindy is an AI teammate that lives in Slack, answers from your tools and meetings, and runs multi step work with approvals built in.
Lindy is an AI teammate that lives in a company's Slack workspace, where everyone gets a private assistant in their DMs and the whole team shares one in channels. It is built to be delegated to in conversation. Ask a question and it answers from your tools and meetings with the underlying file or decision attached, hand it a task and it runs the multi step work across systems from start to finish, or ask for an artifact and it produces decks, sheets and reports.
The product is organized around five capabilities. It connects to Gmail, Slack, Notion, HubSpot and over a thousand other tools plus any MCP server, and where no programmatic interface exists it can drive a cloud computer directly. It joins meetings on Google Meet, Zoom and Teams as a visible participant, then records, transcribes and files them into a searchable library of shareable folders.
Routines carry recurring work on a schedule, from morning briefs to weekly reports. It ships with more than forty skills covering research, analysis, decks and dashboards, and a team can add their own by demonstrating a task once. Its memory lives in a versioned system of plain files the customer can open, read and edit like a document, split between personal and workspace scope.
By default, anything with outside impact (sending an email, updating a ticket, posting to another channel or publishing a document) waits for a named approver, while read only lookups from approved sources proceed. Permissions are set per integration and revocable, private Slack channels are reachable only by invitation, and personal DMs, email and meetings never surface in shared channels.
Pricing is per seat with a shared credit pool the whole workspace draws from, starting at $30 per user per month. The platform is model agnostic, letting the customer pick a model per task, and carries SOC 2 Type II, GDPR, HIPAA and PIPEDA, with SSO and SCIM on the Enterprise tier. It is delivered as managed SaaS only, with no self hosted, VPC or region selection option.
Vendor details
Canonical URL
https://www.lindy.ai
Category
Agent builder
Subcategory
Slack-resident AI teammate with meetings, routines, skills and editable file-based memory
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Lindy connects to Gmail, Slack, Notion, HubSpot and 1,000+ tools, plus any hosted MCP server, and builds actions from the tools that server publishes. A credentials vault stores an API key once for personal or workspace use without pasting it into a chat, and guardrails set per integration control what Lindy may do with each connection. An HTTP Request skill covers anything uncatalogued, and a Pipedream partnership contributed 500+ actions across 200+ apps. Where no interface exists at all, computer use gives the agent a cloud machine to drive the screen directly. Lindy works through Slack threads and mentions, iMessage and SMS, Gmail via a Chrome extension, and Google Meet, Zoom and Teams, which it joins as a visible named participant to record and transcribe. Other systems can call it through a webhook trigger secured with a bearer token, with a callback response.
In practice
Someone asks in #growth why signup conversion dropped. Lindy traces it across four tools to a broken verification step after Tuesday's deploy, writes up the root cause, files the ticket and flags the deploy in #eng.
A deal closes and the handoff needs doing. Lindy updates HubSpot, creates the Notion doc, posts to customer-success, schedules the kickoff and sends the welcome email, pausing for approval on anything that leaves the building.
You were out for a week. Lindy gives you the TL;DR of the busy channel, what was decided, and exactly what still needs you, drawing on meetings it recorded while you were away.
Sources & related URLs
Related / legacy domains
Agentic Index coverage score
10.5 / 14 capabilities · 75%
| Integrations & Tool Calling | Full |
|---|---|
|
Connections cover Gmail, Slack, Notion, HubSpot and 1,000+ tools plus any hosted MCP server, and Lindy builds actions from the tools such a server publishes. A credentials vault saves an API key once and shares it with the workspace without it being pasted into a chat, and per-integration guardrails control what Lindy may do with each connection. An HTTP Request skill covers anything uncatalogued, and a Pipedream partnership adds 500+ actions across 200+ apps. Older Lindy material claims 3,000+ integrations, against 1,000+ today. Sourcedocs.lindy.ai integrations, credentials and MCP pages, lindy.ai/changelogread 2026-08-31 |
|
| Workflow Orchestration | Partial |
|
Lindy runs multi-step work across tools from start to finish as one agent. A deal handoff, for example, updates HubSpot, creates a Notion doc, posts to a channel, schedules a kickoff and sends a welcome email. Routines run saved instructions on a schedule, and skills act as reusable playbooks it picks up on its own. There is no branching or conditions, no multiple coordinating agents or sub-agents and no flow surface the customer configures, because the planning is the agent's own. Sourcedocs.lindy.ai llms.txt index, routines and skills pagesread 2026-09-29 |
|
| Knowledge Grounding & RAG | Full |
|
Lindy records and transcribes meetings on Google Meet, Zoom and Teams and files them into a searchable library of shareable folders that can be queried later, with a shared meeting library and folders on every plan. Grounding also spans Slack history and connected tools, answers come back with the underlying file or decision attached, and a versioned team file system holds documents Lindy works from. Ad hoc knowledge lookups are a supported way to delegate work, and persistent workspace context is included. Sourcedocs.lindy.ai meeting-library, files and ad-hoc-tasks pages, lindy.ai/pricingread 2026-08-31 |
|
| Human Oversight & Guardrails | Full |
|
Approvals are built into every plan, and Lindy states that nothing irreversible happens without approval. Anything with outside impact, such as sending an email, updating a ticket, posting to another channel or publishing a doc, waits for a named approver, while read-only lookups from approved sources proceed without one. Integration-level guardrails control what Lindy may do with each connected tool, permissions are set, changed and revoked by the customer, and channel scope is explicit, with private Slack channels reachable only if a channel manager invites it. Sourcelindy.ai/pricing, lindy.ai/security and docs.lindy.ai integrations overviewread 2026-08-31 |
|
| Security, Identity & Governance | Full |
|
Lindy is SOC 2 Type II certified, with the audit attributed to Johanson Group, and also covers GDPR, HIPAA and PIPEDA. A Drata-hosted trust center takes requests for reports and compliance summaries, and a named security contact handles architecture detail and penetration-test results. Customer facing controls include permissions the customer sets, changes and revokes per integration, encryption in transit and at rest, a commitment that data is never sold or used for model training, deletion and access rights, and on Enterprise SSO, SCIM and a signed BAA. Lindy says it also runs regular vulnerability scanning and penetration testing, real-time monitoring and a defined incident-response playbook. SSO and SCIM are Enterprise only, so self serve plans rely on permissions per integration and on encryption. Sourcelindy.ai/security, lindy.ai/pricing and app.drata.com trust centerread 2026-08-31 |
|
| Observability & Auditability | Partial |
|
Team files carry version history and the meeting library is searchable and shareable, both on every plan. The current Teammate product has no logging, tracing or audit feature, and audit logs come only on Enterprise, with no description of what they record. A per-run task view showing the received request body and how each action field was completed exists only in the legacy builder, outside the current product. Lindy does not say what record of agent actions an admin can see and export. Sourcelindy.ai/pricing, lindy.ai/security, docs.lindy.ai index and docs.lindy.ai legacy webhooks pageread 2026-08-31 |
|
| Memory & State Persistence | Full |
|
Files is a versioned file system the customer can see into, edit and share, and it contains the memory folder where what Lindy knows is kept in plain files that can be opened and changed like a document, such as recurring report timing and individual formatting preferences. Persistent workspace context and team files with version history come on every plan. Memory is scoped personal or workspace, with personal context never surfacing in shared channels, and skills persist demonstrated procedures for reuse across the team. Sourcedocs.lindy.ai files and skills pages, lindy.ai/pricingread 2026-08-31 |
|
| Deployment & Data Residency | Not documented |
|
Deployment is managed SaaS only. Lindy supports data deletion requests, access rights and residency requirements but names no region, no selection control and no deployment topology, describing its infrastructure only as enterprise-grade cloud with hardened access controls and logical separation between customers. There is no VPC, on-premises, self-hosted, dedicated-cluster or region-selection option. Enterprise adds identity, audit and BAA terms. Sourcelindy.ai/security, lindy.ai/pricing and docs.lindy.ai indexread 2026-08-31 |
|
| Prebuilt Agents, Templates & Packs | Full |
|
The product ships with 40+ skills covering research, data analysis, decks, dashboards and channel catch-ups, included on every plan along with the option to create more, and the agent picks them up on its own as reusable playbooks when a request calls for them. Customers add their own by showing Lindy a task once, after which it is saved for the whole team, and individual skills can be installed and toggled on or off. A creators program publishes further material. Sourcedocs.lindy.ai skills page, lindy.ai/pricing and lindy.ai homepage skills panelread 2026-08-31 |
|
| Triggers & Channel Coverage | Full |
|
Routines handle schedules, as saved instructions that run recurring work automatically such as daily briefs, meeting follow-ups and weekly digests. Events include a reply being needed in the inbox, a meeting ending, time-sensitive mail triggering an outbound text alert, and a sent email going unanswered prompting a follow-up draft. Work arrives through Slack threads and mentions, iMessage and SMS, Gmail through a Chrome extension, and Google Meet, Zoom and Teams, which Lindy joins as a named visible participant. Slack-native threads, scheduled routines and 24/7 iMessage come on every plan. Sourcedocs.lindy.ai routines, iMessage, meeting-recording and chrome-extension pages, lindy.ai/pricingread 2026-08-31 |
|
| Model Flexibility & Routing | Full |
|
Every plan includes model selection across all models. The product is model agnostic, with the customer picking a model for each task from most major models, and individual models are added over time, including Gemini 2.5 Flash-Lite for phone calls and Gemini vision for shared images. Selection is per task rather than per workspace, so different work can run on different models within one seat. Sourcelindy.ai/pricing and lindy.ai/changelogread 2026-08-31 |
|
| APIs, SDKs & MCP Extensibility | Partial |
|
Inbound, the webhook trigger accepts a custom API call into a Lindy with a secret key sent as a bearer token in the Authorization header, exposes the received request body to downstream actions and supports a callback action for two-way communication with the calling system, and it now also takes custom headers and content types. Outbound, an HTTP Request skill calls arbitrary external APIs. Lindy publishes no SDK, client library or MCP server, and MCP appears only as Lindy consuming hosted servers. An OpenAPI specification is also listed. Sourcedocs.lindy.ai webhooks page and documentation index, lindy.ai/changelogread 2026-08-31 |
|
| Testing, Debugging & Optimization | Not documented |
|
The current Teammate product has no testing, preview, sandbox, evaluation, scoring or benchmarking capability, and none is among the eighteen capabilities included on every plan. The nearest affordances belong to the legacy builder, namely a task view for inspecting a completed run, configurable error-handling conditions after a webhook, and autosaved drafts with a discard-to-last-saved-version control. Routines and skills are authored in natural language and take effect directly, with no dry run. Sourcedocs.lindy.ai index, lindy.ai/pricing and lindy.ai/changelogread 2026-08-31 |
|
| Browser & Computer Use | Full |
|
Computer use comes on every plan. Lindy calls the capability Autopilot, saying APIs are limiting, and the agent gets its own cloud computer and can do anything the user could do on theirs. When a tool is not otherwise reachable, Lindy can use its computer or build its own integrations. Sourcelindy.ai/pricing, lindy.ai/changelog and lindy.ai homepage FAQread 2026-08-31 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Product updates
Lindy Apps lets a team ask Lindy, in Slack or chat, to build an internal tool such as a deal room, spend tracker or approval board. Each app saves its own data, gets its own link and can be rolled back to an earlier version. Apps read from and write back to connected tools, so moving a deal in the app updates it in Salesforce, with a separate permission for each tool.
Bears on: Agent capability
View sourceWith Watch and Learn, a user teaches Lindy a task by recording their screen for up to an hour, or by writing out the steps or pasting a checklist they already use. Lindy learns how the user does the task and can then run it on request or on a schedule as a routine, and the steps can be changed at any time.
Bears on: Workflow orchestration
View sourceAdded Hunter, ContactOut, Prospeo integrations, and an Outlook Calendar trigger.
Bears on: Integrations
View sourcePricing
From $30 per user per month, on the Team plan at $29.99 with 3,000 credits. Enterprise is custom.
Per seat, with each seat's monthly credits pooled into one shared balance that the whole workspace draws from.
Included quota
Team is $29.99 per user per month with 3,000 credits per user per month for standard usage. Pro is $99.99 per user per month with 15,000 credits per user per month, 5x the entry plan, and Max is $199.99 per user per month with 35,000 credits, about 12x. Enterprise is custom, with everything in Max plus HIPAA with a signed BAA, shared usage and bonus credits, dedicated support, audit logs, onboarding and enablement, and SSO and SCIM. Every plan includes the Slack native teammate in threads and mentions, scheduled routines, persistent workspace context, 40+ skills plus custom ones, shared meeting library and folders, meeting recording, notes, scheduling, prep and follow up, daily briefs and catch ups, inbox management with replies drafted in the user's voice, up to 5 connected inboxes, 24/7 iMessage, team files with version history, computer use, thousands of integrations, MCP support, model selection across all models, and approvals. Everyday asks use 2 to 250 credits, deep work 250 to 1,000 and big builds 1,000 to 2,500.
What is public
Lindy (lindy.ai) sells Lindy Teammate on four paid tiers, three of them self serve with list prices: Team at $30 per user per month with 3,000 credits, Pro at $100 with 15,000, Max at $200 with 35,000, and custom Enterprise adding SSO, SCIM, HIPAA with a signed BAA, shared usage with bonus credits, dedicated support and enablement. There is no lasting free tier. A Free plan gives $50 in credits that last 7 days with no card required, and a new teammate who joins via Slack gets a one time seven day free week before the seat is billed. All eighteen core capabilities, including computer use, model selection, MCP support and approvals, are included on every paid plan, and the tiers differ on credits alone.
Billing mechanics
One workspace subscription billed per seat, with every seat's credit allocation pooled so the whole team draws from a single balance. Anyone who uses Lindy takes a seat, whether they sign up directly, join the workspace, or @mention Lindy in Slack. New teammates joining through Slack get a one time seven day free week before their seat is billed. Direct signups are billed immediately, and a returning teammate does not get a second free week. Credits measure work rather than messages and scale with job size, from 2 to 250 for everyday asks up to 1,000 to 2,500 for complex builds. Credits refresh each cycle and do not roll over. Admins manage seats and per seat credit allocations in one place.
Cost watchouts
Tasks, premium actions and larger models all draw credits, and phone numbers and voice minutes add their own charges.
Variable cost rationale
Work is metered in credits. Each seat adds its monthly allocation (3,000 on Team, 15,000 on Pro, 35,000 on Max) to one pool the workspace shares, and a task draws more credits the bigger it is, with premium actions and larger models costing more. The bill grows with seats and with heavier work that needs top ups or a larger plan. Phone agents, where still sold, add $10 a month per number and voice minutes billed in credits. Nothing is billed past the pool without an admin choosing it. When credits run out, Lindy pauses credit using actions until the next reset instead of charging overage, and admins decide whether to top up at $10 per 1,000 credits or move seats to a larger plan. Monthly credits do not roll over, while purchased top ups do.
Additional watchouts
Phone pricing from the earlier product, $10 a month per number with standard U.S. calls at 20 credits a minute and higher rates in some countries and call types, is not on any current pricing surface, and nothing current says whether phone agents are still sold or at what cost. Support steps up by tier, from help center and community on lower tiers to dedicated onboarding and support at Enterprise.
Overage / add-ons
There is no overage bill. When the shared pool runs low, Lindy pauses credit using actions until credits reset. Admins can top up at $10 per 1,000 credits, and purchased top ups carry over.
Sales call required
No, self serve available
Free / trial
Free plan with $50 in credits for 7 days, no card required, and a 7 day free week for each new teammate joining through Slack
Lowest paid plan
Team at $29.99 per user per month, with 3,000 credits a month
Key ambiguities
Running out of credits pauses credit using actions until the next cycle rather than producing an overage bill, and admins can top up at $10 per 1,000 credits or move to a larger plan. Enterprise is custom with no public figure. The legacy phone agent pricing, $10 per phone number per month with voice minutes billed in credits, is not on any current pricing surface and may have gone with the classic builder. Model coverage is described as all models in the feature list and most major models in the usage section.
Cancellation / refund
Team cancels anytime with no long term contract. The workspace stays active through the paid cycle, with no mid cycle proration, and no refund terms are published.
Support SLA / resale
Help center and community support on Team. Enterprise adds dedicated support, onboarding, SSO and SCIM.
Related vendors
- Activepieces — Open source, MIT licensed automation platform where every one of 700…
- Agenta — Agenta is an open source workspace where teams build AI agents by…
- AgentX — No code platform to build, evaluate, and deploy multi agent…
- AI Library — No code platform for building and running AI agents, with a…
- Aigensei — Enterprise agentic workflow platform that runs business processes…
- Airia — Enterprise platform that unifies agent orchestration, security, and…
Alternatives to Lindy
The closest documented capability profiles to Lindy among agent builders tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Cassidy12.0 / 14Adds documented Testing, Debugging & OptimizationLindy vs Cassidy →
- Taskade10.0 / 14Fuller documented coverage on Workflow Orchestration and APIs, SDKs & MCP ExtensibilityLindy vs Taskade →
- Flozic10.5 / 14Adds documented Testing, Debugging & Optimization
- MindPal9.5 / 14Adds documented Testing, Debugging & Optimization
- Camunda14.0 / 14Adds documented Deployment & Data Residency and Testing, Debugging & Optimization
- Chipp12.0 / 14Adds documented Testing, Debugging & Optimization
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded