# Page Not Found

The URL `setup-and-configure/email-ticketing-setup/how-to-configure-the-email-integration-for-gmail-and-google-workspaces` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Gmail & Google Workspaces](https://support.suptask.com/integrations-automations-and-workflows/email-ticketing-setup/how-to-configure-the-email-integration-for-gmail-and-google-workspaces.md)
- [Multiple Workspaces & Slack Community](https://support.suptask.com/setup-and-configure/multiple-slack-workspaces/how-to-set-up-suptask-with-multiple-workspaces.md)
- [Using the Organization field](https://support.suptask.com/setup-and-configure/forms-and-fields/how-to-use-the-organization-field.md)
- [Migrate to the new generation](https://support.suptask.com/setup-and-configure/inboxes/how-to-migrate-to-the-new-inboxes.md)
- [Fields](https://support.suptask.com/setup-and-configure/forms-and-fields/how-to-create-custom-fields.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://support.suptask.com/integrations-automations-and-workflows/email-ticketing-setup/how-to-configure-the-email-integration-for-gmail-and-google-workspaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://support.suptask.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://support.suptask.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/integrations-automations-and-workflows/email-ticketing-setup/how-to-configure-the-email-integration-for-gmail-and-google-workspaces.md`).

You may also use `Accept: text/markdown` header for content negotiation.