Right now, you’re probably doing this:

Copy email → paste into Claude → ask for a reply → copy answer → paste back into Gmail. but i’m not

Most people use Claude to ask questions. A few use it to run their entire work context.

Emails, Slack, Notion, meetings — instead of copying anything in, it’s already connected. That shift changes everything:

You don’t read your inbox → you ask what matters. You don’t scroll Slack → you ask what needs action. You don’t search docs → you ask what already exists.

Claude stops being a tool you prompt… and becomes the layer where your work actually happens. That’s what Connectors unlock.

I use claude with almost my every gmail account .

Because my Claude is connected to everything else: my Gmail (email), my Slack (team channels), my Granola (meeting notes). with Claude Connectors.

Claude has over 200 connectors. But you’re probably using none of them, and this newsletter is here to help you get started.

Two things before we start:

1. Save this guide for later. Book a 10 min meeting this week to act on it.
2. Share it with your team who wants to get more from Claude.

I — How to connect your app to Claude.

A Connector is a 1-click bridge between Claude and an app you already pay for.Here’s how to connect your app to Claude:

1. Open Claude. Go to the plus “+” inside the chatbox.
2. Find “Connectors” and click on “Add connector”. Add one of them.
3. Now open a new chat. Click “+” in the chat bar > Connectors > make sure your app is toggled on for that conversation. It should be automatic.

Step 1: Find the + inside the chatbox.

Step 2: Go to Connector → Add connector.

Step 3: Search for a connector (like Gmail, Gamma, Google Drive, Granola…)

Step 4 — You can check if it is connected

What changes when you turn one on?

Let’s see some examples:

• Gmail on: ask “what are my top 3 recent mail” and Claude answers from your actual Gmail. 0 copy-pastes.

The response claude gave me

What the actually is.

Both are same .You can try it too . Follow all the steps above .

II — My 5 favorite Claude connectors

Now here are my 5 favorite Claude Connectors I (actually) use every week.

1. Notion. For my knowledge base.

I use Notion for our content calendars and knowledge base. Like, for example, my social media posts, all of our standard procedures on how we do things…

Prompt I use with Notion:

Go to Notion, NEW Post Calendar. Extract the content from May 21, 2026 (Design brief, Caption). Create 2 new ones using the same ideas and techniques.

Worth noticing, I am a solo, but most big ones use Microsoft or Atlassian with Jira, Confluence… Needless to say, Claude can connect to all of them. But I haven’t tried. So go & do it and let me know if it’s good :).

2. Slack. Because I don’t use Microsoft Teams.

I use Slack, not Teams, to talk with my teams.

A typical prompt I use :

Read #{teammate name} #team-lead, #internal-content-sync, #circle-studio from the last 48 hours. Surface the 3 things I need to react to. Skip jokes, GIFs, standup updates.

3. Gamma. To make on-brand slides in seconds.

I use Gamma for all of my slides. It’s the fastest/cheapest/easiest. Hard to beat.

A typical Gamma prompt:

Go to Gamma. Create a [NUMBER]-slide deck on [TOPIC] for [AUDIENCE].
Goal: [What you want them to do or understand].
Cover: [List 5-8 key points or sections].
Tone: [confident / data-driven / concise].
Make it visual, clean, and one idea per slide.

4. Gmail. The most obvious win.

I save the most known for last.

What it replaces: searching your inbox, finding the wrong email, searching again.It also works for Outlook emails, obviously. A prompt you’d like to try:

Read my Gmail from this week.
Group every email into 3 buckets:
1. Needs my reply today.
2. Can wait until Friday.
3. Newsletter / FYI / can ignore.
Output: 3 lists. No commentary.

Non-obvious tip: ask Claude to draft the replies as drafts in Gmail, not in the chat. Just add the prompt: “Save the 5 replies as drafts in my Gmail.”

If you only turn on 2 connectors today, pick , Gmail/Outlook, and Slack/Teams (depending on what you use internally). This duo compounds..

III. When NOT to use a Connector.

3 rules.

1. Don’t leave them all on by default.

Connectors burn tokens before you type. Every Connector loaded is context Claude has to scan. Turn them on per chat. Off per chat. Treat the toggle bar like a kitchen tap.

2. Don’t use Connectors for creative work.

When you’re drafting a LinkedIn post or writing a script, you want a clean room.

Slack noise, Gmail noise, Notion noise pollutes the output. My default writing chat: every Connector off. Always.

3. Don’t grant write access until you trust the read flow.

Read-only first. Watch how Claude uses it for a week.

Then grant write. Most data accidents happen on day one when someone enables a Connector with full write access and asks Claude to “clean up my Drive.”

Where to start.

You won’t turn on all 9 tonight. Don’t try.

Pick 2.

My favorite stack of connectors is:

1. My email (mine is Gmail).
2. My team channel (mine is Slack).

They give the needed context to Claude so I can do better work.

It’s obvious, but I’ll say it again.

I don’t care about Claude, or any other AI model. I don’t pick sides. I’m not paid to make this newsletter.

I’m sharing, ONCE a week, how my work is changing (very fast) with AI.

As I’m trying to keep up, I want you to keep up.

so you stay ahead. Well, I will continue to do so for any future upgrades.

Because I want to be the greatest filter to the AI noise. And 2000+ people trust me to be their filter. ALL because of my LinkedIn. But most readers subscribed because someone they trusted sent them one of my articles.

If this helped you, share it with someone who’s still doing things the hard way. It takes less than a second, but it might genuinely change how they work.

And if someone forwarded this to you — thank them, you’re now part of the loop.

You can subscribe for free here to get the next one.

Next up: I’ll break down how to build your own Claude Connector (for developers) — and how people are extending Claude beyond the default integrations.