I used to live inside twelve open browser tabs. Email here, meeting notes there, Slack buried somewhere behind them all. Copy from one, paste into another, then re-explain the whole thing to my AI before it understood a single word. Sound familiar?
Then I came across a sharp little walkthrough from a LinkedIn creator who shares practical AI workflows, and it flipped how I think about using Claude day to day. The post lays out how to connect your actual apps to Claude so it reads them live, no copy-pasting required. I was genuinely impressed by how simple the original poster made it look, so I broke the whole thing down for you here.
What the author is actually showing
The big idea from this AI professional is that Claude does not have to work blind. Instead of you feeding it scraps of context, you let it connect straight into the tools you already use. Think Gmail, Slack, Notion, Granola. Once they are linked, Claude reads them in real time. As the creator put it: Claude now reads your apps. Live. 0 copy-pastes.
The 5-step setup the creator shared
Here is the exact process the original poster walks through. It takes about 60 seconds, and each step has a clear reason behind it.
- Open Claude. This is your starting point, the home base for everything that follows.
- Click the “+” inside the chatbox, not Settings. This is the part most people miss, so the author calls it out directly. The connector menu lives in the chatbox, not buried in your account settings.
- Find “Connectors” and click “Add connector.” This is the gateway that lets Claude talk to outside apps.
- Search for your app, like Gmail, Granola, Slack, or Notion. Pick the tool you actually want Claude to read from.
- Authorize it, and you are done. Claude now has a live line into that app.
That is the whole mechanic. Quick, but the real value comes from how you use it next.
Why you should not turn on all 200
This is where the post gets clever. There are around 200 connectors available, and the instinct is to flip them all on. The expert warns against exactly that. The smarter move is to pick three that compound, meaning three tools that feed each other context.
Here is the stack the creator recommends:
- Your notetaker (Granola) so Claude can read your meetings and remember what was actually said.
- Your email (Gmail) so Claude can draft your replies with full awareness of the thread.
- Your team chat (Slack) so Claude can pull the relevant threads instead of you hunting for them.
The secret is the context, not the prompting. When all three connectors are on in the same chat, Claude pulls your meetings, inbox, and team channels at once. No tabs. No searching. No re-explaining yourself.
I think this is the part worth sitting with. We spend so much energy trying to write the perfect prompt, when the real unlock is just giving the AI the right information to begin with. The mind behind this post nailed that point.
The one warning to remember
The contributor flags an important catch, and I am glad they did. Do not leave your connectors on by default. They quietly burn tokens before you even type a word, because Claude is pulling context in the background. So switch them on when you need them for a focused task, then switch them off when you are done.
Why this matters for your workflow
Let me connect this to something bigger. Most people treat AI like a vending machine. You type a request, you get an answer, the machine forgets you the moment you walk away. Connectors change that relationship entirely. Suddenly Claude works more like a teammate who already sat in your meeting, already skimmed your inbox, and already read the Slack thread before you asked.
A few practical ways you could put this to work:
- Meeting follow-ups: after a call, ask Claude to turn your Granola notes into a clean recap and draft the follow-up email in Gmail, all in one go.
- Inbox triage: let Claude scan recent threads and draft replies that already match the tone of the conversation.
- Team sync: have Claude pull the key Slack threads from the week and summarize what actually needs your attention.
Each of those normally means jumping between three or four apps. With a compound connector stack, it becomes a single chat.
My quick take
What I appreciate most about this savvy professional’s approach is the restraint. Anyone can tell you to connect everything. It takes real insight to say connect three things that talk to each other, and turn them off when you are done. That is the difference between a flashy demo and a workflow you will actually keep using.
If you have been drowning in open tabs like I was, this is worth trying today. Open Claude, hit that “+” in the chatbox, and link your first connector. Then go check out the full LinkedIn post from the original creator for the complete walkthrough and their exact stack. Save it so you stop living in twelve open tabs.