Chargebee

CRM & salesAPI keyConnection test available

Manage customers, subscriptions and invoices on a Chargebee Billing site through the v2 API (Product Catalog 2.0).

OCNORA ships 31 typed Chargebee operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://{site}.chargebee.com/api/v2 through the HTTP node with the same credential.

Before you connect Chargebee

Authentication
API key
Credential
the Chargebee site API keythe site API key: the raw string, {"api_key": "…"}, or the HTTP Basic pair {"username": "<api key>", "password": ""}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
Prerequisites
  • The key must be a full-access one: a read-only key can list customers and still be refused when it tries to create a webhook endpoint. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to an https URL Chargebee can reach — it only accepts ports 80, 443, 8080 and 8443.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

A sample Chargebee workflow

  1. 1
    Eventtrigger.chargebee_event
    Start a run when Chargebee emits an event (subscription, invoice, payment…).
  2. 2
    Get Customerchargebee.get_customer
    Retrieve one customer by its Chargebee id.
  3. 3
    Apply Credits To Invoicechargebee.apply_credits
    Apply the customer's refundable credit notes to an invoice.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Triggers 1

Operations 31

Chargebee questions

How does OCNORA authenticate with Chargebee?
With a stored API key credential, shaped the Chargebee site API key or the site API key: the raw string, {"api_key": "…"}, or the HTTP Basic pair {"username": "<api key>", "password": ""}. A connection test can check it when you add it.
What can I automate with Chargebee?
31 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the Chargebee operation I need is not listed?
Call https://{site}.chargebee.com/api/v2 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Chargebee?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Chargebee calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Chargebee workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.