A Chargebee MCP for billing workflows that reach past billing
Connect one site-scoped API key and the whole subscription lifecycle becomes workflow steps: customers, subscriptions, invoices, credit notes, payment sources, hosted checkout pages, coupons, and the event stream. An AI agent can answer billing questions from live data, a failed payment can open a task with the invoice attached, and every node that moves money is flagged destructive so workflows gate it. Build it all first on the test site that comes with every Chargebee account, with test money.
What the Chargebee MCP connector does
The Chargebee connector for Mattering Automations is 48 nodes across the Chargebee API v2, built on Product Catalog 2.0: customers, the full subscription lifecycle (create, update, cancel, pause, resume, reactivate), catalog items and their item prices, invoices with void, delete, and collect payment, credit notes and refunds, read-only transactions, stored payment sources, hosted checkout and payment-method pages, customer portal sessions, coupons, and the event stream that mirrors what webhooks deliver. One site-scoped API key authenticates all of it.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can look up a customer's subscriptions, read the invoice that just failed to collect, check the stored payment source's status, and draft the follow-up, without anyone opening the Chargebee admin console.
Chargebee builds its own official MCP tooling, including a hosted MCP server that gives assistants a direct line to your billing data, and if that is the whole job it is a genuine option. This connector is for the other half of the job, where billing is one step among many. On the Mattering canvas the same nodes sit next to every other connector and the platform itself, so a failed payment can open a task with the invoice attached, a refund can wait behind a human approval step, and a nightly sweep can write subscriptions and invoice totals into a Mattering database next to the rest of your work. Use whichever fits, or both.
The safety modeling is stated plainly, because in billing, destructive usually means money. Of the 48 nodes, 22 are safe reads, 14 are reversible writes, and 12 are flagged destructive: creating a subscription can generate and charge the first invoice at creation when auto collection is on and a payment source is stored, updating one can collect prorated charges immediately, collecting an invoice charges the customer's payment method, refunding a credit note moves money out of the account, and the customer, invoice, payment source, and coupon deletes are permanent. Workflows see the flag and gate accordingly. The other half of the safety story is Chargebee itself: every account includes a test site, a sandbox with its own API key and a test gateway, and the entire node surface, including every destructive node, runs there with test money.
One connection, three surfaces
- Visual automations. Drag Chargebee nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Chargebee node, ready to drop on the canvas
48 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 22
Chargebee: Get Coupon
Fetch one coupon: discount, duration, applicability, validity, and how many times it has been redeemed.
Chargebee: Get Credit Note
Fetch one credit note: type, status, the invoice it credits, and how much is allocated, refunded, and still available.
Chargebee: Get Customer
Fetch one customer: contact details, billing address, auto collection setting, and credit balances (promotional, refundable, excess payments).
Chargebee: Get Event
Fetch one event with its full content object (the affected customer, subscription, invoice, or other resources as of the event).
Chargebee: Get Hosted Page
Fetch one hosted page: its state (a succeeded state means the customer completed it) and, once succeeded, the resulting subscription or customer content.
Chargebee: Get Invoice
Fetch one invoice: status, line items, linked payments, applied credits, and the amounts due, paid, and adjusted.
Chargebee: Get Item
Fetch one catalog item: type, family, applicability, and checkout/portal visibility.
Chargebee: Get Item Price
Fetch one item price: pricing model, amount, currency, period, and trial settings.
Chargebee: Get Payment Source
Fetch one payment source: type, status, gateway, and masked instrument details (never the full number).
Chargebee: Get Subscription
Fetch one subscription: status, current term window, next billing time, and the subscription_items it is billed on.
Chargebee: Get Transaction
Fetch one transaction: type, status, amount, gateway reference, error details on failures, and the invoices or refunds it is linked to.
Chargebee: List Coupons
List coupons with filters on name, discount type, duration type, and status. Rows arrive at data.list[].coupon with redemption counts.
Chargebee: List Credit Notes
List credit notes with filters on customer, subscription, the invoice they credit, type (adjustment or refundable), and status. Rows arrive at data.list[].credit_note with allocated, refunded, and available amounts.
Chargebee: List Customers
List customers with filters on email, name, and created or updated time. Needs no parameters and works for every API key (a fresh site returns an empty list), so this is the credential health check to run first in any Chargebee automation. Rows arrive wrapped per entity at data.list[].customer; pass data.next_offset back as offset for the next page.
Chargebee: List Events
List events (the same stream webhooks deliver): subscription_created, invoice_generated, payment_succeeded, and the rest, filtered by type, source, and occurrence time. Each row's content object carries the affected resources; poll this to drive automations without a webhook endpoint.
Chargebee: List Hosted Pages
List hosted pages with filters on type (checkout_new, checkout_existing, manage_payment_sources, and others) and state (created, requested, succeeded, cancelled, acknowledged). Rows arrive at data.list[].hosted_page.
Chargebee: List Invoices
List invoices with filters on customer, subscription, status, and invoice or updated date. Rows arrive at data.list[].invoice with line items, payments, and amounts in the currency's minor unit.
Chargebee: List Item Prices
List item prices (the sellable price points of items: currency, period, and pricing model). Rows arrive at data.list[].item_price; filter by item_id to see one item's price points.
Chargebee: List Items
List catalog items (Product Catalog 2.0: plans, addons, and charges are all items). Rows arrive at data.list[].item.
Chargebee: List Payment Sources
List stored payment sources with filters on customer, type (card, paypal_express_checkout, direct_debit, and others), and status (valid, expiring, expired, invalid, pending_verification). Rows arrive at data.list[].payment_source; card entries carry masked details only.
Chargebee: List Subscriptions
List subscriptions with filters on customer, status, item price, and created or updated time. Rows arrive at data.list[].subscription with subscription_items showing each item price on the subscription.
Chargebee: List Transactions
List payment transactions with filters on customer, subscription, payment source, type (authorization, payment, refund, payment_reversal), status, gateway, and date. Rows arrive at data.list[].transaction with linked invoices and refunds for reconciliation.
Action nodes 26
Chargebee: Cancel Subscription
DESTRUCTIVE: cancel a subscription, immediately by default or at end of term. Immediate cancellation ends service now and can issue prorated credits or schedule refunds for the unused term per the options below. Chargebee CAN reactivate a cancelled subscription, but reactivation normally starts a fresh billing term and invoices immediately (the one documented exception is a subscription cancelled by dunning and reactivated inside its original term, which keeps that term and raises no invoice), so cancel plus reactivate is not a clean undo. Prefer Pause Subscription for a temporary stop.
Chargebee: Checkout Change Subscription Page
Create a hosted checkout page URL for changing an EXISTING subscription (upgrade, downgrade, quantity change). Nothing changes until the customer completes the page; the URL expires 3 hours after creation.
Chargebee: Checkout New Subscription Page
Create a hosted checkout page URL for a NEW subscription on the given item prices. Nothing is billed by creating the page; the customer pays only if they complete checkout. Per the vendor docs the URL expires 3 hours after creation. Send data.hosted_page.url to the customer.
Chargebee: Collect Invoice Payment
DESTRUCTIVE (moves real money): charge the customer's payment source for an invoice in payment_due, posted, or not_paid status. Per the vendor docs it collects the invoice's full amount_to_collect unless a smaller amount is given, and returns the updated invoice plus the payment transaction.
Chargebee: Create Coupon
Create a coupon for Product Catalog 2.0 items: a fixed amount or percentage deduction applied to the invoice or to specific item prices. Item constraints (which items the coupon covers) go through extra_body per the documented item_constraints shape.
Chargebee: Create Credit Note
DESTRUCTIVE (creates money owed): issue a credit note against an invoice. Type refundable creates real money owed back to the customer (retained as credits, applied to unpaid invoices, or refunded); type adjustment reduces an unpaid invoice. Classed destructive per the refund precedent because a refundable credit is a liability on the books the moment it exists.
Chargebee: Create Customer
Create a customer record. Nothing is billed by creating a customer; subscriptions and invoices are separate steps. Chargebee generates the id when you leave it blank.
Chargebee: Create Item
Create a catalog item (a plan, addon, or charge in Product Catalog 2.0). Items carry no price; create item prices for each currency and period afterwards.
Chargebee: Create Item Price
Create a price point for an item: one currency, period, and pricing model combination, for example silver-USD-monthly. period and period_unit are required for plan and addon items.
Chargebee: Create Portal Session
Create a customer portal session and its pre authenticated access_url, so a customer manages their own subscriptions, payment methods, and invoices. Per the vendor docs the access_url must be used within one hour and works once; mint a fresh session per visit.
Chargebee: Create Subscription
DESTRUCTIVE (moves real money): create a subscription for an existing customer on the given item prices. With auto collection on and a stored payment source, Chargebee generates the first invoice and charges it immediately at creation; use start_date or trial_end for a subscription that must not bill now. The response carries the subscription, the customer, and the first invoice when one was generated.
Chargebee: Delete Coupon
DESTRUCTIVE: permanently delete a coupon. The code stops being redeemable and there is no undelete; archive via the Chargebee UI is the reversible alternative when the code might return.
Chargebee: Delete Customer
DESTRUCTIVE: permanently delete a customer. The customer is marked deleted and their subscriptions, unpaid invoices, and stored payment methods go with them per site settings; there is no undelete. Optionally also deletes the payment method at the gateway.
Chargebee: Delete Invoice
DESTRUCTIVE: permanently delete an invoice. The vendor's preconditions are effectively those of Void Invoice (no successful or in-progress linked payments, amount_adjusted zero, no refunded or refund_due credit notes, no withheld taxes) plus a bar on gift subscriptions, so the real difference from voiding is what survives the call, not which invoices are accepted. The vendor's own docs recommend voiding instead because voiding preserves the audit trail; a deleted invoice is only reachable again via List Invoices with include_deleted.
Chargebee: Delete Payment Source
DESTRUCTIVE: permanently delete a stored payment source, including the copy at the payment gateway where the gateway supports deletion. A customer whose only payment source is deleted cannot be auto-collected until a new one is added; there is no undo.
Chargebee: Manage Payment Sources Page
Create a hosted page URL where a customer adds or updates their payment methods without card data ever touching your systems. Per the vendor docs this page type's URL stays valid for 5 days.
Chargebee: Pause Subscription
Pause an active subscription so billing stops until it is resumed. Resume Subscription is the documented inverse, which is what makes this the reversible alternative to cancelling.
Chargebee: Reactivate Subscription
DESTRUCTIVE (moves real money): reactivate a CANCELLED subscription. Per the vendor docs the subscription returns to active or in_trial, a new billing term starts, and charges raised at execution are invoiced (and collected when auto collection is on) unless invoice_immediately is false or trial_end puts it back in trial. One documented exception: a subscription cancelled by dunning and reactivated inside its original billing term keeps that term and generates no new invoice. Only cancelled subscriptions can be reactivated.
Chargebee: Refund Credit Note
DESTRUCTIVE (moves real money): refund a refundable credit note's available amount to the customer through the original payment method. Money leaves the account and there is no API undo; the response carries the updated credit note and the refund transaction.
Chargebee: Resume Subscription
Resume a paused subscription, immediately or at a specific date; the pause pair's documented inverse. Note that normal billing restarts on resumption, and charges pending from the pause can be invoiced immediately per charges_handling.
Chargebee: Update Coupon
Update a coupon's name, discount value, validity, or redemption cap. Only the fields you fill are changed; changes apply to future redemptions, not to subscriptions already carrying the coupon.
Chargebee: Update Customer
Update a customer's contact and collection settings. Only the fields you fill are changed. Billing address changes use Chargebee's separate update_billing_info endpoint (not built); switching auto_collection to on makes future invoices charge the stored payment method automatically.
Chargebee: Update Item
Update a catalog item's names, description, applicability, or visibility. Only the fields you fill are changed; the item's type cannot be changed after creation.
Chargebee: Update Item Price
Update an item price's names, amount, or trial. Per the vendor docs, once subscriptions or invoices exist for an item price its pricing_model, period, period_unit, currency_code, and billing_cycles become immutable; changing the price only affects future invoices.
Chargebee: Update Subscription
DESTRUCTIVE (can move real money): change a subscription's item prices, quantities, or term. The subscription_items array REPLACES the complete list of items on the subscription, so pass every item that should remain, not just the changes. With proration on, upgrade charges can be invoiced and collected immediately against the stored payment method.
Chargebee: Void Invoice
DESTRUCTIVE: void an invoice in payment_due, posted, or not_paid status. The vendor's preconditions are the same list Delete Invoice enforces: no successful or in-progress linked payments, amount_adjusted must be zero, no refunded or refund_due credit notes, and no withheld taxes. The status becomes voided permanently: no un-void exists, applied promotional credits return to the customer, and per the vendor docs Chargebee will not issue prorated credits later for the term the voided invoice covered. Voiding preserves the record for audit; prefer it over Delete Invoice.
Connecting Chargebee takes one credential
Chargebee authenticates API requests with HTTP Basic auth: the API key is the username and the password is left empty. Keys are created per site in the Chargebee admin console under Settings, then Configure Chargebee, then the API keys section, which Chargebee's own docs label API Keys and Events in one place and API Keys and Webhooks in another. The site name matters as much as the key: every Chargebee account has two separate sites, a test site and a live site, each with its own name, its own data, and its own API keys, and the site name in the credential is what selects the environment. Start on the test site.
Sign in to Chargebee. To start safely, switch to your test site first: click your account name and choose Go to TEST site. The test site is its own site with its own API key and a test gateway, so everything you build there bills test money only.
Open Settings, then Configure Chargebee, then the API keys section, and create an API key. Chargebee documents several key types and the type decides how much of the connector works: a full-access key of the All type covers every node including the deletes, while its Write and Update variants withhold create or delete rights, and on the read side a Read-only: All key covers the 22 query nodes whereas a Read-only: Restricted key only covers the data groups you tick.
Note your site name: the first label of your Chargebee domain, for example acme in acme.chargebee.com, with the test site as its own name such as acme-test. You can also paste the full domain and Mattering reduces it to the bare site name.
In Mattering Automations, open Connectors, click Add Connector, choose Chargebee, and create a credential with the site name and API key.
Click Test Connection. Mattering asks the site for one customer over the API: success proves both the site name and the key, a 401 means the key is wrong for that site, and a connection failure means the site name is wrong. Then all 48 Chargebee nodes appear in the canvas palette; Chargebee: List Customers is the health check to run first.
Common uses for the Chargebee MCP
Failed payments that open a task instead of a ticket nobody sees
Chargebee: List Events polls the same stream webhooks deliver, filtered by event type and occurrence time, so a scheduled run can pick up payment failures without hosting a webhook endpoint. Chargebee: Get Invoice pulls the invoice with its amounts due and linked payments, Chargebee: Get Transaction carries the gateway's error details for the failed attempt, and the workflow opens a task in Mattering Productivity with all of it attached. The retry itself, Chargebee: Collect Invoice Payment, is flagged destructive because it charges the customer's payment method, so put it behind an approval step rather than a bare schedule.
Checkout links minted from anywhere a lead shows up
Chargebee: Create Customer makes the record, and nothing is billed by creating a customer. Chargebee: Checkout New Subscription Page then mints a hosted checkout URL for the item prices you choose: the customer pays only if they complete the page, card data never touches your systems, and per the vendor docs the URL expires 3 hours after creation, so mint it at send time. Chargebee: Get Hosted Page reports the page's state afterward; a succeeded state means the customer completed checkout and carries the resulting subscription.
An AI agent that answers billing questions from live data
The 22 query nodes are the safest surface to hand an agent: Chargebee: List Subscriptions with status filters, Chargebee: List Invoices for what is due and what was paid, Chargebee: List Transactions for reconciliation, Chargebee: List Payment Sources for card status including expiring and expired, and Chargebee: Get Customer for balances. An agent can answer which subscriptions renew this week, which invoices sit unpaid, and whose card expires next month, all read-only, with the 12 destructive nodes never in reach unless a workflow explicitly wires them.
Subscription changes with the reversible pair first
Chargebee: Pause Subscription stops billing until Chargebee: Resume Subscription restarts it, the documented inverse pair, which makes pause the right tool for a temporary stop. Cancellation is flagged destructive for a reason: Chargebee can reactivate a cancelled subscription, but per the vendor docs reactivation generates an invoice for a new term in every case but one, a subscription cancelled by dunning and reactivated inside its original billing term, so cancel plus reactivate is not a clean undo. The honest workflow pattern is pause by default, and cancel only behind a condition or an approval task.
Catalog kept in sync from where the product actually lives
Chargebee: Create Item and Chargebee: Create Item Price build the Product Catalog 2.0 shape, an item plus one price point per currency and period combination, and Chargebee: Update Item and Chargebee: Update Item Price change only the fields you fill. A workflow can read a product database in Mattering and keep the Chargebee catalog matching it. One documented boundary the nodes state plainly: once subscriptions or invoices exist for an item price, its pricing model, period, and currency become immutable, and price changes only affect future invoices.
Credits and refunds with a human in the loop
Chargebee: Create Credit Note issues a credit against an invoice: type adjustment reduces an unpaid invoice, while type refundable creates real money owed back to the customer the moment it exists, which is why the node is flagged destructive. Chargebee: Refund Credit Note then moves the available amount back through the original payment method, with no API undo. Both nodes carry the destructive flag so the natural workflow shape is exactly what a finance team wants anyway: the request lands as an approval task, and the money moves only after a person says so.
Example: A lead converts: create the customer, send a checkout link, know when they paid
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a form submission or inbound webhook arrives carrying the lead's name, email, and the plan they chose.
Chargebee: Create Customer makes the customer record. Nothing is billed by creating a customer; subscriptions and invoices are separate steps.
Chargebee: List Item Prices looks up the item price id for the chosen plan, currency, and period.
Chargebee: Checkout New Subscription Page mints the hosted checkout URL for that customer and item price. The customer pays only if they complete the page, and the URL expires 3 hours after creation, so the workflow sends it immediately.
A scheduled follow-up run calls Chargebee: Get Hosted Page and checks for a succeeded state, which carries the resulting subscription.
The workflow writes the new subscription into a Mattering database and opens an onboarding task in Mattering Productivity, so the first human touch happens while the signup is still warm.
Chargebee MCP questions, answered
What Chargebee operations are supported?
48 nodes on the Chargebee API v2 with Product Catalog 2.0: 22 query nodes and 26 action nodes covering customers (list, get, create, update, delete), the subscription lifecycle (create, update, cancel, pause, resume, reactivate), catalog items and item prices, invoices (list, get, void, delete, collect payment), credit notes (create, refund), read-only transactions, payment sources (list, get, delete), hosted checkout and payment-method pages, portal sessions, the event stream, and coupons. Deliberately not shipped: legacy Product Catalog 1.0 plans and addons, quotes, raw payment-source creation (the hosted page is the PCI-clean path), invoice back-office operations like record payment and write-off, and webhook management, which Chargebee configures in site settings rather than through the API.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Chargebee has an official MCP server. Why use this connector?
Chargebee does offer its own official MCP tooling, including a hosted MCP server that connects assistants directly to your billing data, and if all you want is an assistant talking to Chargebee alone, it is a genuine option. This connector earns its place when billing is one step in a larger workflow: the same canvas holds your other connectors and the Mattering platform itself, so a failed payment can open a task, a refund can wait behind a human approval step, and a nightly sweep can write invoices into a database next to the rest of your work. Credentials live in one place with your other connector secrets, and the same nodes serve visual automations and AI agents alike. Use whichever fits, or both.
Can an automation charge a customer real money?
Yes, and the connector says so on the nodes instead of hiding it. Chargebee: Collect Invoice Payment charges the customer's payment source for an invoice's collectible amount. Chargebee: Create Subscription can generate and charge the first invoice at creation when auto collection is on and a payment source is stored; start_date or trial_end are the documented ways to create one that must not bill now. Chargebee: Update Subscription can invoice and collect prorated upgrade charges immediately, and Chargebee: Reactivate Subscription generates an invoice for a new term unless the subscription was cancelled by dunning and is reactivated inside its original term. Every one of these carries the destructive flag, so workflows can gate them behind conditions or approval steps, and nothing else in the connector moves money.
Is there a safe way to test billing workflows?
Yes, and it is Chargebee's own: every Chargebee account includes a test site alongside the live site. The test site is a sandbox with its own site name, its own API key, and a test gateway, so the entire 48-node surface, including every destructive node, runs there with test money. Point the Mattering credential at the test site name, build and run the whole workflow, then create a second credential with the live site name and key when it is ready. Test and live are separate sites, so nothing done on one touches the other.
Does this support Product Catalog 1.0 plans and addons?
No. The connector is built on Product Catalog 2.0, where plans, addons, and charges are all items with item prices as their sellable price points, and the subscription and coupon operations use Chargebee's item-based endpoints. Sites still running the legacy Product Catalog 1.0 model are not covered; Chargebee documents the migration path between the two catalog versions.
If a workflow cancels a subscription, can it undo that?
Not cleanly, which is why cancel is flagged destructive. Chargebee can reactivate a cancelled subscription, but per the vendor docs reactivation generates an invoice for a new term, collected immediately when auto collection is on, so cancel plus reactivate is a new term with new charges rather than a rollback. The one documented exception is narrow: a subscription cancelled by dunning and reactivated inside its original billing term keeps that term and generates no new invoice. Immediate cancellation can also issue prorated credits or schedule refunds for the unused term. For a temporary stop, Chargebee: Pause Subscription and Chargebee: Resume Subscription are the documented reversible pair, and the node copy points there.
What is the difference between voiding and deleting an invoice?
They are different nodes with different consequences, and Chargebee's own docs recommend voiding. Chargebee: Void Invoice works on invoices in payment_due, posted, or not_paid status, sets the status to voided permanently with no un-void, returns applied promotional credits to the customer, and preserves the invoice for audit. Chargebee: Delete Invoice permanently removes it instead. Their preconditions are close to identical, since both are refused when the invoice carries successful or in-progress payments, adjustments, refund-state credit notes, or withheld taxes, so the real difference is what survives the call: after a delete the invoice is reachable only through List Invoices with include_deleted. Both are flagged destructive; when an invoice was generated incorrectly, void is the vendor-recommended call because the record stays auditable.
Put Chargebee to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Chargebee is a product of its respective owner; Mattering is an independent platform.