> 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

Connect Chargify subscription billing data to Coupler.io — pull customers, subscriptions, invoices, coupons, and transactions into sheets or warehouses.

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            |

## Chargify data overview

Chargify exposes five core entities through Coupler.io. Each one maps to a key part of your subscription billing operation — from who your customers are to how money moves through your system.

## Entities summary

| Entity        | Primary use                                       |
| ------------- | ------------------------------------------------- |
| Customers     | Customer directory and contact data               |
| Subscriptions | Recurring revenue tracking and lifecycle analysis |
| Invoices      | Billing records and payment status                |
| Coupons       | Discount campaign performance                     |
| Transactions  | Payment history and financial reconciliation      |

## Customers

#### Key fields

| Field                      | Description                          |
| -------------------------- | ------------------------------------ |
| `id`                       | Unique Chargify customer ID          |
| `first_name` / `last_name` | Customer name                        |
| `email`                    | Primary contact email                |
| `organization`             | Company name (if B2B)                |
| `created_at`               | Date the customer record was created |
| `updated_at`               | Date the record was last modified    |
| `reference`                | Your internal ID for this customer   |

## Subscriptions

#### Key fields

| Field                    | Description                                                  |
| ------------------------ | ------------------------------------------------------------ |
| `id`                     | Unique subscription ID                                       |
| `state`                  | Current status (active, canceled, trialing, past\_due, etc.) |
| `product_name`           | Name of the subscribed product/plan                          |
| `current_period_ends_at` | End of the current billing cycle                             |
| `trial_ended_at`         | When the trial period ended                                  |
| `activated_at`           | When the subscription became active                          |
| `canceled_at`            | Cancellation date (if applicable)                            |
| `total_revenue_in_cents` | Lifetime revenue from this subscription                      |
| `product_price_in_cents` | Current plan price                                           |
| `customer_id`            | Link back to the customer record                             |

## Invoices

#### Key fields

| Field             | Description                            |
| ----------------- | -------------------------------------- |
| `uid`             | Unique invoice identifier              |
| `number`          | Human-readable invoice number          |
| `status`          | Payment status (paid, pending, voided) |
| `total_amount`    | Total invoice amount                   |
| `due_amount`      | Remaining amount due                   |
| `paid_date`       | Date the invoice was paid              |
| `issue_date`      | Date the invoice was issued            |
| `subscription_id` | Associated subscription                |

## Coupons

#### Key fields

| Field                            | Description                                 |
| -------------------------------- | ------------------------------------------- |
| `id`                             | Unique coupon ID                            |
| `code`                           | The discount code string                    |
| `discount_type`                  | Percentage or flat amount                   |
| `percentage` / `amount_in_cents` | Discount value                              |
| `redemption_limit`               | Max number of uses                          |
| `times_used`                     | How many times the coupon has been redeemed |
| `end_date`                       | Expiry date                                 |
| `created_at`                     | When the coupon was created                 |

## Transactions

#### Key fields

| Field              | Description                                    |
| ------------------ | ---------------------------------------------- |
| `id`               | Unique transaction ID                          |
| `transaction_type` | Type (payment, refund, credit, etc.)           |
| `amount_in_cents`  | Transaction amount                             |
| `success`          | Whether the transaction succeeded              |
| `created_at`       | Transaction timestamp                          |
| `subscription_id`  | Linked subscription                            |
| `customer_id`      | Linked customer                                |
| `gateway_used`     | Payment gateway that processed the transaction |

## Common metric combinations

* **MRR by plan** — Subscriptions filtered by `state = active`, grouped by `product_name`, summing `product_price_in_cents`
* **Churn rate** — Subscriptions with `state = canceled`, count over time using `canceled_at`
* **Revenue collected** — Transactions filtered by `success = true` and `transaction_type = payment`, summing `amount_in_cents`
* **Coupon effectiveness** — Coupons joined to Subscriptions to see conversion rate per discount code
* **Overdue invoices** — Invoices filtered by `status = pending` with `due_amount > 0`

## Use cases by role

{% tabs %}
{% tab title="Finance teams" %}

* Pull **Invoices** and **Transactions** into Google Sheets or Excel for monthly revenue reconciliation
* Use the **Aggregate** transformation to sum `amount_in_cents` by month for cash flow reporting
* Join Transactions with Subscriptions to reconcile payments against active plans
* Send overdue invoice data to ChatGPT or Claude for draft follow-up email suggestions
  {% endtab %}

{% tab title="Revenue/Growth teams" %}

* Track MRR trends using the **Subscriptions** entity, segmented by `product_name`
* Monitor trial-to-paid conversion by comparing `trial_ended_at` vs `activated_at` dates
* Use **Append** to combine subscription data from multiple Chargify sites into a single report
* Analyze coupon redemption rates with the **Coupons** entity to assess discount campaign ROI
  {% endtab %}

{% tab title="Customer success" %}

* Pull **Customers** joined with **Subscriptions** to see which customers are on which plans
* Identify at-risk accounts by filtering subscriptions with `state = past_due`
* Use Looker Studio or a connected AI destination to surface high-value customers at risk of churn
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* All monetary values in Chargify are stored in **cents** — divide by 100 for dollar amounts in your reports
* The `state` field on Subscriptions is the most important field for segmenting active vs. churned revenue
* Chargify uses a **site-based** data model — if you run multiple Chargify sites, each requires its own connection with a separate subdomain and API key
* Coupons are scoped to a product family in Chargify; the exported data reflects this structure
* Deleted customers may still appear in transaction history for audit purposes

## Chargify common issues

### Connection issues

<details>

<summary>Authentication failed — invalid API key</summary>

Double-check that you've copied the full API key from Chargify without any leading or trailing spaces. In Chargify, go to **Settings → API Keys** to verify the key is active. Note that API keys are site-specific — make sure you're using the key from the correct Chargify site.

</details>

<details>

<summary>Subdomain not recognized</summary>

The subdomain field should contain only the prefix of your Chargify URL — not the full URL. For example, if your Chargify portal is at `acme.chargify.com`, enter `acme`, not `https://acme.chargify.com`.

</details>

### Missing data

<details>

<summary>Some subscriptions or customers are missing from the export</summary>

Chargify's API may exclude soft-deleted or archived records by default. If you're missing canceled subscriptions or inactive customers, check whether those records still exist in your Chargify account. Records that have been fully purged from Chargify will not appear in the export.

</details>

<details>

<summary>Coupons entity returns an empty result</summary>

If you haven't created any coupons in Chargify, the entity will return an empty dataset — this is expected behavior. Also confirm that coupons are scoped to the correct product family in Chargify.

</details>

### Permission errors

<details>

<summary>API key returns a 403 Forbidden error</summary>

The API key you're using may have restricted permissions. Chargify supports read-only API keys — make sure the key has at least read access to the entities you're trying to export. If you're unsure, generate a new key in **Settings → API Keys** with full read permissions.

</details>

### Data discrepancies

<details>

<summary>Revenue totals don't match what I see in Chargify's dashboard</summary>

Chargify stores all monetary values in **cents**. If your destination tool is displaying raw values without dividing by 100, the numbers will appear 100x too large. Add a calculated column or formula in your destination to convert cents to dollars.

Also note that Chargify dashboards may apply their own filters (e.g., excluding refunds or credits) that differ from what Coupler.io exports.

</details>

<details>

<summary>Transaction counts differ from the Chargify UI</summary>

The Transactions entity includes all transaction types — payments, refunds, credits, and adjustments. Chargify's UI may filter these differently depending on which report you're viewing. Filter by `transaction_type` in your destination to isolate the specific transaction type you want to reconcile.

</details>

### Rate limits

<details>

<summary>Data flow fails with a rate limit or 429 error</summary>

Chargify enforces API rate limits per site. If you're syncing multiple entities in quick succession or have very large data volumes, you may hit these limits. Try running each entity as a separate data flow and space out your scheduled refreshes. If the problem persists, contact Chargify support to check your site's rate limit tier.

</details>

## Chargify 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](#chargify-data-overview) article. If you're running into connection or authentication problems, check [Common Issues](#chargify-common-issues).
{% 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 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/sources/category/finance-and-accounting/chargify.md?ask=<question>&goal=<user_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.
