> 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/sources/category/finance-and-accounting/cin7/faq.md).

# FAQ

<details>

<summary>What authentication method does Cin7 use with Coupler.io?</summary>

Cin7 uses API key authentication. You'll need your **API Username** and **API Key** from Cin7, which you can find under **Settings > Integrations > API** in your Cin7 account. There's no OAuth flow — just copy and paste the credentials into Coupler.io.

</details>

<details>

<summary>Can I connect multiple Cin7 accounts in the same data flow?</summary>

Yes. Add each Cin7 account as a separate source block within the same data flow, then use the **Append** transformation to combine the records. This is useful if you run separate Cin7 accounts by region, brand, or warehouse.

</details>

<details>

<summary>What's the difference between Sale lists and Sales?</summary>

**Sales** contains one row per transaction with summary-level data like total revenue, COGS, and margin. **Sale lists** contains one row per line item within each order, so you can see exactly which products were sold. Use Sales for revenue reporting and Sale lists for product-level analysis.

</details>

<details>

<summary>What's the difference between Purchase lists and Purchases?</summary>

Same pattern as sales — **Purchases** is the transaction-level summary (total cost, supplier, payment status), while **Purchase lists** is the line-item detail (which products, quantities, and unit costs were on each PO). Use both if you need a complete picture of procurement.

</details>

<details>

<summary>Can I get historical stock level data from Cin7?</summary>

Cin7's API returns current stock levels, not a historical log. To build a stock history, configure your Coupler.io data flow to **append** data on each run rather than overwrite it. Each sync will add a new snapshot with a timestamp, giving you a time series over time.

</details>

<details>

<summary>Why are my CRM entities (Leads, Deals, Opportunities) empty?</summary>

These entities only contain data if you actively use Cin7's built-in CRM module. If your team uses a separate CRM tool, these entities won't have records. Check in Cin7 whether the CRM module is enabled and whether records exist.

</details>

<details>

<summary>Can I send Cin7 data to an AI tool like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route any Cin7 entity — for example, Sales or Opportunities — directly to an AI destination for analysis, forecasting, or automated reporting.

</details>

<details>

<summary>How do I analyze revenue by product using Cin7 data?</summary>

Add both the **Sales** and **Products** entities as source blocks in the same data flow, then use Coupler.io's **Join** transformation to link them on the shared product or SKU identifier. This gives you a combined dataset with transaction revenue alongside product details like cost price, category, and brand.

</details>

<details>

<summary>Is Cin7 API access available on all plans?</summary>

No — API access is typically available on Cin7's Business and Enterprise plans. If you can't find the API section under **Settings > Integrations**, contact Cin7 support to confirm whether your plan includes it.

</details>

{% hint style="info" %}
For a full breakdown of what each Cin7 entity contains and how to combine them, see [Data Overview](/sources/category/finance-and-accounting/cin7/data-overview.md). If you're running into connection or data problems, check [Common Issues](/sources/category/finance-and-accounting/cin7/common-issues.md).
{% endhint %}


---

# 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://docs.coupler.io/sources/category/finance-and-accounting/cin7/faq.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.