Chargebee MCP integration for AI agents.
Connect AI agents to Chargebee through 9 structured actions, including get customer, create customer, and get invoice. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Chargebee integration exposes
The Chargebee Agent App exposes 9 provider-backed actions for finance work. Its current contract lets an authorized agent retrieve one chargebee customer by id, create a basic chargebee customer record from json-friendly fields, and retrieve one chargebee invoice by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Chargebee account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Chargebee capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADRetrieve one Chargebee customer by ID.
INPUTS: customerId
create_customerWRITECreate a basic Chargebee customer record from JSON-friendly fields.
get_invoiceREADRetrieve one Chargebee invoice by ID.
INPUTS: invoiceId
get_item_priceREADRetrieve one Chargebee item price by ID.
INPUTS: itemPriceId
get_subscriptionREADRetrieve one Chargebee subscription by ID.
INPUTS: subscriptionId
list_customersREADList Chargebee customers with optional exact-match filters and pagination.
INPUTS: limit / offset / id / customerId / subscriptionId
list_invoicesREADList Chargebee invoices with optional exact-match filters and pagination.
INPUTS: limit / offset / id / customerId / subscriptionId
list_item_pricesREADList Chargebee item prices with optional exact-match filters and pagination.
INPUTS: limit / offset / id / customerId / subscriptionId
list_subscriptionsREADList Chargebee subscriptions with optional exact-match filters and pagination.
INPUTS: limit / offset / id / customerId / subscriptionId
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
customerIdREQUIRED- A Chargebee resource identifier.
get_invoice
invoiceIdREQUIRED- A Chargebee resource identifier.
get_item_price
itemPriceIdREQUIRED- A Chargebee resource identifier.
get_subscription
subscriptionIdREQUIRED- A Chargebee resource identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Retrieve one Chargebee customer by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerControl Create Customer
Create a basic Chargebee customer record from JSON-friendly fields. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_customerVerify with Get Invoice
Retrieve one Chargebee invoice by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_invoiceSAFETY BOUNDARY
Operate Chargebee with explicit limits
- Authorize Chargebee with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Chargebee rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Chargebee task completed successfully.
CONNECTION MODEL
API key
Chargebee API key used as the HTTP Basic Auth username with an empty password. Create or view keys in the Chargebee admin console: https://www.chargebee.com/docs/api_keys.html
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Chargebee.