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

# Gmail

> Give an agent access to your connected Gmail account so it can send, read, and search email

Gmail gives your agent access to your connected mailbox. The agent can send messages, read and search email, manage drafts, and fetch attachments while it responds to chat messages or completes tasks.

## What it does

When Gmail is enabled on an agent, the agent can automatically perform email actions as part of its reasoning process. You ask a question or give it a task — the agent decides when and how to use your Gmail account on your behalf.

## Prerequisites

You must have an active Gmail connection in your workspace before enabling this tool. If no active connection exists, the toggle is disabled.

1. Go to **Integrations** for your workspace.
2. Find **Gmail** in the integrations grid.
3. Click **Connect** and complete the OAuth flow.
4. Return to your agent and enable the tool.

## Adding the tool to an agent

1. Open an agent in the editor.
2. Click the button with the tooltip **Add MCP Tool or Sub Agent**.
3. In **MCP Tools**, click **Gmail**. The Gmail node appears on the canvas.
4. Click the node to open the **Settings** panel on the right.
5. In the **Authentication** field, select the connected Gmail account the agent should use.
6. If no active connection is found, the settings panel shows a warning with a link to **Integrations** to connect first.

## Use cases

* Send a summary email when a workflow completes.
* Search for unread messages from a specific sender and summarize them.
* Draft a reply to a customer inquiry based on earlier workflow output.
* List recent threads in a label and extract action items.

## Notes

* The agent uses your connected Gmail account to perform actions. Make sure the OAuth connection has access to the mailbox your workflows need.
* This tool counts as 1 credit per action the agent performs.
* OAuth may show third-party authorization branding during the connect flow.

See also: [Integrations](../../workspace/integrations), [Creating and Configuring](../creating-and-configuring)
