> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I connect email and calendar?

> Connect Gmail or Outlook to Klipy with OAuth — no password needed. Calendars are included automatically. Step-by-step email and calendar setup.

Connecting email is the step that unlocks Klipy. Once Gmail or Outlook is linked, Klipy builds your contact graph, reconstructs conversation history, and starts generating follow-up drafts and to-dos. Calendar access comes automatically with the same OAuth—no separate step.

Klipy uses **OAuth** throughout. You never share your email password with Klipy.

## Gmail

**1. Open Email settings**

In the Klipy app, go to **Settings → Channels → Email**.

Screenshot coming soon

Screenshot coming soon: Settings → Channels → Email panel (Gmail)

**2. Connect Gmail**

Click **Connect** (or **Connect Gmail**). Choose the Google Workspace or personal account you use for customer conversations.

Complete Google's consent screen. Klipy requests:

* **Read** access to your mail, so it can process conversation intelligence.
* **Send** access—used only when you explicitly **approve a draft**. Nothing sends automatically.

Screenshot coming soon

Screenshot coming soon: Google OAuth consent screen

**3. Confirm and let import run**

After authorization, Gmail stays linked until you disconnect. Historical import begins in the background—see [Importing data](https://klipy.ai/docs/guides/importing-data.md) for timeline and scope.

## Outlook / Microsoft 365

**1. Open Email settings**

Go to **Settings → Channels → Email**.

**2. Connect Outlook**

Click **Connect** (or **Connect Outlook**). Sign in with your Microsoft work or personal account and approve the permissions shown.

Screenshot coming soon

Screenshot coming soon: Settings → Channels → Email panel, Outlook variant

**3. Confirm and let import run**

Once connected, Outlook mail stays linked until you disconnect. Recent history is imported automatically ([Importing data](https://klipy.ai/docs/guides/importing-data.md)).

> [!WARNING]
>
> **Organizational Microsoft accounts** often require an administrator to allow third-party OAuth apps. If sign-in fails or your tenant blocks the app, ask **IT** to approve Klipy before retrying.

## Calendar

Calendar access is bundled with your email connection—there is no separate calendar-only flow.

* **Gmail** → includes **Google Calendar** for the same account.
* **Outlook** → includes **Outlook Calendar** for the same Microsoft account.

Once your email is connected, open **Calendar** in Klipy and confirm upcoming events appear. Events with Google Meet, Zoom, or Microsoft Teams links will be picked up by the [notetaker](https://klipy.ai/docs/guides/connecting-notetaker.md) automatically.

Screenshot coming soon

Screenshot coming soon: Calendar view with synced upcoming events

> [!NOTE]
>
> If you want calendar-based meeting capture without email, contact support—the standard path requires an email connection first.

## What happens after you connect

* Your contact graph builds from recent threads (usually visible within a few minutes).
* Klipy filters incoming email for sales signals and suppresses noise—read [What Klipy captures](https://klipy.ai/docs/guides/capture.md) for full details on what is and isn't stored.
* Follow-up drafts, to-dos, and meeting prep start generating as activity arrives.

## Frequently asked questions

> [accordion] Does Klipy read all my email?
>
> No. Every incoming message passes an intelligence filter. Marketing mail, billing receipts, internal chatter, and spam are discarded. Only messages with real sales signal—engaged replies, meeting requests, objections, new stakeholders—are processed. Raw email bodies are not stored; Klipy stores structured intelligence extracted from them.

> [accordion] What data does Klipy store from my email?
>
> Klipy stores a structured summary of each qualifying message—not the full text. This includes a brief summary, conversation type, sentiment, main intent, open questions, and buying signals. See [What Klipy captures](https://klipy.ai/docs/guides/capture.md) for the complete list.

> [accordion] Does Klipy send email on my behalf?
>
> Only when you approve it. Klipy drafts follow-up suggestions, but nothing leaves your account until you review and explicitly approve the draft inside the app.

> [accordion] Is Klipy similar to Fyxer for email AI?
>
> Both tools bring AI to your inbox. Klipy's focus is CRM intelligence: it extracts relationship context from email to build a deal pipeline, generate follow-up drafts, and track conversations—not inbox management or triage. If you use email primarily for sales, Klipy surfaces what matters for each deal rather than reorganizing your inbox.

> [accordion] Do I need admin approval to connect Gmail?
>
> Personal Google accounts connect immediately. Google Workspace accounts may show a screen asking for admin approval if your org restricts third-party app access. Check with IT before connecting if you're on a managed Workspace account.

> [accordion] Can I connect multiple email accounts?
>
> Klipy supports one primary email connection per user. If you need multi-inbox support, contact support.

> [accordion] What if I disconnect email?
>
> Klipy stops processing new mail. Existing intelligence (contacts, summaries, drafts) remains in your workspace. Reconnecting re-enables live capture but does not re-import history already processed.

> [accordion] Does Klipy work with Google Workspace and personal Gmail?
>
> Yes. Both personal (`@gmail.com`) and Workspace accounts work with the same Gmail OAuth flow.

> [accordion] How is Klipy different from a traditional CRM like Salesforce or HubSpot for email?
>
> Traditional CRMs require you to log emails manually or use BCC plugins. Klipy reads and processes email automatically, extracting deal intelligence without data entry. It's designed for the owner-seller who can't afford to spend time on CRM admin.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.