Skip to main content
The Integrations page: an Add button, a Browse all integrations banner, and enabled tools like Browserbase, Datadog, DeepWiki, and GitHub showing their connected accounts
Lindy connects to 1,000+ tools: Gmail, Slack, Notion, HubSpot, Google Drive, GitHub, and the rest of your stack. Open Integrations to see what’s connected, or click Browse all integrations for the full catalog.

​
When a tool isn’t in the list

Lindy supports MCP, so any MCP server your team runs plugs straight in. If a tool has no integration and no MCP server, Lindy still isn’t stuck. It can drive the browser the way a person would, or write its own integration against the tool’s API. Two more things are worth understanding: whether a connection is yours or the team’s, and what Lindy is allowed to do with it.

​
Personal and team connections

A personal connection is private to you. Your Lindy uses it for your own work, your DMs, and the web app. An owner or admin can share one of their personal connections with the whole workspace. From then on, everyone’s Lindy reads that tool as that account and acts with its permissions. Members can see team connections but can’t change them.

​
Guardrails

Guardrails decide what Lindy can do without asking. This is the setting that matters most for Teammate. Each integration has one: Two things to know:
  • Reads are never guarded. Checking your calendar or searching your email always just works. Guardrails only cover writes.
  • Guardrails apply in shared Slack threads only. Your web app chat, Slack DMs with Lindy, and iMessage and SMS aren’t guarded.
A guardrail covers every account under an integration. You can’t yet set one rule for your work Gmail and a different one for your personal Gmail.

​
Approving a write in Slack

When Lindy needs approval, it posts Approve and Deny buttons in the thread. The person who asked can approve their own request, and so can any workspace owner or admin. Anyone else gets a private note to ask one of them. Approve allows that one action and changes nothing else. Always allow changes the rule going forward: workspace-wide if an owner or admin clicks it, or just for that person if a member does.

​
Connecting and managing

Search for the tool you want and connect it with OAuth or an API key. Every action for that tool turns on at once, so there’s no action-picking step. For tools that support more than one login, like Gmail, you can add further accounts under the same integration. Each connection shows whether it’s healthy, needs reconnecting (usually an expired token), or isn’t set up yet. From a connection you can rename it, share it with the workspace (owners and admins only), or disconnect it. Removing the last account of an integration removes the integration from your list.