# Connecting your tools to GPTree

Connect Gmail, Slack, GitHub, Notion, and 1,000+ more apps so chat can act on them. Write actions always ask for your approval before they run.

"Connect tools" in the left menu opens an integrations gallery: search Gmail, Slack, GitHub, Notion, and 1,000+ more, then connect the ones you actually use. (Settings, then Service accounts, lists your integrations too and opens the same gallery.) Once an app is connected, its tools show up in chat. You finish a draft, say "send that as an email", and it happens as an action instead of a copy-paste errand.

The mental model: connecting an app gives your conversations hands. GPTree could already think alongside you; connectors let it touch the systems where the work actually lives, so the output of a conversation doesn't have to die inside the conversation.

It earns the setup time the moment your conversations regularly produce things that need to leave GPTree. You spend Tuesday morning diagnosing a bug across a 40-message thread, and the conclusion needs to become an issue your team can see. You write the client summary and it needs to be in an inbox by noon. If you keep alt-tabbing to retype what the model just wrote, that's the sign.

## Write actions ask first

Anything that changes something in a connected app comes back to you before it runs. Sending an email, creating an issue: write actions ask for your approval, every time. We built it that way on purpose, because "I connected Slack" should never quietly turn into "the AI can post as me without asking".

So the loop in practice goes: the chat produces the thing, the action comes up for approval, you approve, it runs. That also keeps the blast radius small while you're experimenting, since no write action fires without your click.

The approval step is the honest limitation too. This is not hands-off automation. If your goal is actions running with nobody watching, the gate is in your way, and it's in your way by design.

## The curated nine and the long tail

Nine connectors are curated: Gmail, Slack, GitHub, Notion, Google Calendar, Linear, Asana, Jira, and Dayzie. Past those, the gallery covers more than a thousand apps, and search is how you find yours. Connecting works the same either way: authorize the app once, and its tools start showing up in your conversations.

Our advice is to connect the two or three you touch every day and stop there. The gallery is not a checklist.

## Connections are yours, not the workspace's

Connections are per user. You authorize your Gmail, your teammate authorizes theirs. On a team this surprises someone about once a week in support email: connecting an app does not light it up for everyone in the workspace. Each person connects their own accounts, which is the arrangement you want anyway, because nobody's actions should run through somebody else's login.

One neighbor to keep separate in your head: the AI Providers page. That page is for model API keys (your own OpenAI or Anthropic key, with model usage billed through your provider). It has nothing to do with the integrations gallery. Keys make more models available in the picker; connectors make apps reachable from chat. People conflate the two constantly. They're different rooms.
