> 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.md).

# Chargify

Chargify is a subscription billing and revenue management platform built for B2B SaaS businesses. It handles recurring billing, subscription lifecycle management, invoicing, and coupon tracking — all in one place.

Connecting Chargify to Coupler.io lets you pull your billing data into spreadsheets, dashboards, data warehouses, or AI tools without writing any code.

## Why connect Chargify to Coupler.io?

* **Centralize your revenue data** — bring customers, subscriptions, invoices, transactions, and coupons into one place
* **Build live revenue dashboards** — send data to Looker Studio, Google Sheets, or Excel and keep it refreshed automatically
* **Combine with other sources** — join Chargify subscription data with CRM or support data to get a full customer picture
* **Analyze with AI** — route your billing data to ChatGPT, Claude, Gemini, or other AI destinations for instant insights

## Prerequisites

* A Chargify account with at least read access to the data you want to export
* A Chargify API key (found in your Chargify site settings)
* Your Chargify subdomain (the prefix in your Chargify URL, e.g., `yourcompany` from `yourcompany.chargify.com`)

## Quick start

{% hint style="success" %}
If you want a broad view of your subscription business, start with the **Subscriptions** entity — it's the most useful for MRR tracking and churn analysis.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account, go to the Data Flows section, and click **Add data flow**.
{% endstep %}

{% step %}
**Select Chargify as your source.** Search for Chargify in the source list and select it.
{% endstep %}

{% step %}
**Enter your API key and subdomain.** In Chargify, go to **Settings → API Keys** to find or generate your API key. Copy it into Coupler.io along with your Chargify subdomain.
{% endstep %}

{% step %}
**Choose the entity you want to import.** Select one of the available entities: Customers, Subscriptions, Invoices, Coupons, or Transactions.
{% endstep %}

{% step %}
**Choose your destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync and confirm the data loads correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity        | What it contains                                                        |
| ------------- | ----------------------------------------------------------------------- |
| Customers     | Contact details, IDs, and metadata for all your Chargify customers      |
| Subscriptions | Subscription status, plan details, MRR, trial info, and lifecycle dates |
| Invoices      | Issued invoices with line items, amounts, payment status, and due dates |
| Coupons       | Discount codes, usage counts, expiry dates, and coupon types            |
| Transactions  | Payment attempts, refunds, and credits tied to subscriptions            |


---

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