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

# Integrations overview

> Connect the tools Henry can use. Thousands of apps, one click each.

Henry does real work by using your tools: reading your inbox, updating your CRM, filing tickets, building spreadsheets. Each tool you connect is an **integration**. Open **Integrations** in the web app to see what is connected and what is available.

## Connect a tool

<Steps>
  <Step title="Find it">
    Search for the app. Henry connects to more than 3,200 apps, including Gmail, Google Calendar, Google Drive, Notion, Linear, Jira, HubSpot, Salesforce, GitHub, Airtable, Asana, Slack, and Stripe. The **Popular** section lists common picks.
  </Step>

  <Step title="Sign in">
    Click **Connect** and sign in to the tool. Henry uses the tool's own sign-in and asks only for the access it needs.
  </Step>

  <Step title="Choose who can use it">
    Pick **Team-only** (anyone in the workspace can use this connection) or **Private (Invite only)** (only you and people you invite). See [Sharing and access](/user-guide/integrations/sharing-and-access).
  </Step>
</Steps>

Henry can start using the tool in the same conversation. Reads work immediately; writes ask for confirmation until you say otherwise.

## Team connections and private connections

The same app can be connected more than once, each connection with its own rules.

* A **team** connection is one shared login the whole workspace uses, such as the company HubSpot or the shared support inbox.
* A **private** connection is your own account, such as your Gmail or your calendar. Only you and the people you invite can use it, and everyone you invite acts through your login.

When Henry tells you an integration is **private to someone else**, the answer is one of two things: ask that person to invite you, or connect your own account. Henry does not use a colleague's private connection on your behalf.

## The account page

Click any connected account to open it. Three tabs:

* **Tools** lists every tool the connection provides, labeled **Read** or **Write**, with a setting for each: **Run automatically** or **Ask for confirmation**. See [Tool permissions](/user-guide/integrations/tool-permissions).
* **Access** controls who can use the connection and at what level.
* **Settings** renames the account, pauses it, reconnects it, or disconnects it. See [Managing accounts](/user-guide/integrations/managing-accounts).

Each account also has a **notes** field. Anything you write there, such as "the Deals pipeline is the only one we use", is context Henry keeps in mind whenever it uses that account.

## Needs attention

When a connection stops working, because a login expired or authorization was revoked, it moves to **Needs attention** at the top of the page with a **Reconnect** button. Henry checks hourly and can notify you by email or Slack DM. Turn those alerts on in **Settings → Notifications**.

## Who can connect integrations

By default anyone in the workspace can connect a tool and edit connections they set up. Admins can tighten this in **Settings → Permissions**. See [Permissions](/user-guide/admin/permissions).

## Custom MCP servers

If your team runs its own tools behind an MCP server, add it with **Add custom MCP** and its tools become available to Henry. See the [Developer Guide](/developer-guide/custom-mcp-servers).

## How it works under the hood

Henry connects to most apps through Pipedream, with a small number of first-party connectors. Your sign-in tokens for integrations are held by the connection provider, not stored by Henry. Read more in [Security architecture](/developer-guide/security-architecture).