> For the complete documentation index, see [llms.txt](https://docs.fullwhere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullwhere.com/integrations/integrations-en/emails/gmail.md).

# Gmail

To connect your business Gmail emails linked to your Google Workspace, you need to:&#x20;

* Connect your email address to one of your brands or locations
* Set up automatic email forwarding
* Authenticate your domain with Fullwhere

## Connect your email address

To connect your email address to one of your Fullwhere brands, please refer to our [dedicated article](/documentation/documentation-en/get-started/brands.md#connecter-vos-adresses-email-a-fullwhere-recommande).

To connect your email address to one of your Fullwhere locations, please refer to our [dedicated article](/documentation/documentation-en/get-started/locations.md#connecter-vos-adresses-email-a-fullwhere-recommande).

## Set up automatic forwarding

This approach is recommended for forwarding from Google, as it imposes no rate limits and does not require creating a dedicated inbox. You will need administrator access to complete this setup.

[Google documentation](https://support.google.com/a/answer/10486484?product_name=UnuFlow\&hl=en\&visit_id=638690871651590812-3129432273\&rd=1\&src=supportwidget0\&hl=en)

### Step-by-step instructions:

1. Log in to your Google Workspace admin console at <https://admin.google.com/> using your administrator credentials.
2. Go to Apps > Google Workspace > Gmail.
3. Find the "Default Routing" section in the Gmail settings and select Configure to create a new routing rule.
4. When adding the setting:
   * Enter your support email address (e.g.: <support@mycompany.com>) in the "Envelope recipient" field.
   * Under the "Envelope recipient" option, check "Modify the envelope recipient" and enter your Fullwhere forwarding address (which you copied from your Fullwhere settings) in the "Replace recipient" field.
5. Save your changes in the Google Workspace admin console.
6. Now, edit the rule you just created and make sure the setting under the "Options" section is set to: "Apply this action to recognized and unrecognized addresses."

{% hint style="info" %}
Note: Changes may take up to 24 hours to propagate, although they sometimes take effect faster.<br>

Warning: Make sure the "Disable forwarding" option is not selected in your Gmail settings, as this could block automatic forwarding to Fullwhere.
{% endhint %}

## Authenticate your domain

To authenticate your domain with Fullwhere, please refer to our [dedicated article](/documentation/documentation-en/integrations/authenticate-your-domain-for-sending-emails.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fullwhere.com/integrations/integrations-en/emails/gmail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
