> 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/chargify/faq.md).

# FAQ

<details>

<summary>Can I connect multiple Chargify sites to Coupler.io?</summary>

Yes. Each Chargify site has its own subdomain and API key. Create a separate source connection in Coupler.io for each site. You can then use the **Append** transformation to combine data from multiple sites into a single destination sheet or table.

</details>

<details>

<summary>Why are all the monetary values showing as very large numbers?</summary>

Chargify stores all monetary values in cents — for example, $99.00 is stored as `9900`. Divide any field ending in `_in_cents` or `_amount` by 100 in your destination to get the correct dollar value. This applies to `total_revenue_in_cents`, `product_price_in_cents`, `amount_in_cents`, and similar fields.

</details>

<details>

<summary>Which entity should I use to calculate MRR?</summary>

Use the **Subscriptions** entity. Filter by `state = active`, then sum `product_price_in_cents` (divided by 100) and group by `product_name` or billing interval. For a normalized MRR figure, you'll need to adjust annual plans by dividing by 12.

</details>

<details>

<summary>Can I see which customers have canceled and why?</summary>

The **Subscriptions** entity includes `canceled_at` and `cancellation_message` fields that tell you when a subscription was canceled and any reason recorded at the time. Filter by `state = canceled` to isolate churned subscriptions.

</details>

<details>

<summary>Can I join Chargify data with my CRM or helpdesk data in Coupler.io?</summary>

Yes. Use the **Join** transformation in Coupler.io to link Chargify Customers (using the `email` or `reference` field) with records from another source like HubSpot, Salesforce, or Intercom. This lets you build a unified customer view without any coding.

</details>

<details>

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

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route invoice or subscription data directly to these tools for analysis, forecasting, or drafting customer communications.

</details>

<details>

<summary>How do I find my Chargify API key?</summary>

Log in to your Chargify account, go to **Settings → API Keys**, and either copy an existing key or generate a new one. Make sure the key belongs to the correct site (subdomain) you want to connect.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](/sources/category/finance-and-accounting/chargify/data-overview.md) article. If you're running into connection or authentication problems, check [Common Issues](/sources/category/finance-and-accounting/chargify/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/chargify/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.