Chargebee

undefined

Detail	Value
Category	Finance
Base URL	https://{site}.chargebee.com/api/v2
Authentication	API Key
Endpoints	5
Connector key	chargebee

Using Chargebee in a workflow

1. Go to Connections and click New Connection.
2. Pick Chargebee from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Subscriptions
GET	Customers
GET	Invoices
GET	Plans
GET	Events

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Subscriptions

Detail	Value
Operation ID	subscriptions_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Chargebee connection from the Connection dropdown.
3. In the Operation dropdown, select subscriptions_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Chargebee API reference.

GET

Customers

Detail	Value
Operation ID	customers_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Chargebee connection from the Connection dropdown.
3. In the Operation dropdown, select customers_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Chargebee API reference.

GET

Invoices

Detail	Value
Operation ID	invoices_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Chargebee connection from the Connection dropdown.
3. In the Operation dropdown, select invoices_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Chargebee API reference.

GET

Plans

Detail	Value
Operation ID	plans_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Chargebee connection from the Connection dropdown.
3. In the Operation dropdown, select plans_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Chargebee API reference.

GET

Events

Detail	Value
Operation ID	events_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Chargebee connection from the Connection dropdown.
3. In the Operation dropdown, select events_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Chargebee API reference.