TriggerChargebeeReal-timeUpdated June 2026

When does Chargebee fire on successful payments?

Short answer: In TinyCommand, add the Chargebee Payment Succeeded trigger to a workflow and publish. It listens through a Chargebee webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to start a run.

Use this trigger All 4 Chargebee triggers

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

Payment Succeeded

When the matching event happens

when a payment is successfully processedwatch for payment succeedednew payment succeededwhen payment succeededon payment succeeded

What this trigger returns

for the curious

You don’t need to read this. TinyCommand auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "id": "txn_123",
  "date": 1712835600,
  "type": "payment",
  "amount": 4999,
  "customer_id": "cust_123",
  "currency_code": "USD",
  "subscription_id": "sub_123"
}

Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

Field	Type	Example
id	string	"txn_123"
date	number	1712835600
type	string	"payment"
amount	number	4999
customer_id	string	"cust_123"
currency_code	string	"USD"
subscription_id	string	"sub_123"

Pairs with

Drop these actions after Payment Succeeded.

Add Labels to Message

Gmail · Email

Add Reaction

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about Payment Succeeded.

How does the Payment Succeeded trigger work in Chargebee?

Fires when a payment is successfully captured against an invoice. Payload includes amount, currency, payment method, customer, the cleared invoice. The standard revenue-tracking hook for accounting sync and customer-success "they paid" workflows.

Is the Payment Succeeded trigger real-time?

Yes. Payment Succeeded uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Chargebee.

What data does Payment Succeeded return?

The full event payload from Chargebee. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.

Can I filter Payment Succeeded so only some events start a workflow?

Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.

Do I need Chargebee admin permissions to use Payment Succeeded?

For most Chargebee accounts a standard user can authorize the trigger. Some Chargebee plans require an admin to enable third-party webhooks. Check Chargebee's docs if the trigger fails to register.

More triggers

Other Chargebee triggers.

Trigger

Subscription Cancelled

Fires when a subscription cancels — by customer self-serve, by CS team, or scheduled. The churn hook: revoke product access at period end, trigger the exit survey, log to customer-success churn dashboard.

Trigger

Subscription Created

Fires on new subscription creation. Payload includes plan, customer, billing cycle, trial dates. The base hook for SaaS onboarding: provision product access, welcome sequence, notify CS for high-value plans.

Trigger

Subscription Renewed

Fires when a subscription auto-renews at the end of its billing period. Useful for "they renewed → thank them, ask for testimonial, log to retention tracking" workflows that capture the customer-satisfaction signal.