Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Chargebee

Subscription billing and revenue operations platform for managing customers and subscriptions.

CategoryAccounting
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Chargebee with Flows360

Subscription billing and revenue operations platform for managing customers and subscriptions.

Use the Chargebee connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 8 triggers.

Available actions

  • Create Subscription
  • Cancel Subscription
  • Create Customer
  • Get Customer
  • Custom API Call

Available triggers

  • Subscription Created
  • Subscription Cancelled
  • Subscription Renewed
  • Subscription Changed
  • Payment Succeeded
  • Payment Failed
  • Plus 2 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Chargebee
  • Package: @activepieces/piece-chargebee@0.1.0
  • Exact artifact digest: sha256:177a9f064f7beaab044066b37af5069fd047d1b8015ca75889540c27f38fe3e0
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Subscription (create_subscription), Create a subscription for an existing customer using a Chargebee item price. Classification: read.
  • Cancel Subscription (cancel_subscription), Cancel a Chargebee subscription immediately, at end of term, or on a specific date. Classification: read.
  • Create Customer (create_customer), Create a customer in Chargebee. Classification: read.
  • Get Customer (get_customer), Retrieve a customer from Chargebee by ID. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Subscription Created, webhook.
  • Subscription Cancelled, webhook.
  • Subscription Renewed, webhook.
  • Subscription Changed, webhook.
  • Payment Succeeded, webhook.
  • Payment Failed, webhook.
  • Invoice Generated, webhook.
  • Customer Created, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects13
Supported actionsNot published
Triggers8

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Site Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Subscription Yes No Create a subscription for an existing customer using a Chargebee item price.
Cancel Subscription Yes No Cancel a Chargebee subscription immediately, at end of term, or on a specific date.
Create Customer Yes No Create a customer in Chargebee.
Get Customer Yes No Retrieve a customer from Chargebee by ID.
Custom API Call Yes No Make a custom API call to a specific endpoint
Subscription Created Yes No webhook trigger declared by the pinned package.
Subscription Cancelled Yes No webhook trigger declared by the pinned package.
Subscription Renewed Yes No webhook trigger declared by the pinned package.
Subscription Changed Yes No webhook trigger declared by the pinned package.
Payment Succeeded Yes No webhook trigger declared by the pinned package.
Payment Failed Yes No webhook trigger declared by the pinned package.
Invoice Generated Yes No webhook trigger declared by the pinned package.
Customer Created Yes No webhook trigger declared by the pinned package.

Triggers

Subscription Created · Webhook

Triggers when a new subscription is created for a customer.

Subscription Cancelled · Webhook

Triggers when a subscription is cancelled.

Subscription Renewed · Webhook

Triggers when a subscription is successfully renewed.

Subscription Changed · Webhook

Triggers when a subscription is updated u2014 plan change, quantity, or add-ons.

Payment Succeeded · Webhook

Triggers when a payment is successfully collected.

Payment Failed · Webhook

Triggers when a payment attempt fails. Useful for dunning and retry workflows.

Invoice Generated · Webhook

Triggers when a new invoice is generated for a subscription.

Customer Created · Webhook

Triggers when a new customer is created in Chargebee.

Setup

Setup

  1. Add the Chargebee connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Site (site), required.
  • API Key (api_key), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-chargebee@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 8 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Chargebee connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-chargebee@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com