Lindy AI: How to Connect Gmail and Google Calendar

Connecting mail and calendar is the first real decision you make with Lindy, and it is the one people rush. Everything downstream depends on it: the assistant cannot draft a reply it cannot read, and it cannot propose a time it cannot see. It is also the step where you hand over the most access, so it deserves ten minutes of attention rather than three clicks.

There are two places you will meet this connection. One is the guided setup that runs when you first bring Lindy into your workspace. The other is inside the workflow editor, where you add a Gmail or Google Calendar step and connect an account on the spot. They end at the same place, so the one you use depends on where you started.

What does Lindy need access to, and why?

Lindy asks for a Google or Microsoft account covering both mail and calendar, not two separate connections. Their quickstart states the reason plainly: with that account connected, Lindy can run your inbox, prepare and take notes on meetings, and handle scheduling. Those three jobs cut across mail and calendar at the same time, which is why they arrive as one authorization.

For Google Calendar specifically, the documentation describes a second choice after you authorize. You select which particular calendar Lindy should access. That is the setting to think about if you keep a personal calendar in the same Google account as your work one, because it is your chance to keep the two apart.

It is fair to say the ask is broad. One independent review of Lindy flagged exactly this, noting that the product needs wide permissions across email, calendar and other business data, and that some people are uneasy granting an assistant that much reach. That is not a criticism of the product so much as a description of the job: an assistant that reads nothing can help with nothing.

How do you connect Gmail and Calendar during setup?

The guided path starts in Slack. Lindy's quickstart describes an admin installing Lindy from Slack's Add to Slack screen, after which each teammate connects themselves. The first time someone DMs or mentions Lindy, it replies with a Connect Slack to Lindy button, and the account connections follow from there in three passes: email and calendar first, then a phone number, then the rest of your tools.

1. Have an admin install Lindy in Slack — Lindy's quickstart has an admin install it from Slack's Add to Slack screen. This is a workspace-level action, so if you are not an admin, this is the part you ask for.
2. Connect your own Slack account — The first time you DM or mention Lindy, it replies with a Connect Slack to Lindy button. Each teammate does this for themselves, so one person connecting does not connect the team.
3. Connect email and calendar — Connect your Google or Microsoft account. Per the quickstart, this is what lets Lindy run your inbox, prep and take notes on meetings, and handle scheduling.
4. Choose which calendar it may see — The Google Calendar documentation has you authorize the account, then select which specific calendar Lindy should access. Decide here whether your personal calendar is in scope.
5. Add a phone number if you want it — The quickstart offers adding a phone number or connecting Apple Messages so you can text Lindy. This is optional and separate from the mail and calendar connection.
6. Connect the rest of your stack later — The third pass covers other tools such as Notion, HubSpot and Linear. There is no need to do this on day one, and connecting less at first makes the early behaviour easier to read.

How do you add Gmail or Calendar inside a workflow?

Inside the flow editor you add the integration as a step, then connect the account from that step. The documentation for both Gmail and Google Calendar describes the same move: click the plus sign at the bottom of the canvas or right click the canvas, choose Add Trigger or Add Action, then pick the integration. Click Add Account, complete the authorization, and the step is live.

The integrations page is the other entry point, and it works differently in one useful way. Their documentation describes searching for the tool and connecting it with OAuth or an API key, after which every action for that tool becomes available at once. There is no step where you tick which capabilities to enable, so a connected tool is a fully connected tool.

What can Lindy do with Gmail once connected?

Once Gmail is connected, Lindy gets both triggers that start work and actions that perform it. Their documentation lists five triggers: Email Received, Email Sent, New Attachment Received, New Email Matching Search, and New Labeled Email. Email Received is called out as the most popular, with a note to use filters to target specific messages.

• Writing: Send Email, Send Reply, Draft Email and Edit Draft.
• Organising: Add and Remove Labels, Delete Label, Archive and Unarchive.
• Status: Mark as Read, Unread, Important or Unimportant, and Move to or from Trash.
• Finding: Find Email, Search Emails, Get Email, and Find Email Address By Person.

Their own best practice guidance for this integration is worth following on day one. Use filters so the agent is not woken by everything, test those filters before you scale up, and prefer draft actions over send actions for anything sensitive. A draft you approve costs you five seconds. A sent message you did not expect costs a lot more.

What can Lindy do with Google Calendar?

The calendar side splits the same way. Their documentation lists triggers for Calendar Event Created, Calendar Event Updated, Calendar Event Started, Calendar Event Ended, and New Event Matching A Search. The Started trigger is configurable to fire before or after the event begins, which is what makes pre-meeting prep possible.

On the action side the documentation lists Create Event, Add Quick Event, Update Event, Check Availability, Find Available Times, Get Event Details and View Events. Add Quick Event parses natural language, so a phrase like a meeting tomorrow at 2pm becomes a real event. Their own tip is to pair Find Available Times with Check Availability when you want scheduling that reasons across more than one calendar.

Who else can use the connection, and can you stop it writing?

Every connection has a scope, and it matters more than most people expect. Lindy's integrations documentation describes two: Personal, where only the person who created it can use or modify it, and Team, where everyone in the workspace can use it but only owners and admins can change it. Pick Personal for your own inbox unless you genuinely want colleagues acting through your account.

Write behaviour has its own control, which their documentation calls guardrails. Three settings are described: always allow, so it writes without asking, require approval, so it asks before writing, and do not offer, so it never writes at all. Reads are not guarded, which is the sentence to sit with before you connect anything you would not want summarised out loud.

None of that is a reason to avoid connecting. It is a reason to connect deliberately: one inbox, one calendar, read-heavy actions first, then widen once you have watched it for a week. Whatever tool you use, that sequence turns a scary permission screen into a manageable one.

It is also close to how we approached the same problem at Sistava. An AI Employee arrives with its tools already wired, so the question you answer is which job it owns rather than which scopes to grant across which steps. If you enjoy holding those controls yourself, Lindy gives you real ones, and the guardrail settings are genuinely well thought out. If you would rather never see them, that tells you something about which shape of product suits you.

Sources

• Lindy documentation, Quickstart
• Lindy documentation, Integrations
• Lindy documentation, Gmail integration
• Lindy documentation, Google Calendar integration
• Lindy documentation, Pricing, read 17 August 2026
• FlowHunt, How to Use Lindy AI, a beginner's guide
• SalesRobot, Lindy AI review after three months