> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/addons/google-sheets-addon/why-your-data-flows-sometimes-dont-appear-in-the-add-on.md).
# Why your data flows sometimes don't appear in the add-on
Learn which data flows appear in the Coupler.io Google Sheets add-on sidebar and how the display is determined by your connected spreadsheet and workspace.
When you open your Coupler.io add-on, you'll only see data flows that use the current spreadsheet as their destination.
If your data source and destination are different spreadsheets that belongs to the same google account, make sure you open the destination spreadsheet before opening the Coupler.io add-on.
When you add a new data flow from the add-on, Coupler.io automatically sets the destination setting with the current spreadsheet:
If several users add data flows in their personal Coupler.io accounts (not a shared one) with the same destination spreadsheet, each of them sees only their data flows. This prevents other users from accessing your data flows just by installing the add-on.
If you want other users to see the list of data flows you have set up, you need to [invite those users to your Coupler.io account](/account-management/workspaces-and-organization/how-to-add-user-to-organization-or-workspace.md). If they already have a personal Coupler.io account, they'll need to [switch accounts](/account-management/workspaces-and-organization/how-to-switch-between-organization.md) in the add-on to see your data flows.
---
# 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.coupler.io/addons/google-sheets-addon/why-your-data-flows-sometimes-dont-appear-in-the-add-on.md?ask=&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.
