Kimi Adds Gmail, Google Drive and Calendar: What the Plugins Can Do

Kimi announced support for Gmail, Google Drive and Google Calendar on October 29. The integrations let users summarise email threads, find files and plan their day inside the assistant. They make Kimi more useful for work already stored in Google's apps, without requiring a new model release.

What Kimi's Google plugins do

The official announcement describes three capabilities: summarising Gmail threads, finding files in Google Drive and using Google Calendar to plan a day. It directs users to the Kimi Plugins page and says access uses OAuth permissions controlled by the user.

Those are the confirmed functions. The announcement does not establish that Kimi can autonomously send emails, invite attendees or edit every type of Drive document. Planning a day and creating calendar events are different capabilities; readers should not assume the latter from the former.

This is also separate from using a Google account to sign in to Kimi. Authentication identifies a user. Connecting a service gives the application access to information or actions covered by the permissions the user grants.

Why bringing work context into the assistant matters

A general chatbot can help draft a meeting brief, but someone normally has to find the relevant conversation and document first. Connectors can reduce that preparation work. The potential value is less about a better answer to a standalone question and more about reaching the right source material quickly.

Consider preparing for a project review. An email thread might contain a revised requirement, while the original plan lives in Drive and the meeting sits on the calendar. Having those services available in one assistant creates a useful starting point for preparation. It does not guarantee that the assistant will select the latest document or recognise which email supersedes an earlier decision.

For that reason, a sensible first task is narrow: ask for a summary of one identifiable conversation or help finding a known file. Compare the result with the original before extending the workflow to broader questions. A plausible summary is not the same as a complete one.

Check permissions before connecting an account

OAuth is an authorisation mechanism, not a general guarantee about everything an application does with data. Review the access requested on the consent screen and the provider's privacy terms before connecting a work account. For an organisation, that review should also fit its rules for third-party services.

Google's linked-app guidance explains how to review which applications have access to an account and remove that access. Google also recommends checking the developer's privacy policy and security disclosures before sharing account data.

The useful distinction is between granting access and trusting an output. Permission determines what an application may reach. It does not verify whether a summary preserves a deadline, a condition or the person responsible for a decision.

What Kimi has not specified

The launch post does not provide a connector-specific price, an eligible-plan table, regional restrictions or usage limits. It also does not enumerate the precise OAuth scopes. Check the current plugin interface and consent screen rather than treating those omissions as evidence of unrestricted or free access.

For existing Kimi users, the integrations could remove some of the copying and searching around everyday tasks. The more important test comes after connection: whether the assistant can reliably locate the right evidence and make it easy to check, especially when several versions of the answer exist across a person's working day.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help technical teams turn product updates and complex workflows into stories developers and founders can understand and share.

Book a 30-minute call.