> For the complete documentation index, see [llms.txt](https://salesa.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salesa.gitbook.io/docs/guide/gmail.md). # Gmail Gmail is the core source of information for Salesa.\ It is where the system reads deal-related messages and detects intent automatically.\ By connecting Gmail, your sales pipeline can stay accurate without manual updates or data entry. ### **Why Connect Gmail** Salesa reads only the messages that are related to sales activity such as customer replies, meeting requests, or pricing discussions.\ This information helps identify when a deal moves forward and keeps your Google Sheet updated in real time. Each team member connects their own Gmail account so the system can track their individual conversations securely.\ No one else in the team can see personal emails or messages outside of deal activity. ### **What Salesa Reads** Salesa does not store or display the full email content.\ It only processes the metadata and message snippets needed to understand what is happening in a deal, such as: * When the customer last replied * Whether the message shows interest or intent to buy * When a new opportunity appears All other messages are ignored automatically. ### **How Gmail and Sheets Work Together** Once Gmail is connected, Salesa links email activity to rows inside your Google Sheet.\ If a new conversation starts, a new deal row is created.\ If an existing deal gets an update, the related row changes automatically. This connection keeps your pipeline in sync with your inbox so your Sheet always reflects real conversations. ### **Permissions and Security** Gmail access is handled through Google OAuth 2.0.\ Salesa never stores passwords and can be disconnected anytime from the integrations page or directly from your Google Account settings.\ Access is limited to reading deal-related emails only and does not include sending or deleting any messages. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://salesa.gitbook.io/docs/guide/gmail.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.