Subscription billing and revenue operations platform for managing customers and subscriptions.
Chargebee currently provides 8 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to keep financial events visible beside the customer, vendor, or project they affect.
Subscription Created
Triggers when a new subscription is created for a customer.
Subscription Cancelled
Triggers when a subscription is cancelled.
Subscription Renewed
Triggers when a subscription is successfully renewed.
Subscription Changed
Triggers when a subscription is updated — plan change, quantity, or add-ons.
Payment Succeeded
Triggers when a payment is successfully collected.
Payment Failed
Triggers when a payment attempt fails. Useful for dunning and retry workflows.
Invoice Generated
Triggers when a new invoice is generated for a subscription.
Customer Created
Triggers when a new customer is created in Chargebee.
Create Subscription
Create a subscription for an existing customer using a Chargebee item price.
Cancel Subscription
Cancel a Chargebee subscription immediately, at end of term, or on a specific date.
Create Customer
Create a customer in Chargebee.
Get Customer
Retrieve a customer from Chargebee by ID.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Chargebee event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Subscription Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Chargebee action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Subscription
Combine Chargebee with another integration and Coherence records to keep financial events visible beside the customer, vendor, or project they affect.
Starts with
Subscription Created
Finishes with
Create Subscription, then preserve the outcome in Coherence
The exact authentication fields depend on Chargebee. The workflow structure stays straightforward:
Authorize the Chargebee account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Chargebee or provide a complementary trigger or action.
Chargebee currently provides 8 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to keep financial events visible beside the customer, vendor, or project they affect.
Chargebee currently lists 8 triggers and 5 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Chargebee triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
