> 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/google-sheets.md).

# Google Sheets

Google Sheets is the center of your Salesa pipeline.\
It is where all your deals, stages, and updates are stored.\
Salesa connects directly to your Sheet and keeps it in sync with your Gmail so your sales data is always accurate and up to date.

### **How Salesa Uses Google Sheets**

Each row in your Sheet represents a deal, and each column holds information such as the deal name, owner, stage, and last contact date.\
When Salesa detects a new opportunity or an update from your emails, it edits the matching row automatically.\
Your Sheet becomes a live view of your sales activity without anyone needing to type updates manually.

Changes appear instantly for everyone in your organization who shares the same Sheet.\
That means every team member always sees the same pipeline, even if multiple people are handling different deals.

### **Recommended Sheet Structure**

Salesa can work with any Sheet, but the best results come when the columns follow a clear structure.\
Below is an example of a simple and effective layout:

<table><thead><tr><th width="190">Column</th><th width="545">Description</th></tr></thead><tbody><tr><td>Deal Name</td><td>The name or subject of the deal</td></tr><tr><td>Owner</td><td>The person responsible for the deal</td></tr><tr><td>Stage</td><td>The current status of the deal</td></tr><tr><td>Amount</td><td>The expected value of the deal</td></tr><tr><td>Last Contact</td><td>The date of the latest email exchange</td></tr><tr><td>Next Step</td><td>What needs to happen next</td></tr></tbody></table>

You can add extra columns like Region, Product, or Lead Source if needed.\
Salesa will recognize the most relevant ones automatically.

### **Syncing and Updates**

Salesa scans your Gmail for deal-related messages, detects intent, and updates your Sheet in real time.\
When a new conversation begins, it creates a new row.\
When an existing deal moves forward, it updates the corresponding row instead.

If you or your team make changes manually, Salesa will respect them and continue syncing new information without overwriting your edits.

### **Best Practices**

* Use one Sheet per team or product for clear tracking.
* Avoid deleting header rows since Salesa uses them for mapping.
* Keep stage names consistent with your organization’s setup.
* Review your Sheet structure occasionally to make sure columns are still relevant.

### **Connected Features**

The Google Sheets integration works together with:

* **Sales Stage:** Defines how deals move through your pipeline.
* **Pipeline Limit:** Manages Sheet size and auto-creates new pipelines when needed.
* **AI Insights:** Reads your Sheet data to suggest follow-ups and next actions.

***

> **In short:**\
> Google Sheets is your live sales database in Salesa.\
> It keeps everything organized, shared, and updated automatically, giving your team full visibility without extra work.


---

# 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/google-sheets.md?ask=<question>&goal=<endgoal>
```

`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.